Skip to content

Monte Carlo MCP connector

The Monte Carlo connector brings data alerts, incidents, assets, lineage and monitors into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi agent, so your team can investigate data issues from any AI client, inside their own Monte Carlo access.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Which alerts fired on the orders table overnight?

Working in Monte Carlo with Elaichi

  • Looked in Monte Carlo
Ask anything…
Governance / Audit log Last 24 hours
Monte Carlo Looked in Monte Carlo Emily Carter · Claude · 9:41 AM Done
Monte Carlo Looked in Monte Carlo Megan Brooks · ChatGPT · 9:38 AM Done
Monte Carlo Looked in Monte Carlo Ryan Hayes · Cursor · 9:35 AM Done

How to connect Monte Carlo to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

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

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

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

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

Monte Carlo 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 Monte Carlo 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 Monte Carlo through Elaichi

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

  • Data engineering

    Work an alert before the morning standup

    Ask what fired overnight in Monte Carlo, pull the details of the alert on the orders table, and get a summary ready before anyone else is awake.

  • Data platform

    Trace a broken table back upstream

    When a table goes stale, follow its lineage in Monte Carlo to find the upstream asset that stopped loading, without clicking through the graph by hand.

  • Analytics

    Check a dashboard's source table is healthy

    Before sending a report, ask whether the assets behind it have open alerts or failed monitors in Monte Carlo, and attach the answer to the email.

  • Data governance

    Put a monitor on a key table

    Describe the table and the check you want, and have a freshness or volume monitor created in Monte Carlo so the next gap is caught early.

  • Finance

    Confirm revenue data is fresh before close

    Ask whether the revenue and billing tables in Monte Carlo loaded on time this month and whether anything is still open before numbers go out.

  • Support

    Explain why a stakeholder's numbers look wrong

    When someone asks why a figure changed, pull the related Monte Carlo incidents and lineage and reply with a plain explanation in minutes.

Try asking

  • “Which alerts fired on the orders table overnight?”
  • “Show the upstream lineage for the revenue dashboard table.”
  • “Create a freshness monitor on the customers table.”

What connecting Monte Carlo gets you

5 screens from Elaichi, each doing one job for your Monte Carlo account.

Elaichi Agent

Ask Elaichi to work across your apps.

Which alerts fired on the orders table overnight?

Show the upstream lineage for the revenue dashboard table.

Create a freshness monitor on the customers table.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about data incidents in plain language.

Ask which Monte Carlo alerts fired overnight and get answers from live monitors and assets.

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

One endpoint, every client, no shared key.

Use Monte Carlo from Claude, ChatGPT, Cursor or Microsoft Copilot through one org endpoint over OAuth.

ElaichiToolboxes
Name Source template Tools Created

Data engineering toolbox

Monte Carlo · alerts and incidents

Monte Carlo starter 18 Mar 4, 2026

Data platform toolbox

Monte Carlo · monitors and coverage

— 9 Mar 2, 2026

Analytics toolbox

Monte Carlo · assets and lineage

— 24 Feb 27, 2026

Data governance toolbox

Monte Carlo · ownership and data quality

Monte Carlo starter 6 Feb 19, 2026

Finance toolbox

Monte Carlo · revenue and billing tables

— 31 Jan 30, 2026

Product toolbox

Monte Carlo · event and usage tables

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Monte Carlo toolbox.

Give data engineering, analytics and governance separate toolboxes, each scoped to that team.

ElaichiConnections
Connection Scope Status Access
MO

Monte Carlo (Data platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
MO

Monte Carlo (Analytics)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
MO

Monte Carlo (Finance data)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
MO

Monte Carlo (Marketing data)

Connected by Tyler Reed

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

Monte Carlo (Production warehouse)

Connected by Ryan Hayes

Personal • Active Not shared
MO

Monte Carlo (Staging warehouse)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates investigate without ever seeing a credential.

One person connects Monte Carlo, shares it with teams, and nobody else touches a token.

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]

Monte Carlo Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Monte Carlo Alerts Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Monte Carlo Alerts List Toolbox

Audit log

Every Monte Carlo call answers who did what.

When, who, what happened and which monitor or asset, in an append-only log.

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.

Monte Carlo digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch alerts

    Monte Carlo

    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

    Monte Carlo

    Queued

Workflows

A schedule starts the incident digest, you approve.

Monte Carlo alerts are fetched, grouped, drafted into a digest, approved, then posted back.

Monte Carlo health

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

Live

Alerts

1,284 ↓ 12%

Assets

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Alerts created

Last 14 days

By team

Share of activity

Data platform 34%

Analytics 27%

Finance data 21%

Marketing data 18%

Collections and dashboards

Monte Carlo health, computed without a model.

Four metrics, 14 days of alerts created and a team breakdown, refreshed on a schedule.

Why connect Monte Carlo's MCP server through Elaichi

Monte Carlo builds and runs this MCP server. Elaichi sits in front of it, so Monte Carlo's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Monte Carlo's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Monte Carlo's tools at the same Elaichi address as every other connected app. Nobody adds Monte Carlo's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Monte Carlo sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Monte Carlo's server. By default, a tool Monte Carlo does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Monte Carlo

    Monte Carlo builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Monte Carlo team.

    docs.getmontecarlo.com/docs/in-app-support

Why run a vendor's MCP server through Elaichi →

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Monte Carlo

All three can connect Monte Carlo 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 Monte Carlo, 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 Monte Carlo tools Allow or restrict single Monte Carlo 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 Monte Carlo 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.

Questions, answered

How do I connect Monte Carlo to Claude?

Connect Monte Carlo in Elaichi first: pick it from the catalog, sign in to your Monte Carlo account and approve the connection, with no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the address. Claude asks you to sign in to Elaichi, and Monte Carlo alerts, assets and monitors are available in your chats.

Does Monte Carlo work with ChatGPT and Cursor as well as Claude?

Yes. Once Monte Carlo is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi agent. You connect Monte Carlo once and each person signs in to Elaichi from whichever client they use.

What can an AI agent actually do with my Monte Carlo data?

An agent connected through Elaichi can review alerts and incidents in Monte Carlo, look up tables and other assets, follow lineage upstream and downstream, and create or update monitors. In practice that means asking what fired on the orders table overnight, which upstream asset caused it, and setting a freshness check so it is caught next time. Short, concrete asks tend to work better than long paragraphs.

Does connecting Monte Carlo give the AI everything in my workspace?

No. Every call to Monte Carlo runs as the person who signed in, so the agent sees only the assets, alerts and monitors that person can already see in Monte Carlo. Elaichi can narrow that further with restrictions and toolboxes, and it never widens what Monte Carlo itself allows.

Can my team share one Monte Carlo connection?

Yes. One person connects Monte Carlo in Elaichi and shares the connection with a team, and nobody else ever handles a key or password. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who looked at an alert or created a monitor, not the account owner.

Can I stop an agent from deleting or changing things in Monte Carlo?

Yes. Restrictions in Elaichi apply per action, so you can allow reading alerts and lineage in Monte Carlo while restricting the creation or removal of monitors. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

What happens to a Monte Carlo connection when someone leaves?

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

Does the Monte Carlo MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Monte Carlo 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 Monte Carlo?

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

How is Elaichi different from Composio for Monte Carlo?

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

Put Monte Carlo 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