Magic Patterns MCP connector
Connect Magic Patterns to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, or the Elaichi Agent can create designs and slide decks, check design status, manage design systems, and read or write artifact files, all inside each person's own access.
- Connects over OAuth
- Free 14-day trial
- No credit card
Create a pricing page design using our main design system.
Working in Magic Patterns with Elaichi
-
List design systems
-
Get editor ID from URL
-
Get design status
How to connect Magic Patterns to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Magic Patterns MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Magic Patterns MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Magic Patterns MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Magic Patterns MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Magic Patterns MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Magic Patterns to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Magic Patterns through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Magic Patterns is logged.
-
Product
Turn a feature brief into a first design
Paste the brief and ask for a screen built on the team's design system. Check the status while it generates and send a follow-up prompt to adjust it.
-
Design
Keep every new screen on the design system
Ask which design systems exist, read their files, and have new designs created against the right one. Publish updates to the design system once the team signs off.
-
Marketing
Draft a landing page from a campaign brief
Describe the campaign and get a landing page design back, then iterate with short prompts until the copy and layout match the launch.
-
Sales
Build a pitch deck without leaving the chat
Ask for a slide deck for a specific prospect and get a draft ready to refine, with the version history there if you need to go back.
-
Engineering
Pull generated files straight into the codebase
Read the files behind an artifact, write changes back, and publish when it is ready to share with the rest of the team.
-
Founders
Explore several directions before you commit
Create an inspiration document, add a few variants of the same idea, and update or clear them as the direction becomes clear.
Try asking
- “Create a pricing page design using our main design system.”
- “What is the status of the onboarding flow design?”
- “Make a five slide deck for the Q3 product launch.”
What connecting Magic Patterns gets you
6 screens from Elaichi, each doing one job for your Magic Patterns account.
Ask Elaichi to work across your apps.
Create a pricing page design using our main design system.
What is the status of the onboarding flow design?
Make a five slide deck for the Q3 product launch.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Magic Patterns designs in plain words.
Check design status, read version history, or request a new screen without leaving the chat.
Copy the endpoint
AI apps
One endpoint brings Magic Patterns to every client.
Claude, ChatGPT, Cursor, Microsoft Copilot, and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
23 Magic Patterns tools, no code to write.
Designs, slide decks, artifacts, design systems, and inspiration documents, covered out of the box.
Toolboxes
Every team gets its own Magic Patterns toolbox.
Scope what Design, Product, and Marketing can reach, one toolbox per team.
Shared connections
Share one Magic Patterns connection, keep credentials private.
Teammates create designs through a shared account and never see a token or password.
Audit log
Every design change lands in the log.
See who created, published, or edited which artifact, and when it happened.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Magic Patterns digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch designs
Magic Patterns
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Magic Patterns
Queued
Workflows
A schedule starts the work, a person approves.
New designs are fetched, grouped, drafted into a digest, approved, and posted back to Magic Patterns.
Magic Patterns health
Refreshed 4 minutes ago · every 15 minutes · from the designs collection
Designs
1,284 ↓ 12%
Design systems
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Designs created
Last 14 days
By team
Share of activity
Design 34%
Product 27%
Marketing 21%
Sales 18%
Collections and dashboards
Magic Patterns health, computed without a model.
Designs created over 14 days, broken down by team, refreshed on a schedule.
Why connect Magic Patterns' MCP server through Elaichi
Magic Patterns builds and runs this MCP server. Elaichi sits in front of it, so Magic Patterns' tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Magic Patterns' server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Magic Patterns' tools at the same Elaichi address as every other connected app. Nobody adds Magic Patterns' server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Magic Patterns sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Magic Patterns' server. By default, a tool Magic Patterns does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Magic Patterns
Magic Patterns builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Magic Patterns team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Magic Patterns
All three can connect Magic Patterns to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Magic Patterns tools | Allow or restrict single Magic Patterns tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Magic Patterns call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Magic Patterns tools for your AI agents
23 tools are ready to call through Elaichi's MCP endpoint the moment you connect Magic Patterns, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Magic Patterns builds and runs these tools.
No tools match your search.
Questions, answered
How do I connect Magic Patterns to Claude?
Connect Magic Patterns in Elaichi first, where you sign in to Magic Patterns over OAuth and approve access, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in to Elaichi and Magic Patterns is ready to use.
Does Magic Patterns work with ChatGPT and Cursor as well as Claude?
Yes. Once Magic Patterns is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Magic Patterns once and every client picks it up.
What can an AI agent actually do with my Magic Patterns data?
An agent connected to Magic Patterns can create designs and slide decks from a description, check whether a design is finished, send follow-up prompts, and read the recent message and version history. It can also list and read your design systems, read or write the files behind an artifact, publish artifacts and design systems, and manage variants in an inspiration document. Short, concrete asks such as a single screen with a named design system work better than long paragraphs.
Does connecting Magic Patterns give the AI access to every design in my workspace?
No. Every call to Magic Patterns runs as the person who signed in, so the agent sees only the designs, design systems, and artifacts that person can already reach in Magic Patterns. Elaichi can narrow that access further with roles and restrictions, and it never widens it.
Can I stop an agent from publishing or changing things in Magic Patterns?
Yes. Restrictions in Elaichi apply per action, so you can allow reading designs and design systems while restricting writes to artifact files or publishing. A restricted Magic Patterns action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Magic Patterns connection when someone leaves?
Offboarding a person in Elaichi ends their access to Magic Patterns at once, across every client they used. A connection shared with a team keeps working for everyone else. Disconnecting Magic Patterns once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.
Does the Magic Patterns MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Magic Patterns is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Magic Patterns?
Yes. Both let Claude, ChatGPT or Cursor use Magic Patterns. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Magic Patterns call.
How is Elaichi different from Composio for Magic Patterns?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Magic Patterns: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Magic Patterns in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot