Skip to content

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.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Show me the events for order 48213 and where it is now

Working in Monta with Elaichi

  • Get single Monta batch by ID
  • List all Monta health checks
  • List all Monta inbound forecast events
Ask anything…
Governance / Audit log Last 24 hours
Monta List all Monta inbound forecast events Emily Carter · ChatGPT · 9:41 AM Done
Monta List all Monta health checks Emily Carter · ChatGPT · 9:41 AM Done
Monta Get single Monta batch by ID Emily Carter · ChatGPT · 9:41 AM Done
Monta Monta addresses validate Megan Brooks · Claude · 9:38 AM Done
Monta List all Monta inbound forecast group labels Ryan Hayes · Cursor · 9:35 AM Done

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

Step by step, for each AI app

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

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

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

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

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

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

  • Operations

    Find out where an order stands

    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.

  • Supply chain

    Tell the warehouse what is arriving

    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.

  • Warehouse

    Approve a week of inbound forecasts at once

    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.

  • Customer service

    Check what was packed before replying

    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.

  • Ecommerce

    Clean up an address before it ships

    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.

  • Compliance

    Anonymize an order on request

    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.

Try asking

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

See all 100 Monta tools →

What connecting Monta gets you

6 screens from Elaichi, each doing one job for your Monta account.

Elaichi Agent

Ask Elaichi to work across your apps.

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

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about Monta orders in plain language.

Order events, parcels and inbound forecasts answered from live Monta records, not a stale export.

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

Monta works from every client through one endpoint.

Claude, ChatGPT, Cursor and Microsoft Copilot reach Monta with no SDK and no shared API key.

ElaichiTools
Tool Action Description
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.

Tool catalog

100 Monta tools ready with no code.

Orders, batches, colli, inbounds and forecasts, covered without an engineer writing a line.

ElaichiToolboxes
Name Source template Tools Created

Operations toolbox

Monta · orders and batches

Monta starter 18 Mar 4, 2026

Warehouse toolbox

Monta · inbounds and forecasts

— 9 Mar 2, 2026

Customer service toolbox

Monta · order events and parcels

— 24 Feb 27, 2026

Supply chain toolbox

Monta · inbound forecast groups

Monta starter 6 Feb 19, 2026

Ecommerce toolbox

Monta · addresses and order feed

— 31 Jan 30, 2026

Compliance toolbox

Monta · order anonymization

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Monta toolbox.

Warehouse approves forecasts, customer service reads orders, each scoped to what their work needs.

ElaichiConnections
Connection Scope Status Access
MO

Monta (Operations)

Connected by Emily Carter

Personal • Active 1 team · 6 members
MO

Monta (Warehouse)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
MO

Monta (Customer service)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
MO

Monta (Supply chain)

Connected by Tyler Reed

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

Monta (Ecommerce)

Connected by Ryan Hayes

Personal • Active Not shared
MO

Monta (Compliance)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use Monta without seeing the key.

One person connects Monta, shares it with teams, and nobody else handles 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]

Monta Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Monta Orders Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Monta Orders List Toolbox

Audit log

Know who touched every Monta order.

Every forecast approval, order lookup and anonymization logged with who, when and which 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.

Monta digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch orders

    Monta

    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

    Monta

    Queued

Workflows

A schedule turns Monta inbounds into decisions.

Forecasts fetched, grouped, drafted into a digest, approved by a person, posted back to Monta.

Monta health

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

Live

Orders

1,284 ↓ 12%

Colli

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Orders created

Last 14 days

By team

Share of activity

Operations 34%

Warehouse 27%

Customer service 21%

Supply chain 18%

Collections and dashboards

Monta order health reported without being asked.

Orders created over 14 days, split by team, computed from Monta with no model involved.

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Monta, 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 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Monta tools for your AI agents

100 tools are ready to call through Elaichi's MCP endpoint the moment you connect Monta, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

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.

Put Monta 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