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

Source: https://elaichi.ai/connectors/medusa/

## Facts

| | |
| --- | --- |
| Application | Medusa |
| Category | Ecommerce |
| AI tools | 380 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Medusa is connected

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

## Connect Medusa in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Medusa.
2. Optionally set Share with, then press Connect.
3. Paste a Medusa API key. One person generates a token in Medusa and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Medusa tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Medusa MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Medusa MCP connector for Microsoft Copilot

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

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

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

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Medusa tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Medusa through Elaichi

### Launch a seasonal campaign with its promotions

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

### Open a claim after a damaged delivery

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

### Fix or cancel a claim raised in error

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

### See which sales channels each key serves

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

### Rotate a Medusa API key safely

Engineering. Create a fresh key, hand its sales channels across, then revoke or delete the old one, with each step recorded in the audit log.

### Review every live campaign before month end

Marketing. Ask for all Medusa campaigns ending this month with their promotions, then extend, rename or retire them without opening the admin.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Medusa connection?

Yes. One person connects Medusa with an API key and shares the connection with a team, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every campaign change or claim.

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

## All 380 Medusa tools

Every tool below is callable through https://api.elaichi.ai/mcp once Medusa is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Medusa API keys** (List). List API Keys. Retrieve a list of API keys. The API keys can be filtered by fields such as `id`. The API keys can also be sorted or paginated.
- **Create a Medusa API key** (Create). Create Api Key. Create a secret or publishable API key. A secret API key is used for admin authentication. A publishable API key is used by client applications to set the scope of the request.
- **Get single Medusa API key by ID** (Get). Get API Key. Retrieve an API key by its ID. You can expand the API key's relations or select the fields that should be returned using the query parameters.
- **Update a Medusa API key by ID** (Update). Update an API Key. Update an API key's details.
- **Delete a Medusa API key by ID** (Delete). Delete an Api Key. Delete a publishable or secret API key.
- **Medusa API keys revoke** (Revoke). Revoke API Key. Revokes an API key. If the API key is a secret, it can't be used for authentication anymore. If it's publishable, it can't be used by client applications.
- **Medusa API keys manage sales channels** (Action). Manage Sales Channels of a Publishable API Key. Manage the sales channels of a publishable API key, either to associate them or remove them from the API key.
- **List all Medusa campaigns** (List). List Campaigns. Retrieve a list of campaigns. The campaigns can be filtered by fields such as `q`, `campaign_identifier` and `budget`. The campaigns can also be sorted or paginated.
- **Create a Medusa campaign** (Create). Create Campaign. Create a campaign.
- **Get single Medusa campaign by ID** (Get). Get a Campaign. Retrieve a campaign by its ID. You can expand the campaign's relations or select the fields that should be returned using the query parameters.
- **Update a Medusa campaign by ID** (Update). Update a Campaign. Update a campaign's details.
- **Delete a Medusa campaign by ID** (Delete). Delete a Campaign. Delete a campaign by its ID. This doesn't delete promotions that belong to this campaign.
- **Medusa campaigns manage promotions** (Action). Manage the Promotions of a Campaign. Manage the promotions of a campaign, either by adding them or removing them from the campaign.
- **List all Medusa claims** (List). List Claims. Retrieve a list of claims. The claims can be filtered by fields such as `id`. The claims can also be sorted or paginated.
- **Create a Medusa claim** (Create). Create a Claim. Create a claim. The claim is still in the request state, and the changes are only applied on the order once the claim is confirmed.
- **Get single Medusa claim by ID** (Get). Get a Claim. Retrieve a claim by its ID. You can expand the claim's relations or select the fields that should be returned using the query parameters.
- **Medusa claims cancel** (Cancel). Cancel a Claim. Cancel a claim and its associated return.
- **Medusa claims add claim items** (Add). Add Claim Items to a Claim. Add order items to a claim as claim items. These claim items will have the action `WRITE_OFF_ITEM`.
- **Medusa claims update claim item** (Update). Update a Claim Item. Update an order item in a claim by the ID of the item's `WRITE_OFF_ITEM` action. Every item has an `actions` property, whose value is an array of actions. You can check the action's name using its `action` property, and use the value of the `id` property.
- **Medusa claims remove claim item** (Delete). Remove a Claim Item from a Claim. Remove an order item from a claim by the ID of the item's `WRITE_OFF_ITEM` action. Every item has an `actions` property, whose value is an array of actions. You can check the action's name using its `action` property, and use the value of the `id` property.
- **Medusa claims add inbound items** (Add). Add Inbound Items to a Claim. Add inbound (or return) items to a claim. These inbound items will have a `RETURN_ITEM` action.
- **Medusa claims update inbound item** (Update). Update Inbound Items of a Claim. Update an inbound (or return) item of a claim using the `ID` of the item's `RETURN_ITEM` action. Every item has an `actions` property, whose value is an array of actions. You can check the action's name using its `action` property, and use the value of the `id` property.
- **Medusa claims remove inbound item** (Delete). Remove an Inbound Item from Claim. Remove an inbound (or return) item from a claim using the `ID` of the item's `RETURN_ITEM` action. Every item has an `actions` property, whose value is an array of actions. You can check the action's name using its `action` property, and use the value of the `id` property.
- **Medusa claims add inbound shipping method** (Add). Add an Inbound Shipping Method to a Claim. Add an inbound (or return) shipping method to a claim. The inbound shipping method will have a `SHIPPING_ADD` action.
- **Medusa claims update inbound shipping method** (Update). Update Inbound Shipping Method of a Claim. Update the shipping method for returning items in the claim using the `ID` of the method's `SHIPPING_ADD` action. Every shipping method has an `actions` property, whose value is an array of actions. You can check the action's name using its `action` property, and use the value of the `id` property.
- **Medusa claims remove inbound shipping method** (Delete). Remove Inbound Shipping Method from Claim. Remove the shipping method for returning items in the claim using the `ID` of the method's `SHIPPING_ADD` action. Every shipping method has an `actions` property, whose value is an array of actions. You can check the action's name using its `action` property, and use the value of the `id` property.
- **Medusa claims add outbound items** (Add). Add Outbound Items to a Claim. Add outbound (or new) items to a claim. These outbound items will have an `ITEM_ADD` action.
- **Medusa claims update outbound item** (Update). Update Outbound Item of a Claim. Update an outbound (or new) item of a claim using the `ID` of the item's `ITEM_ADD` action. Every item has an `actions` property, whose value is an array of actions. You can check the action's name using its `action` property, and use the value of the `id` property.
- **Medusa claims remove outbound item** (Delete). Remove an Outbound Item from Claim. Remove an outbound (or new) item from a claim using the `ID` of the item's `ITEM_ADD` action. Every item has an `actions` property, whose value is an array of actions. You can check the action's name using its `action` property, and use the value of the `id` property.
- **Medusa claims add outbound shipping method** (Add). Add Outbound Shipping Methods to a Claim. Add an outbound shipping method to a claim. The outbound shipping method will have a `SHIPPING_ADD` action.
- **Medusa claims update outbound shipping method** (Update). Update Outbound Shipping Method of a Claim. Update the shipping method for delivering outbound items in a claim using the `ID` of the method's `SHIPPING_ADD` action. Every shipping method has an `actions` property, whose value is an array of actions. You can check the action's name using its `action` property, and use the value of the `id` property.
- **Medusa claims remove outbound shipping method** (Delete). Remove Outbound Shipping Method from Claim. Remove the shipping method for delivering outbound items in the claim using the `ID` of the method's `SHIPPING_ADD` action. Every shipping method has an `actions` property, whose value is an array of actions. You can check the action's name using its `action` property, and use the value of the `id` property.
- **Medusa claims confirm request** (Action). Confirm a Claim Request. Confirm a claim request, applying its changes on the associated order.
- **Medusa claims cancel request** (Cancel). Cancel Claim Request. Cancel a requested claim.
- **List all Medusa collections** (List). List Collections. Retrieve a list of collections. The collections can be filtered by fields such as `id`. The collections can also be sorted or paginated.
- **Create a Medusa collection** (Create). Create Collection. Create a collection.
- **Get single Medusa collection by ID** (Get). Get a Collection. Retrieve a collection by its ID. You can expand the collection's relations or select the fields that should be returned using the query parameters.
- **Update a Medusa collection by ID** (Update). Update a Collection. Update a collection's details.
- **Delete a Medusa collection by ID** (Delete). Delete a Collection. Delete a product collection.
- **Medusa collections manage products** (Action). Manage Products of a Collection. Manage the products of a collection by adding or removing them from the collection.
- **List all Medusa currencies** (List). List Currencies. Retrieve a list of currencies. The currencies can be filtered by fields such as `code` or `q`. The currencies can also be sorted or paginated.
- **Get single Medusa currency by ID** (Get). Get a Currency. Retrieve a currency by its code. You can expand the currency's relations or select the fields that should be returned using the query parameters.
- **List all Medusa customer groups** (List). List Customer Groups. Retrieve a list of customer groups. The customer groups can be filtered by fields such as `id`. The customer groups can also be sorted or paginated.
- **Create a Medusa customer group** (Create). Create Customer Group. Create a customer group.
- **Get single Medusa customer group by ID** (Get). Get a Customer Group. Retrieve a customer group by its ID. You can expand the customer group's relations or select the fields that should be returned.
- **Update a Medusa customer group by ID** (Update). Update a Customer Group. Update a customer group's details.
- **Delete a Medusa customer group by ID** (Delete). Delete a Customer Group. Delete a customer group. Customers in the group aren't deleted.
- **Medusa customer groups manage customers** (Action). Manage Customers of a Customer Group. Manage the customers of a group to add or remove them from the group.
- **List all Medusa customers** (List). List Customers. Retrieve a list of customers. The customers can be filtered by fields such as `id`. The customers can also be sorted or paginated.
- **Create a Medusa customer** (Create). Create Customer. Create a customer.
- ...and 330 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
