Skip to content

Moda MCP connector

Connect Moda to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, 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.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Resize the spring launch design for Instagram, LinkedIn and email.

Working in Moda with Elaichi

  • Looked in Moda
Ask anything…
Governance / Audit log Last 24 hours
Moda Looked in Moda Emily Carter · Claude · 9:41 AM Done
Moda Looked in Moda Megan Brooks · ChatGPT · 9:38 AM Done
Moda Looked in Moda Ryan Hayes · Cursor · 9:35 AM Done

How to connect Moda to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Moda MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 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.

Moda MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Moda MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Moda MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 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 Moda to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Moda through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Moda is logged.

  • 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.”

What connecting Moda gets you

5 screens from Elaichi, each doing one job for your Moda account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask for a design, get it in Moda.

Plain questions turn into live Moda designs, exports and brand kit updates.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Moda in Claude, ChatGPT, Cursor and Microsoft Copilot at once.

One governed endpoint over OAuth, no SDK, no shared API key, everyone signed in as themselves.

ElaichiToolboxes
Name Source template Tools Created

Marketing toolbox

Moda · campaign designs and exports

Moda starter 18 Mar 4, 2026

Design toolbox

Moda · brand kits and assets

— 9 Mar 2, 2026

Social toolbox

Moda · post templates and resizes

— 24 Feb 27, 2026

Sales toolbox

Moda · pitch decks and one-pagers

Moda starter 6 Feb 19, 2026

People toolbox

Moda · onboarding and internal comms

— 31 Jan 30, 2026

Events toolbox

Moda · signage and badges

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Moda toolbox.

Marketing, Design, Social and Sales each see only the Moda tools their work needs.

ElaichiConnections
Connection Scope Status Access
MO

Moda (Marketing)

Connected by Emily Carter

Personal • Active 1 team · 6 members
MO

Moda (Brand)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
MO

Moda (Social)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
MO

Moda (Sales enablement)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
MO

Moda (People)

Connected by Ryan Hayes

Personal • Active Not shared
MO

Moda (Events)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share Moda access, never share the login.

One person connects Moda, teams work through it, nobody else sees a credential.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Moda Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Moda Designs Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Moda Designs List Toolbox

Audit log

Every Moda change names who made it.

When, who, what happened and which design, in an append-only log.

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.

Moda digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch designs

    Moda

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Moda

    Queued

Workflows

A schedule starts the Moda work itself.

New Moda designs are fetched, grouped, drafted into a digest, approved, then posted back to Moda.

Moda health

Refreshed 4 minutes ago · every 15 minutes · from the designs collection

Live

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%

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.

Why connect Moda's MCP server through Elaichi

Moda builds and runs this MCP server. Elaichi sits in front of it, so Moda's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Moda's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Moda's tools at the same Elaichi address as every other connected app. Nobody adds Moda's 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 Moda 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 Moda's server. By default, a tool Moda 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 Moda

    Moda builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Moda team.

    [email protected]

Why run a vendor's MCP server through Elaichi →

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Moda, by what to check
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 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.

Questions, answered

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, Microsoft Copilot, 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 role, and it can never widen it beyond what Moda itself allows.

Can my team share one Moda connection?

Yes. One person connects Moda in Elaichi and shares the connection with a team, and nobody else ever handles a Moda login or credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every design that was created, edited or exported.

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 restricting edits, deletions or brand kit changes for a given role. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.

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, Microsoft Copilot 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, 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 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 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