# Fulfil MCP connector

Connecting Fulfil to Elaichi lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent look up and update Fulfil contacts, products and customer shipments as the person who signed in, with every action logged.

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

## Facts

| | |
| --- | --- |
| Application | Fulfil |
| Category | Ecommerce |
| AI tools | 54 |
| 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 Fulfil is connected

- Where is the customer shipment for Dana Reyes's order?
- Create a product called Linen Tote in navy
- Update the address on the contact for Harbor Supply Co

## Connect Fulfil in Elaichi

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

1. Open Connections, choose Add connection, and pick Fulfil.
2. Optionally set Share with, then press Connect.
3. Paste a Fulfil API key. One person generates a token in Fulfil 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 Fulfil tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

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

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

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

## Fulfil 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 Fulfil 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 Fulfil 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 Fulfil through Elaichi

### Find where a customer's shipment is

Support. Ask for the customer shipment behind an order and get its status straight from Fulfil, without leaving the chat where the customer's question came in.

### Update shipments in bulk after a carrier change

Operations. Tell the agent which customer shipments moved to a new carrier and have them all updated in Fulfil together, rather than opening each one.

### Add a new product before the launch

Merchandising. Describe the product and have it created in Fulfil with its code and details, then correct a detail later with one more ask.

### Catch a contact up after a call

Wholesale. Update a wholesale buyer's contact record in Fulfil with the new address, phone or notes from the call, in the words you already typed.

### Count what is waiting to ship today

Warehouse. Ask how many customer shipments are in each state this morning and get the counts from Fulfil before the shift starts.

### Clean up duplicate customer contacts

Ecommerce. List contacts that look like the same person, pick the one to keep, and delete the stray records from Fulfil in a single conversation.

## Elaichi vs Zapier MCP vs Composio for Fulfil

All three can connect Fulfil 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 Fulfil tools | Allow or restrict single Fulfil 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 Fulfil 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 Fulfil to Claude?

Connect Fulfil in Elaichi by pasting a Fulfil API key, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register in Fulfil and no client ID or secret to generate. Once the endpoint is added, Claude signs you in through Elaichi and can work with your Fulfil contacts, products and customer shipments.

### Does Fulfil work with ChatGPT and Cursor as well as Claude?

Yes. A Fulfil connection in Elaichi is reached through the same endpoint, https://api.elaichi.ai/mcp, from Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Fulfil once and every client you use picks it up.

### What can an AI agent actually do with my Fulfil data?

It can look up, count, create, update and delete Fulfil contacts, products and customer shipments, and update many contacts or shipments at once. In practice that means asking where a customer's shipment is, adding a product before launch, or fixing a buyer's address after a call. Short, concrete asks work better than long sentences.

### Does connecting Fulfil give the AI everything in my Fulfil account?

No. Every call runs as the person who signed in to Elaichi, so an agent sees and changes only the Fulfil contacts, products and customer shipments that person could already reach. Elaichi can narrow that further with roles and restrictions, and it never widens access beyond what Fulfil already allows.

### Can my team share one Fulfil connection?

Yes. One person connects Fulfil with an API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who looked up a shipment or changed a product.

### Can I stop an agent from deleting or changing things in Fulfil?

Yes. Restrictions in Elaichi apply per action, so you can restrict deleting Fulfil contacts or updating customer shipments for a role or for one person while leaving lookups 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 Fulfil connection when someone leaves?

Offboarding the person in Elaichi ends their access to Fulfil through every client at once. A Fulfil connection they shared keeps working for everyone else on the team. If you disconnect Fulfil in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent in one step.

### Does the Fulfil MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Fulfil 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 Fulfil?

Yes. Both let Claude, ChatGPT or Cursor use Fulfil. 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 Fulfil call.

### How is Elaichi different from Composio for Fulfil?

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 Fulfil: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 54 Fulfil tools

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

