Magic Patterns
Generate and edit Magic Patterns UI designs from your AI assistant. Anthropic lists 3 tools, none of which appear in Magic Patterns' current documentation, which documents 23. Generation burns credits and a paid plan is required.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Magic Patterns via MCP
https://mcp.magicpatterns.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Magic Patterns Tools & Capabilities (3)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The directory tool list shares no names with the documentation. Three listed against twenty-three documented, and none of the three —
get_design,read_files,update_design— appears in Magic Patterns' current tool documentation.read_filesis traceable to a February 2026 changelog entry as a since-renamed name; the other two are not traceable to any Magic Patterns page we found. Read the vendor's tool page, not the listing. - The directory record has no permissions label at all. Not "Read and write", not "Read only" — the field is absent, over a surface Magic Patterns itself describes as including twelve destructive tools. Tenth instance of this pattern in this catalogue.
- We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no safety annotations were readable. Every read/write classification here is Magic Patterns' own.
send_promptis a natural-language dispatcher. Its effective surface is whatever the Magic Patterns generator can do to a design, and the documentation does not bound that. The artifact tools are the reviewable alternative.- The safe artifact workflow is a convention, not an enforcement. Magic Patterns tells agents to clone an artifact before writing, but nothing documented stops
write_artifact_filesfrom targeting the active one directly. - Design-system writes activate immediately.
write_design_system_filesmerges, compiles and activates in one call, with no staging step — and a design system is shared across designs by definition. - Concurrency protection covers design systems only.
baseArtifactIdand a 409 exist there; the design and artifact tools have no documented equivalent, only guidance to re-read state first. - Rollback is fork-and-copy, not revert. Forking from an older version creates a new independent design; the original and its damaged current state remain. Version history returns the most recent 20 versions and message history the last 10 items.
- Generation costs money. Magic Patterns marks
create_design,create_slide_deckandsend_promptas requiring credits, puts one generation at roughly 25 credits, and bills MCP usage against the same balance as the web app. With on-demand usage enabled, overage bills at $0.02 per credit. - A paid plan is required. Magic Patterns states MCP integration requires one, and its plan table marks the MCP unavailable on the free tier. The same gate applies to API-key authentication.
- Generation is slow and asynchronous. Magic Patterns puts it at 2–10 minutes and instructs clients not to poll more often than every 60 seconds. An agent will not see the result of a prompt in the same turn.
- The advertised scopes carry no authorization information. All four are identity scopes; nothing in the token separates reading a design from overwriting one. Use the read-only endpoint if that separation matters.
- Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, and the gated endpoint blocked our own check, so we cannot confirm the
design_system_authoring_guideprompt the docs reference is served over MCP. - The Cursor plugin is a wider surface than the MCP. Magic Patterns calls it a superset — same server plus four bundled skills, including one that generates and publishes a shareable set of design concepts.
Frequently asked questions
How many tools does the Magic Patterns MCP server actually have?
Magic Patterns documents twenty-three. Anthropic's directory snapshot lists three, and none of those three names appears anywhere in the current documentation. This is not a subset gap like Base44's — it is a full mismatch. The documented set spans design creation, artifact file reads and writes, publishing, design-system authoring and inspiration documents. Read the vendor's tool page, not the listing.
Does the Magic Patterns MCP server show a Read and write permission label?
No. Anthropic's 2026-08-16 directory record for Magic Patterns carries no permissions field at all — not an empty one, an absent one. The documented surface includes tools that create designs, overwrite artifact files, publish artifacts and publish design-system versions. This is the tenth connector in this catalogue whose record omits the label over a documented write surface.
Can I roll back a change an AI agent made to my Magic Patterns design?
Yes, through version history and forking. Magic Patterns documents an artifact version timeline and a forking feature that creates an independent copy from any earlier version, which it recommends for recovering after a bad run of changes. Its own tool guidance also tells agents to clone the active artifact before writing files, so the previous one stays revertible.
Does the Magic Patterns MCP server let an agent edit a design in place?
It depends which tool. Magic Patterns documents a code-first path where an agent clones the active artifact first, writes files into that clone, then publishes it — so the previous artifact survives as a version. The prompt-based path sends an instruction to Magic Patterns' own AI, which updates the design directly and adds a timeline entry.
Does using the Magic Patterns MCP server cost credits?
Yes, for generation. Magic Patterns marks its design-creation and prompt tools as requiring credits, and states that MCP usage bills against your normal credit balance exactly as the web app does. It puts a single generation at roughly 25 credits. Free plans get 100 monthly credits, but the MCP itself needs a paid plan regardless.
Do I need a paid Magic Patterns plan to use the MCP server?
Yes. Magic Patterns states plainly that MCP integration requires a paid plan, and its plan comparison table marks the MCP as unavailable on the free tier. The same requirement covers API-key authentication. Paid plans start at Starter, priced at twenty dollars per seat per month, and plans apply per workspace rather than per account.
What files can the Magic Patterns MCP server read?
Files inside a Magic Patterns artifact or design system you can already reach, named explicitly by the caller. Magic Patterns documents no filesystem tool and no repository-browsing tool on the MCP server. A design can have a GitHub repository attached as context inside the product, but that attachment is made in the editor, not through any documented MCP tool.
Does the Magic Patterns MCP server have a read-only mode?
Yes, at a separate endpoint. Magic Patterns documents a read-only URL that ends in slash readonly, on which the writing tools are not registered at all, so a client cannot list or call them. It names ten tools exposed there and twelve it withholds. The same OAuth flow and API keys work against both URLs.
Sources
- Magic Patterns MCP overview — https://www.magicpatterns.com/docs/documentation/features/mcp-server/overview (fetched 2026-08-19 as Markdown via the
.mdsuffix; this is the URL Anthropic's directory publishes) · retrieved 2026-08-19 - Magic Patterns MCP tools and workflows — https://www.magicpatterns.com/docs/documentation/features/mcp-server/available_tools (fetched 2026-08-19; source of the 23-tool list and every per-tool description) · retrieved 2026-08-19
- Magic Patterns credits and plans — https://www.magicpatterns.com/docs/documentation/get-started/credits-and-billing (fetched 2026-08-19; plan table, credit costs, on-demand pricing) · retrieved 2026-08-19
- Magic Patterns v3 API getting started — https://www.magicpatterns.com/docs/api/getting-started (fetched 2026-08-19; the statement that v3 mirrors the MCP surface and shares its credit balance) · retrieved 2026-08-19
- Magic Patterns changelog — https://www.magicpatterns.com/docs/documentation/feature-releases/changelog (fetched 2026-08-19; the 2026-02-28 entry naming the pre-rename tool vocabulary) · retrieved 2026-08-19
- Magic Patterns forking — https://www.magicpatterns.com/docs/documentation/editor/forking (fetched 2026-08-19) · retrieved 2026-08-19
- Magic Patterns sharing designs — https://www.magicpatterns.com/docs/documentation/editor/sharing (fetched 2026-08-19; access levels, publishing, private-by-default date) · retrieved 2026-08-19
- Magic Patterns connect to GitHub — https://www.magicpatterns.com/docs/documentation/importing/connect-github (fetched 2026-08-19) · retrieved 2026-08-19
- Magic Patterns custom publish URL — https://www.magicpatterns.com/docs/documentation/publishing/publish-url (fetched 2026-08-19) · retrieved 2026-08-19
- Magic Patterns docs machine index — https://www.magicpatterns.com/docs/llms.txt (fetched 2026-08-19; 103 lines listing every docs page and two OpenAPI specs) · retrieved 2026-08-19
www.magicpatterns.com/robots.txtallows the docs paths and carries no Content-Signal header. The docs host's own/docs/robots.txtcarriesContent-Signal: ai-train=yes, search=yes, ai-input=yes— synthesis is expressly permitted on all three axes (both fetched 2026-08-19) · retrieved 2026-08-19- Live RFC 9728 protected-resource descriptor — https://mcp.magicpatterns.com/.well-known/oauth-protected-resource (fetched 2026-08-19, HTTP 200; the path-append and path-insert forms both return 404) · retrieved 2026-08-19
- Live RFC 8414 authorization-server metadata — https://oauth.magicpatterns.com/.well-known/oauth-authorization-server and the OpenID configuration at the same host (both fetched 2026-08-19; both 404 on the MCP host) · retrieved 2026-08-19
- Live anonymous probe — 2026-08-19: an
initializerequest to the endpoint returns HTTP 401 withwww-authenticate: Bearer resource_metadata="https://mcp.magicpatterns.com/.well-known/oauth-protected-resource"· retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/088e0355-cb01-44fa-ba0b-23525fde8d5a (snapshot 2026-08-16) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Magic Patterns
- Tools
- 3
- Domain
- mcp.magicpatterns.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.