# Monta MCP connector

The Monta connector brings orders, parcels, batches and inbound forecasts into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person asks about Monta fulfillment in plain language inside their own access.

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

## Facts

| | |
| --- | --- |
| Application | Monta |
| Category | Ecommerce |
| AI tools | 100 |
| 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 Monta is connected

- Show me the events for order 48213 and where it is now
- Which inbound forecasts are still waiting for approval this week?
- List the parcels created for yesterday's order batch

## Connect Monta in Elaichi

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

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

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

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

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

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

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

### Find out where an order stands

Operations. Ask what has happened to an order and get the Monta order events and event feed read back in plain words, so you know whether it is picked, packed or shipped without opening the warehouse screen.

### Tell the warehouse what is arriving

Supply chain. Create an inbound forecast in Monta for a purchase order so the warehouse knows which items and quantities to expect, then update it when the supplier moves the delivery date.

### Approve a week of inbound forecasts at once

Warehouse. List the open inbound forecasts, group them by supplier or delivery window, and approve the whole set in one go instead of clicking through them one at a time.

### Check what was packed before replying

Customer service. See which parcels were created for an order and which order lines were deleted, so the answer you give a customer matches what actually left the Monta warehouse.

### Clean up an address before it ships

Ecommerce. Run a shipping address through Monta's address validation before the order goes into a batch, and catch the missing house number while it is still cheap to fix.

### Anonymize an order on request

Compliance. When a customer asks for their details to be removed, create an order anonymization in Monta, with the audit log recording who did it and when.

## Elaichi vs Zapier MCP vs Composio for Monta

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

Two steps. In Elaichi, add the Monta connector and paste in your Monta API key, which is the only sign-in step, since there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude then signs you in through Elaichi and your Monta orders, parcels, batches and inbound forecasts are available in the chat.

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

Yes. One Monta connection in Elaichi is reached through the same endpoint, https://api.elaichi.ai/mcp, from Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Monta once, and every client your team uses picks it up.

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

It can tell you where an order is by reading its Monta events and event feed, list the parcels and deleted lines on an order, look up a batch, and create, update, approve or delete inbound forecasts and forecast groups. It can also validate a shipping address, list inbounds and health checks, and create an order anonymization when a customer asks. Short, concrete asks such as the events for one order number work better than a long paragraph.

### Does connecting Monta give the AI everything in my warehouse?

No. Every call to Monta runs with the access of the person who signed in to Elaichi, so an agent sees the orders, inbounds and forecasts that person could already see. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what the Monta API key allows.

### Can my team share one Monta connection?

Yes. One person connects Monta with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in as themselves, so the audit log names the actual person who checked an order or approved an inbound forecast.

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

Yes. Restrictions in Elaichi work per action, set on a role or on one person, so you can allow reading Monta orders and events while restricting deleting inbound forecasts or creating anonymizations. 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 Monta connection when someone leaves?

Offboarding the person in Elaichi ends their access to Monta at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A shared Monta connection keeps working for everyone else on the team. If you want Monta gone entirely, disconnecting it once in Elaichi removes it from every client.

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

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

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

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

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

## All 100 Monta tools

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

