mParticle MCP connector
The mParticle connector brings audiences, apps, app platforms, data points, workspaces and accounts into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with every request running as the person who signed in and landing in the audit log.
- App credentials
- Free 14-day trial
- No credit card
List the audiences in the Growth workspace with their IDs
Working in mParticle with Elaichi
-
List all mParticle users
-
Get single mParticle user by ID
-
List all mParticle workspaces
How to connect mParticle to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
mParticle MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
mParticle MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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.
mParticle MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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.
mParticle MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
mParticle MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- 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 mParticle to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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 mParticle through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in mParticle is logged.
-
Marketing
Check which audiences are live before launch
Ask for the audiences in a workspace and get the full list back in seconds. Remove the stale ones you no longer sync anywhere, without clicking through mParticle.
-
Marketing ops
Keep apps and platforms current
Create a new app or app platform in mParticle when a product ships, update names and settings later, and read everything back from the same chat.
-
Analytics
See what an app actually collects
Pull the data points for an app and see which events and attributes are flowing in before you build a report or a segment on top of them.
-
Growth
Audit audiences across every workspace
List the audiences in each mParticle workspace side by side to spot duplicates and overlap before the next campaign goes out.
-
Product
Update services on a platform in bulk
Change the services attached to an app platform in one ask instead of editing them one at a time in mParticle.
-
IT
Review mParticle users and accounts
List the users and accounts in mParticle to confirm who has access before an audit or an offboarding, and tidy up accounts that are no longer needed.
Try asking
- “List the audiences in the Growth workspace with their IDs”
- “Which data points does the iOS app collect?”
- “Show every app platform sending data into the production account”
What connecting mParticle gets you
6 screens from Elaichi, each doing one job for your mParticle account.
Ask Elaichi to work across your apps.
List the audiences in the Growth workspace with their IDs
Which data points does the iOS app collect?
Show every app platform sending data into the production account
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about audiences and apps in plain words.
Type a question and get answers from live mParticle workspaces, audiences and data points.
Copy the endpoint
AI apps
One endpoint for every client you already use.
Claude, ChatGPT and Cursor reach mParticle through one org endpoint, no SDK, no shared key.
Tool catalog
97 mParticle tools ready, no code to write.
Workspaces, accounts, apps, app platforms, audiences and data points, covered without custom code.
Toolboxes
Each team gets its own mParticle toolbox.
Marketing works with audiences while IT manages accounts, each from a toolbox scoped to them.
Shared connections
Teammates work through a connection, never a credential.
See who connected each mParticle account and how many teams and members share it.
Audit log
Every mParticle call answers who did what.
When, who, what happened and which audience or app, 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.
mParticle digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch audiences
mParticle
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
mParticle
Queued
Workflows
A schedule starts the work, a person approves.
Audiences are fetched, grouped and summarized, then a reviewer approves before it posts to mParticle.
mParticle health
Refreshed 4 minutes ago · every 15 minutes · from the audiences collection
Audiences
1,284 ↓ 12%
Apps
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Audiences created
Last 14 days
By team
Share of activity
Marketing 34%
Growth 27%
Analytics 21%
Marketing ops 18%
Collections and dashboards
mParticle health, computed on a schedule, no model.
Four metrics, 14 days of data points created and a breakdown by team, refreshed automatically.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for mParticle
All three can connect mParticle 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over mParticle tools | Allow or restrict single mParticle 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 mParticle 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.
mParticle tools for your AI agents
97 tools are ready to call through Elaichi's MCP endpoint the moment you connect mParticle, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect mParticle to Claude?
Connect mParticle in Elaichi first, then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Elaichi asks for your mParticle app credentials and that is the whole sign-in step. There is no OAuth application to register and no client ID or secret to generate.
Does mParticle work with ChatGPT and Cursor as well as Claude?
Yes. Once mParticle is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent as well as Claude. You connect mParticle once and every client you use picks it up.
What can an AI agent actually do with my mParticle data?
An agent can list the audiences in an mParticle workspace, show the apps and app platforms sending data in, check which data points an app collects, and read account, workspace and user details. It can also create or update apps and app platforms, update platform services in bulk, and remove audiences, apps or accounts when asked. Short, concrete asks such as list the audiences in the Growth workspace work better than long paragraphs.
Does connecting mParticle give the AI every workspace and audience?
No. Every call into mParticle runs as the person who signed in, so an agent sees only the workspaces, apps and audiences that person can already open in mParticle. Elaichi can narrow that further with roles and restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in mParticle?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting mParticle audiences, apps or accounts for a role or for one person while leaving lists and lookups alone. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to an mParticle connection when someone leaves?
Offboarding someone in Elaichi ends their access to mParticle through every client at once. A shared mParticle connection keeps working for everyone else on the team. If you want the connection gone altogether, disconnecting mParticle once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the mParticle MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. mParticle 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 mParticle?
Yes. Both let Claude, ChatGPT or Cursor use mParticle. 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 mParticle call.
How is Elaichi different from Composio for mParticle?
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 mParticle: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put mParticle 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