- **List all Fulfil contact counts** (List). Count contact (customer, supplier or other party)s matching an optional where filter. The count is in result.
- **List all Fulfil contacts** (List). List contact (customer, supplier or other party)s with Fulfil's find method: filter with where, pick fields, sort with ordering. The connector follows the cursor through every page.
- **Get single Fulfil contact by ID** (Get). Get one contact (customer, supplier or other party) by id (Fulfil's serialize: the server's summary of the record). For specific fields use list with where {"id": &lt;id&gt;} and fields. Required: id.
- **Create a Fulfil contact** (Create). Create one or more contact (customer, supplier or other party)s in a single call. Send the records as params.vlist (an array, even for one record); nested lines are allowed. Returns the new ids. Required: params.
- **Update a Fulfil contact by ID** (Update). Update data fields of one contact (customer, supplier or other party). Send the new values as values; change state with execute (a workflow method such as confirm or process), never by writing the state field. Required: id, values.
- **Fulfil contacts bulk update** (Update). Write the same values to several contact (customer, supplier or other party)s in one call: send params.ids and params.values. Required: params.
- **Delete a Fulfil contact by ID** (Delete). Permanently delete one contact (customer, supplier or other party). Required: id.
- **Fulfil contacts execute** (Execute). Call a workflow or other model method on contact (customer, supplier or other party)s, e.g. method=confirm or process with params.ids. describe_model (model_schemas.get) lists a model's methods and their parameters. Required: method.
- **List all Fulfil customer shipment counts** (List). Count customer shipments matching an optional where filter. The count is in result.
- **List all Fulfil customer shipments** (List). List customer shipments with Fulfil's find method: filter with where, pick fields, sort with ordering. The connector follows the cursor through every page.
- **Get single Fulfil customer shipment by ID** (Get). Get one customer shipment by id (Fulfil's serialize: the server's summary of the record). For specific fields use list with where {"id": &lt;id&gt;} and fields. Required: id.
- **Create a Fulfil customer shipment** (Create). Create one or more customer shipments in a single call. Send the records as params.vlist (an array, even for one record); nested lines are allowed. Returns the new ids. Required: params.
- **Update a Fulfil customer shipment by ID** (Update). Update data fields of one customer shipment. Send the new values as values; change state with execute (a workflow method such as confirm or process), never by writing the state field. Required: id, values.
- **Fulfil customer shipments bulk update** (Update). Write the same values to several customer shipments in one call: send params.ids and params.values. Required: params.
- **Delete a Fulfil customer shipment by ID** (Delete). Permanently delete one customer shipment. Required: id.
- **Fulfil customer shipments execute** (Execute). Call a workflow or other model method on customer shipments, e.g. method=confirm or process with params.ids. describe_model (model_schemas.get) lists a model's methods and their parameters. Required: method.
- **List all Fulfil me** (List). The user this API key acts as, with its scopes (system.whoami). The connector calls it to check the key when an account connects.
- **Get single Fulfil model schema by ID** (Get). Describe one model: its fields, types, allowed values and methods with their parameters. The id is the model name, e.g. sales_order. Required: id.
- **List all Fulfil models** (List). List the Fulfil models this API key can reach (v3 names such as sales_order). Use the names as model in the records methods.
- **List all Fulfil product counts** (List). Count products matching an optional where filter. The count is in result.
- **List all Fulfil products** (List). List products with Fulfil's find method: filter with where, pick fields, sort with ordering. The connector follows the cursor through every page.
- **Get single Fulfil product by ID** (Get). Get one product by id (Fulfil's serialize: the server's summary of the record). For specific fields use list with where {"id": &lt;id&gt;} and fields. Required: id.
- **Create a Fulfil product** (Create). Create one or more products in a single call. Send the records as params.vlist (an array, even for one record); nested lines are allowed. Returns the new ids. Required: params.
- **Update a Fulfil product by ID** (Update). Update data fields of one product. Send the new values as values; change state with execute (a workflow method such as confirm or process), never by writing the state field. Required: id, values.
- **Fulfil products bulk update** (Update). Write the same values to several products in one call: send params.ids and params.values. Required: params.
- **Delete a Fulfil product by ID** (Delete). Permanently delete one product. Required: id.
- **Fulfil products execute** (Execute). Call a workflow or other model method on products, e.g. method=confirm or process with params.ids. describe_model (model_schemas.get) lists a model's methods and their parameters. Required: method.
- **List all Fulfil purchase order counts** (List). Count purchase orders matching an optional where filter. The count is in result.
- **List all Fulfil purchase orders** (List). List purchase orders with Fulfil's find method: filter with where, pick fields, sort with ordering. The connector follows the cursor through every page.
- **Get single Fulfil purchase order by ID** (Get). Get one purchase order by id (Fulfil's serialize: the server's summary of the record). For specific fields use list with where {"id": &lt;id&gt;} and fields. Required: id.
- **Create a Fulfil purchase order** (Create). Create one or more purchase orders in a single call. Send the records as params.vlist (an array, even for one record); nested lines are allowed. Returns the new ids. Required: params.
- **Update a Fulfil purchase order by ID** (Update). Update data fields of one purchase order. Send the new values as values; change state with execute (a workflow method such as confirm or process), never by writing the state field. Required: id, values.
- **Fulfil purchase orders bulk update** (Update). Write the same values to several purchase orders in one call: send params.ids and params.values. Required: params.
- **Delete a Fulfil purchase order by ID** (Delete). Permanently delete one purchase order. Required: id.
- **Fulfil purchase orders execute** (Execute). Call a workflow or other model method on purchase orders, e.g. method=confirm or process with params.ids. describe_model (model_schemas.get) lists a model's methods and their parameters. Required: method.
- **List all Fulfil record counts** (List). Count records of the given model matching an optional where filter. The count is in result. Required: model.
- **List all Fulfil records** (List). List records of the given model with Fulfil's find method: filter with where, pick fields, sort with ordering. The connector follows the cursor through every page. Required: model.
- **Get single Fulfil record by ID** (Get). Get one record by id (Fulfil's serialize: the server's summary of the record). For specific fields use list with where {"id": &lt;id&gt;} and fields. Required: id, model.
- **Create a Fulfil record** (Create). Create one or more records of the given model in a single call. Send the records as params.vlist (an array, even for one record); nested lines are allowed. Returns the new ids. Required: model, params.
- **Update a Fulfil record by ID** (Update). Update data fields of one record. Send the new values as values; change state with execute (a workflow method such as confirm or process), never by writing the state field. Required: id, model, values.
- **Fulfil records bulk update** (Update). Write the same values to several records of the given model in one call: send params.ids and params.values. Required: model, params.
- **Delete a Fulfil record by ID** (Delete). Permanently delete one record. Required: id, model.
- **Fulfil records execute** (Execute). Call a workflow or other model method on records of the given model, e.g. method=confirm or process with params.ids. describe_model (model_schemas.get) lists a model's methods and their parameters. Required: model, method.
- **Get single Fulfil report schema by ID** (Get). Describe one report's parameters. The id is the report name. Required: id.
- **List all Fulfil reports** (List). List the reports available in the workspace.
- **Fulfil reports execute** (Execute). Run a report: report is its name (from reports.list), params its parameters (report_schemas.get lists them). Required: report.
- **List all Fulfil sales order counts** (List). Count sales orders matching an optional where filter. The count is in result.
- **List all Fulfil sales orders** (List). List sales orders with Fulfil's find method: filter with where, pick fields, sort with ordering. The connector follows the cursor through every page.
- **Get single Fulfil sales order by ID** (Get). Get one sales order by id (Fulfil's serialize: the server's summary of the record). For specific fields use list with where {"id": &lt;id&gt;} and fields. Required: id.
- **Create a Fulfil sales order** (Create). Create one or more sales orders in a single call. Send the records as params.vlist (an array, even for one record); nested lines are allowed. Returns the new ids. Required: params.
- ...and 4 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