- **Monta addresses validate** (Validate). Validate a delivery address. Required: City, CountryCode, Street.
- **Get single Monta batch by ID** (Get). Get batch with guid. Required: id.
- **List all Monta health checks** (List). Check that the Monta API is up.
- **List all Monta inbound forecast events** (List). List inbound forecast events after a given event id. Required: since_id.
- **List all Monta inbound forecast group labels** (List). Download a delivery label for a forecastgroup based on reference. Required: reference. Returns a file (PDF), not JSON.
- **Get single Monta inbound forecast group by ID** (Get). Get an entire inbound forecast group by its reference or by its unique id (GUID). Required: id.
- **Update a Monta inbound forecast group by ID** (Update). Update an existing inbound forecast group based on reference. Required: id.
- **Delete a Monta inbound forecast group by ID** (Delete). Delete an entire inbound forecast group, including inbound forecasts. Required: id.
- **List all Monta inbound forecast groups** (List). Retrieve details of multiple forecast groups based on several optional parameters. The connector pages through all results.
- **Create a Monta inbound forecast group** (Create). Create a new inbound forecast group based on reference. Required: InboundForecasts, Reference.
- **Get single Monta inbound forecast by ID** (Get). Retrieve details of a single forecast from group with reference and this specific sku. Required: id, reference.
- **Update a Monta inbound forecast by ID** (Update). Update an existing inbound forecast in an existing inbound forecast group. Required: id, reference, Quantity.
- **Delete a Monta inbound forecast by ID** (Delete). Delete a single inbound forecast from an inbound forecast group. Required: id, reference.
- **Create a Monta inbound forecast** (Create). Create a new inbound forecast in an existing inbound forecast group. Required: reference, Quantity, Sku.
- **List all Monta inbound forecasts** (List). List all inbound forecasts for a product SKU. Required: product_sku.
- **Monta inbound forecasts bulk approve** (Approve). Approve multiple inbound forecasts at once based on ID.
- **List all Monta inbounds** (List). Reads all inbounds.
- **Create a Monta order anonymization** (Create). Anonymize an order (GDPR forget): removes the invoice and/or shipping personal data. Required: webshop_order_id.
- **List all Monta order batches** (List). Get order with batches. Required: webshop_order_id.
- **Create a Monta order colli** (Create). Create colli for order. Required: webshop_order_id, Number.
- **List all Monta order colli** (List). Get order collies. Required: webshop_order_id.
- **List all Monta order deleted lines** (List). Get order deleted lines. Required: webshop_order_id.
- **List all Monta order event feed** (List). List order events after a given event id (an event feed across all orders). Required: since_id. Monta returns the next 200 events per call: call again with the last event id until fewer than 200 come back.

- **List all Monta order events** (List). Get order events. Required: webshop_order_id.
- **List all Monta order headers** (List). List orders with header data only (lighter than orders.list), 30 per page. The connector pages through all results.
- **List all Monta order origins** (List). List the order origins (shops) with their shipper and surprise options.
- **List all Monta order processing timeframes** (List). Get expected processing timeframe. Required: webshop_order_id.
- **List all Monta order return forecasts** (List). Get return forecasts for order. Required: webshop_order_id.
- **List all Monta order return labels** (List). Get return labels for order. Required: webshop_order_id.
- **List all Monta order returns** (List). Get returns for order. Required: webshop_order_id.
- **Create a Monta order rma link** (Create). Create RMA link for an order. Required: webshop_order_id.
- **List all Monta order serials** (List). Get order with serial numbers. Required: webshop_order_id.
- **Get single Monta order shipping label file by ID** (Get). Download shipping label for an order. Required: id, webshop_order_id. Returns a file (PDF), not JSON.
- **Create a Monta order shipping label** (Create). Create shipping label for an order. Required: webshop_order_id.
- **List all Monta order shipping labels** (List). Get shipping labels for an order. Required: webshop_order_id.
- **Monta order shipping labels cancel** (Cancel). Cancel the most recent shipping label of an order. Required: webshop_order_id.
- **Monta order shipping labels bulk cancel** (Cancel). Cancel all shipping labels of an order. Required: webshop_order_id.
- **Monta order shipping labels void** (Action). Cancel one shipping label of an order, chosen by its track and trace code. Required: webshop_order_id, track_and_trace.
- **Get single Monta order by ID** (Get). Fetches order information for given order ID. Required: id.
- **Update a Monta order by ID** (Update). Update an order. Only possible while the order is not picked yet. Required: id.
- **Monta orders cancel** (Cancel). Delete (cancel) an order in Monta. Monta requires a Note explaining why. Required: webshop_order_id, Note.
- **List all Monta orders** (List). List orders with full details, 30 per page. The connector pages through all results.
- **Create a Monta order** (Create). Create a new order. Required: ConsumerDetails, WebshopOrderId.
- **Monta orders split** (Action). Split an Order. Required: webshop_order_id.
- **List all Monta pick routes** (List). Fetch pickroute information for your relation (max 100 per call).
- **Delete a Monta product barcode by ID** (Delete). Delete barcode from product. Required: id, sku.
- **Monta product barcodes bulk delete** (Delete). Delete all barcodes from a product. Required: sku.
- **List all Monta product events** (List). List product events after a given event id. Required: since_id.
- **List all Monta product field definitions** (List). Get all custom field definitions for the current relation.
- **Get single Monta product field value by ID** (Get). Retrieve custom field values for a specific product. Required: id.
- ...and 50 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
