Medusa MCP connector
Connect Medusa to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can list, create and update your campaigns, promotions, claims, sales channels and API keys, each person inside their own access, every action logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Which campaigns are live right now and what promotions do they include?
Working in Medusa with Elaichi
-
List all Medusa API keys
-
Get single Medusa API key by ID
-
List all Medusa campaigns
How to connect Medusa to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Medusa 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.
Medusa 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.
Medusa 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.
Medusa 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.
Medusa 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 Medusa 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 Medusa through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Medusa is logged.
-
Marketing
Launch a seasonal campaign with its promotions
Create the campaign in Medusa, set its dates and budget, and attach the promotions that belong to it, all from one ask. Change a promotion later and the campaign keeps up.
-
Support
Open a claim after a damaged delivery
When a customer reports a broken item, open the claim against their Medusa order, add the affected items and the inbound items coming back, and set the return shipping method.
-
Support
Fix or cancel a claim raised in error
Pull up a claim by its ID, swap out the wrong item, adjust quantities, or cancel the claim outright when the customer changes their mind.
-
Operations
See which sales channels each key serves
List every Medusa API key, check the sales channels it is attached to, and move a channel between keys when a storefront or marketplace changes hands.
-
Engineering
Rotate a Medusa API key safely
Create a fresh key, hand its sales channels across, then revoke or delete the old one, with each step recorded in the audit log.
-
Marketing
Review every live campaign before month end
Ask for all Medusa campaigns ending this month with their promotions, then extend, rename or retire them without opening the admin.
Try asking
- “Which campaigns are live right now and what promotions do they include?”
- “Open a claim for order 1042 with one damaged inbound item.”
- “List API keys that still serve the wholesale sales channel.”
What connecting Medusa gets you
6 screens from Elaichi, each doing one job for your Medusa account.
Ask Elaichi to work across your apps.
Which campaigns are live right now and what promotions do they include?
Open a claim for order 1042 with one damaged inbound item.
List API keys that still serve the wholesale sales channel.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about campaigns and claims in plain language.
Three starter prompts pull live answers from your Medusa campaigns, promotions and claims.
Copy the endpoint
AI apps
One Medusa endpoint, every MCP client you use.
Claude, ChatGPT and Cursor connect through one org endpoint, no SDK and no shared API key.
Tool catalog
380 Medusa tools, ready with no custom code.
Campaigns, promotions, claims, sales channels and API keys, each covered by list, create, update and delete.
Toolboxes
Every team gets its own Medusa toolbox.
Marketing works campaigns, Support works claims, each from a toolbox scoped to that team.
Shared connections
Teammates work through Medusa without seeing a credential.
One person connects the Medusa account, then shares it with teams and members.
Audit log
Know who changed which Medusa claim, and when.
Every call lands in an append-only log with who, what, type and resource.
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.
Medusa digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch campaigns
Medusa
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
Medusa
Queued
Workflows
A schedule starts Medusa work end to end.
New claims are fetched, grouped and drafted into a digest, approved, then posted back to Medusa.
Medusa health
Refreshed 4 minutes ago · every 15 minutes · from the campaigns collection
Campaigns
1,284 ↓ 12%
Promotions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Campaigns created
Last 14 days
By team
Share of activity
Marketing 34%
Support 27%
Store US 21%
Store EU 18%
Collections and dashboards
Medusa health numbers, computed without asking a model.
Four metrics, fourteen days of claims created and a breakdown by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Medusa
All three can connect Medusa 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 Medusa tools | Allow or restrict single Medusa 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 Medusa 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.
Medusa tools for your AI agents
380 tools are ready to call through Elaichi's MCP endpoint the moment you connect Medusa, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 320 of 380 Medusa tools here. Connect Medusa and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect Medusa to Claude?
Two steps. In Elaichi, add the Medusa connector and paste in a Medusa API key when asked, there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and Medusa is ready to use.
Does Medusa work with ChatGPT and Cursor as well as Claude?
Yes. Once Medusa is connected in Elaichi, Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent all use the same endpoint, https://api.elaichi.ai/mcp. You connect Medusa once and every client sees it.
What can an AI agent actually do with my Medusa data?
It can list, create, update and delete your Medusa campaigns, attach promotions to them, open claims on orders and manage the claim items, inbound items and return shipping, and manage API keys and the sales channels they serve. You ask in plain language, such as open a claim for this order or list campaigns ending in June. Short, concrete asks work better than long sentences.
Does connecting Medusa give the AI access to my whole store?
No. Every call into Medusa runs under the person who signed in to Elaichi, so an agent can only reach what that person can already reach. Roles and restrictions in Elaichi can narrow that further, for example to campaigns only, and they can never widen it beyond what the Medusa API key allows.
Can I stop an agent from deleting or changing things in Medusa?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting Medusa campaigns or cancelling claims for a role or for one person while leaving listing and creating open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Medusa connection when someone leaves?
Offboarding that person in Elaichi ends their access to Medusa at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A shared Medusa connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Medusa once in Elaichi removes it from every client.
Does the Medusa MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Medusa 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 Medusa?
Yes. Both let Claude, ChatGPT or Cursor use Medusa. 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 Medusa call.
How is Elaichi different from Composio for Medusa?
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 Medusa: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Medusa 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