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

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

## Facts

| | |
| --- | --- |
| Application | mParticle |
| Category | Marketing Automation |
| AI tools | 97 |
| Authentication | App credentials |
| 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 mParticle is connected

- 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

## Connect mParticle in Elaichi

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

1. Open Connections, choose Add connection, and pick mParticle.
2. Optionally set Share with, then press Connect.
3. Paste your mParticle app credentials. mParticle authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which mParticle tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

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

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

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

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

### Check which audiences are live before launch

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

### Keep apps and platforms current

Marketing ops. 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.

### See what an app actually collects

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

### Audit audiences across every workspace

Growth. List the audiences in each mParticle workspace side by side to spot duplicates and overlap before the next campaign goes out.

### Update services on a platform in bulk

Product. Change the services attached to an app platform in one ask instead of editing them one at a time in mParticle.

### Review mParticle users and accounts

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

## 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. Endpoint: 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](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 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 my team share one mParticle connection?

Yes. One person connects mParticle in Elaichi and shares the connection with a team, and nobody else ever handles the mParticle app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every mParticle call.

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

## All 97 mParticle tools

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

- **List all mParticle users** (List). List the users of an mParticle account. Returns user records with their id plus content-type-specific user fields defined upstream. Required: account_id.
- **Get single mParticle user by ID** (Get). Get a single mParticle user by id. Returns the user record with its id plus content-type-specific user fields defined upstream. Required: id, account_id.
- **List all mParticle workspaces** (List). List the workspaces in an mParticle account. Returns workspace records including id. Required: account_id.
- **List all mParticle accounts** (List). List mParticle accounts. Returns: id, name, data_type, created_on, last_modified_on. Required: account_id.
- **Get single mParticle account by ID** (Get). Get a single mParticle account by id. Returns: id, name, data_type, created_on, last_modified_on. Required: id, account_id.
- **Create a mParticle account** (Create). Create an account.
- **Update a mParticle account by ID** (Update). Update an account. Required: id.
- **Delete a mParticle account by ID** (Delete). Delete an account. Required: id.
- **List all mParticle apps** (List). Get all apps.
- **Get single mParticle app by ID** (Get). Get a single app. Required: id.
- **Create a mParticle app** (Create). Create an app.
- **Update a mParticle app by ID** (Update). Update an app. Required: id.
- **Delete a mParticle app by ID** (Delete). Delete an app. Required: id.
- **List all mParticle app platforms** (List). Get all app platforms. Required: app_id.
- **Get single mParticle app platform by ID** (Get). Get a single app platform. The id is the platform OS (e.g. ios, android). Required: id, app_id.
- **Create a mParticle app platform** (Create). Create an app platform. Required: app_id.
- **Update a mParticle app platform by ID** (Update). Update an app platform. The id is the platform OS (e.g. ios, android). Required: id, app_id.
- **Delete a mParticle app platform by ID** (Delete). Delete an app platform. The id is the platform OS (e.g. ios, android). Required: id, app_id.
- **List all mParticle app platform services** (List). Get all services for an app platform. Required: app_id, os.
- **MParticle app platform services bulk update** (Update). Configure a service for an app platform. Required: app_id, os.
- **List all mParticle audiences** (List). Get all audiences. Returns an array containing all active audiences within an account, where the account ID is set as a query parameter.
- **Delete a mParticle audience by ID** (Delete). Delete an audience. Deletes the audience with the given audience ID. The audience ID is labeled "id" in the responses to the Get all audiences and the Get all audiences for a workspace endpoints. Required: id.
- **List all mParticle workspace audiences** (List). Get all audiences for a workspace. Returns an array containing all active audiences within a workspace, where the workspace ID is set as a path parameter and the account ID is set as a query parameter. Required: workspace_id.
- **List all mParticle app data points** (List). Get data points for an app. Retrieves a list of DataPoints that exist for an App. The 1 after /apps/ is a placeholder for the Application ID. Required: app_id.
- **Create a mParticle app data point** (Create). Create a data point. Adds a new DataPoint for an App. Required: app_id.
- **Get single mParticle service filter by ID** (Get). Get a service filter. Get default filtering behavior for a service. The id is the service module name (e.g. GoogleAnalyticsEventForwarder). Required: id, app_id.
- **Update a mParticle service filter by ID** (Update). Update a service filtering. The id is the service module name (e.g. GoogleAnalyticsEventForwarder). Required: id, app_id.
- **List all mParticle service data point filters** (List). Get all data point filters. Retrieve a list of DataPoint filters for a specific App and Service. Required: app_id, module_name.
- **MParticle service data point filters bulk update** (Update). Update a data point filter. Required: app_id, module_name.
- **List all mParticle partner feeds** (List). Get all partner feeds for a workspace. Returns a list of partner feeds set up for a workspace. Required: workspace_id.
- **Get single mParticle partner feed by ID** (Get). Get a specific feed. Get details and settings for a specific partner feed. Required: id.
- **Create a mParticle partner feed** (Create). Create a new feed. Creates a new feed. Required: workspace_id.
- **Update a mParticle partner feed by ID** (Update). Update a feed. Updates an existing feed. Required: id, workspace_id.
- **List all mParticle output configurations** (List). Get all output configurations. List all available configurations for a particular module Required: workspace_id, module_name.
- **Create a mParticle feed subscription** (Create). Create a new feed subscription. Creates and configures a new feed subscription. Required: module_id.
- **List all mParticle services** (List). Get all services for an account.
- **Get single mParticle service by ID** (Get). Get a specific service with settings. The id is the service module name (e.g. Indicative). Required: id.
- **List all mParticle calculated attributes** (List). Get all calculated attributes. Required: workspace_id.
- **Create a mParticle calculated attribute** (Create). Create a new calculated attribute. Required: workspace_id.
- **Get single mParticle calculated attribute by ID** (Get). Get a calculated attribute. Required: id, workspace_id.
- **Update a mParticle calculated attribute by ID** (Update). Update a calculated attribute. Use this endpoint to create or update a draft of your Calculated Attribute definition. When a Calculated Attribute is updated, the draft_definition is changed. Required: id, workspace_id.
- **Delete a mParticle calculated attribute by ID** (Delete). Delete a calculated attribute. Required: id, workspace_id.
- **Get single mParticle calculated attribute activation by ID** (Get). Get a calculated attribute activation status. A calculated attribute’s activation status tells you whether the calculated attribute has been activated and when and who activated it. The id is the calculated attribute ID. Required: id, workspace_id.
- **Create a mParticle calculated attribute activation** (Create). Activate a calculated attribute. Use this endpoint to activate a calculated attribute. You must activate the Calculated Attribute before it can be used elsewhere in the system. Required: workspace_id, calculated_attribute_id.
- **Delete a mParticle calculated attribute draft by ID** (Delete). Delete a calculated attribute draft definition. Use this endpoint to discard a calculated attribute’s draft definition. The id is the calculated attribute ID. Required: id, workspace_id.
- **Get single mParticle calculated attribute calculation by ID** (Get). Get a calculated attribute status. A calculated attribute’s calculation status gives you the calculation progress and an estimated completion date. The id is the calculated attribute ID. Required: id, workspace_id.
- **List all mParticle data plans** (List). Get all Data Plans. Required: workspace_id.
- **Create a mParticle data plan** (Create). Create Data Plan. Required: workspace_id.
- **Get single mParticle data plan by ID** (Get). Get Data Plan. Required: id, workspace_id.
- **Update a mParticle data plan by ID** (Update). Update Data Plan. Required: id, workspace_id.
- ...and 47 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
