Moda MCP connector
Connect Moda to Elaichi and Claude, ChatGPT, Cursor, or the Elaichi Agent can create and edit Moda designs, export canvases, keep brand kits and assets in order, and generate images, each person working inside their own Moda access.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Moda to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Moda once
-
Open Connections, choose Add connection, and pick Moda.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Moda. Moda's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Moda 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.
Moda 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 today. The plugin directory lives at chatgpt.com/plugins.
Moda 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.
Connect Moda 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.
Use cases
What teams do with Moda through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Turn one campaign design into every size
Ask for the launch design to be resized for Instagram, LinkedIn, email and the website, and have each version saved back in Moda ready to review.
-
Design
Keep the brand kit current
Add the new logo files, colors and fonts to the Moda brand kit once, then ask which designs still use the old versions.
-
Social
Draft a week of posts from one brief
Paste the week's messaging and get seven Moda canvases in the right templates, with generated images where no photo exists yet.
-
Sales
Build a pitch deck in brand colors
Describe the customer and the offer, and get a Moda deck built from the approved template, exported as a PDF for the call.
-
People
Make the onboarding pack match the brand
Update the welcome guide, badge and desk card designs in Moda whenever the brand kit changes, without redoing each file by hand.
-
Events
Export signage and badges ready to print
Ask for every design in the conference folder to be exported at print size, and get the files back in one go.
Try asking
- “Resize the spring launch design for Instagram, LinkedIn and email.”
- “Export the Q3 pitch canvas as a PDF for sales.”
- “Add the new logo and colors to the brand kit.”
Compare
Elaichi vs Zapier MCP vs Composio for Moda
All three can connect Moda 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 Moda tools | Allow or restrict single Moda 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 Moda 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 | $15 per user per month. | 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.
See it in Elaichi
What connecting Moda gets you
5 screens from the product, each doing one job for your Moda account.
The agent
Ask for a design, get it in Moda.
Plain questions turn into live Moda designs, exports and brand kit updates.
- designs
- canvases
- brand kits
- assets
Ask Elaichi to work across your apps.
Resize the spring launch design for Instagram, LinkedIn and email.
Export the Q3 pitch canvas as a PDF for sales.
Add the new logo and colors to the brand kit.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Moda in Claude, ChatGPT and Cursor at once.
One governed endpoint over OAuth, no SDK, no shared API key, everyone signed in as themselves.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Moda toolbox.
Marketing, Design, Social and Sales each see only the Moda tools their work needs.
- Marketing
- Design
- Social
- Sales
ElaichiToolboxesShared connections
Share Moda access, never share the login.
One person connects Moda, teams work through it, nobody else sees a credential.
- Marketing
- Brand
- Social
- Sales enablement
ElaichiConnectionsAudit log
Every Moda change names who made it.
When, who, what happened and which design, in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the Moda work itself.
New Moda designs are fetched, grouped, drafted into a digest, approved, then posted back to Moda.
Moda digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch designs
Moda
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 Michael Brennan
Approve Deny -
Post the digest
Moda
Queued
Collections and dashboards
Moda numbers refresh without anyone asking.
Designs created over 14 days, four live metrics, and a breakdown by team, no model involved.
Moda health
Refreshed 4 minutes ago · every 15 minutes · from the designs collection
Designs
1,284 ↓ 12%
Canvases
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Designs created
Last 14 days
By team
Share of activity
Marketing 34%
Brand 27%
Social 21%
Sales enablement 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Moda to Claude?
Connect Moda in Elaichi by signing in to your Moda account through its normal OAuth screen, the same login you use every day. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the address. From then on Claude can work with your Moda designs, canvases and brand kits.
Does Moda work with ChatGPT and Cursor as well as Claude?
Yes. Once Moda is connected in Elaichi, the same address, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Moda once and every client you use picks it up.
What can an AI agent actually do with my Moda data?
An agent can create and edit Moda designs and canvases, export them in the sizes and formats you ask for, add logos, colors and fonts to a brand kit, organize assets, and generate or edit images for a design. Exactly what is available depends on what your own Moda account has set up. Short, concrete asks such as resize this design for LinkedIn work better than long paragraphs.
Does connecting Moda give the AI access to every design in my workspace?
No. Every call to Moda runs as the person who signed in, so the agent can only reach the Moda designs, brand kits and assets that person can already open. Elaichi can narrow that access further for a team or a role, and it can never widen it beyond what Moda itself allows.
Can I stop an agent from deleting or changing things in Moda?
Yes. Restrictions in Elaichi apply per action, so you can allow reading and exporting Moda designs while blocking edits, deletions or brand kit changes for a given team. A restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.
What happens to a Moda connection when someone leaves?
Offboarding that person in Elaichi ends their access to Moda through every client at once. If they connected a shared Moda account, the connection keeps working for everyone else on the team. Disconnecting Moda once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Moda MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Moda 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, 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 Moda?
Yes. Both let Claude, ChatGPT or Cursor use Moda. 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 Moda call.
How is Elaichi different from Composio for Moda?
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 Moda: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Moda in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.