# Anaplan MCP connector

The Anaplan connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent run actions, check action tasks, review CloudWorks flows and search audit events in Anaplan, with every call made as the signed-in person and logged.

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

## Facts

| | |
| --- | --- |
| Application | Anaplan |
| Category | Erp |
| AI tools | 142 |
| 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 Anaplan is connected

- Did last night's actuals import into Anaplan finish?
- Show me import errors from this morning's CloudWorks run
- Which Anaplan flows are scheduled to run this weekend?

## Connect Anaplan in Elaichi

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

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

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

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

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

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

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

### Refresh the forecast after actuals land

FP&A. Kick off the import action that pulls this month's actuals into the planning model, then ask whether the task finished before the review meeting starts.

### Check why last night's load failed

Finance. Pull the import error log for the overnight CloudWorks run and get the failed rows explained in plain language, without opening Anaplan and clicking through the run history.

### Run the demand plan refresh on request

Supply chain. Start the action that reloads the demand plan from the warehouse feed and watch the task until it completes, so the S&OP deck uses current numbers.

### Confirm quota models updated before Monday

Sales operations. List the CloudWorks flows that feed territory and quota data, see when each last ran and whether it succeeded, and raise the ones that did not.

### Pause a schedule during the close

IT. Disable the CloudWorks schedule that pushes data into the model while finance is closing the books, then enable it again when the period is locked.

### Find out who changed what in Anaplan

Model admins. Search Anaplan audit events for a model, a person or a date range and get a readable summary of what happened, ready for an internal control review.

## Elaichi vs Zapier MCP vs Composio for Anaplan

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

Connect Anaplan in Elaichi first: the sign-in step asks for your Anaplan API key, and there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi as yourself and Anaplan is available in your chats.

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

Yes. The Anaplan connector is exposed through the same endpoint, https://api.elaichi.ai/mcp, for Claude, ChatGPT, Cursor, Microsoft Copilot, the Elaichi Agent and any other MCP client. You connect Anaplan once in Elaichi and every client picks it up.

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

With Anaplan connected, an agent can start an action, tell you whether an action task finished, list and run CloudWorks flows, turn a schedule on or off, read import error logs and search audit events. Short, concrete asks work best, such as "did the actuals import into Anaplan finish" rather than a long paragraph of instructions.

### Does connecting Anaplan give the AI access to every workspace and model?

No. Every call to Anaplan runs inside the access of the person who signed in, so the agent sees the workspaces, models and flows that person can already open in Anaplan and nothing more. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what Anaplan itself allows.

### Can my team share one Anaplan connection?

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

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

Yes. In Elaichi you restrict individual actions on the Anaplan connector, such as deleting a CloudWorks connection or disabling a schedule, and the restriction applies to a role or to one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to an Anaplan connection when someone leaves?

Offboarding a person in Elaichi ends their access to Anaplan through every client at once. If they had shared an Anaplan connection with a team, that connection keeps working for everyone else. Disconnecting Anaplan once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

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

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

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

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

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

## All 142 Anaplan tools

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

- **Create a Anaplan action task** (Create). Run deletion. Required: workspace_id, model_id, action_id.
- **List all Anaplan action tasks** (List). Get a list of deletion tasks. Required: workspace_id, model_id, action_id.
- **Get single Anaplan action task by ID** (Get). Monitor the deletion tasks. Required: id, workspace_id, model_id, action_id.
- **List all Anaplan actions** (List). Retrieve model actions. This lists the actions available for the given model ID. The response comes in the form of a JSON array containing the list of actions that you can carry out, with the following values: id is the Id of the action that you can carry out in the specified model. Required: workspace_id, model_id.
- **Get single Anaplan action by ID** (Get). Retrieve action metadata. Required: id, workspace_id, model_id.
- **List all Anaplan audit events** (List). Retrieve Audit Events for Tenant. Retrieves the audit events in the database for the tenant to which your user is associated. You can retrieve results in JSON or CEF. You can specify: the type of events to return. the dateFrom start of a range of events to return. the dateTo end of a range of events to return.
- **Anaplan audit events search** (Search). Search for Audit Events using POST. Retrieves the audit events in the database for the tenant to which your user is associated based on whether you specify these in the body: from , to , and interval . The from and to dates refer to when the event happened and not the date on which the event was stored in the database.
- **Create a Anaplan auth** (Create). Create an Anaplan auth token with the connected username and password (Basic auth). Tokens last 35 minutes; the connector calls this automatically to keep the session alive.
- **Anaplan auth tokens validate** (Validate). Check authentication token details. Otherwise, it returns a 401 Unauthorized message.
- **Create a Anaplan cloudworks connection** (Create). Create a connection. integrations/connections. Use this call to create a new connection for CloudWorks. Required: type.
- **List all Anaplan cloudworks connections** (List). Get connections. Use this to get a list of your current connections to CloudWorks.
- **Update a Anaplan cloudworks connection by ID** (Update). Edit a connection. integrations/connections/{connectionId}. Use this call to edit a connection in Anaplan CloudWorks. Required: id.
- **Anaplan cloudworks connections partial update** (Update). Patch a connection. integrations/connections/{connectionId}. Use this call to patch a connection in Anaplan CloudWorks. Required: connection_id.
- **Delete a Anaplan cloudworks connection by ID** (Delete). Delete a connection. Use this to delete a connection to CloudWorks. Required: id.
- **List all Anaplan cloudworks import error logs** (List). Get an import error log. Use this call to get an import error log. Required: run_id.
- **Create a Anaplan cloudworks integration flow** (Create). Create a new integration flow. Use this call to create a new integration flow for Anaplan CloudWorks.
- **Anaplan cloudworks integration flows execute** (Execute). Run an integration flow. Use this call to run an integration flow. Required: integration_flow_id.
- **List all Anaplan cloudworks integration flows** (List). Get all integration flows. Use this call to retrieve all your integration flows.
- **Get single Anaplan cloudworks integration flow by ID** (Get). Get integration flows by integration ID. Use this call to get details for a specific integration flow. Required: id.
- **Update a Anaplan cloudworks integration flow by ID** (Update). Edit an integration flow. Use this call to edit an integration flow. Required: id.
- **Delete a Anaplan cloudworks integration flow by ID** (Delete). Delete an integration flow. Use this call to delete an integration flow. Required: id.
- **List all Anaplan cloudworks integration runs** (List). Get history of integration runs. Use this call to see the integration history. Required: integration_id.
- **Anaplan cloudworks integration schedules enable** (Enable). Enable the schedule of a CloudWorks integration. Required: integration_id.
- **Anaplan cloudworks integration schedules disable** (Disable). Disable the schedule of a CloudWorks integration without deleting it. Required: integration_id.
- **Create a Anaplan cloudworks integration schedule** (Create). Create an integration schedule. Use this call to create an integration schedule. This call supports a maximum of one schedule per integration. Required: integration_id.
- **Anaplan cloudworks integration schedules bulk update** (Update). Update the schedule of an integration. Use this call to update the schedule of an integration for Anaplan CloudWorks. Required: integration_id.
- **Delete a Anaplan cloudworks integration schedule by ID** (Delete). Delete an integration schedule. Use this call to delete an integration schedule. Required: integration_id.
- **Create a Anaplan cloudworks integration** (Create). Create a CloudWorks integration. Without processId it is an import or export integration with one job (cloud storage to Anaplan or Anaplan to cloud storage); with processId it is a process integration whose jobs cover the process actions that use the cloud connection. Required: name, version, workspaceId, modelId.
- **Anaplan cloudworks integrations execute** (Execute). Run an integration. Use this call to run an integration. Required: integration_id.
- **Anaplan cloudworks integrations cancel** (Cancel). Cancel running integration. Use this call to cancel an ongoing integration job. Required: integration_id.
- **List all Anaplan cloudworks integrations** (List). Get all integrations. Use this call to retrieve all your integrations.
- **Get single Anaplan cloudworks integration by ID** (Get). Get integrations by integration ID. Use this call to get integration details for a specific integration. Required: id.
- **Update a Anaplan cloudworks integration by ID** (Update). Edit a CloudWorks integration (import, export or process). Send the full definition, as for create; include processId for a process integration. Required: id, name, version, workspaceId, modelId.
- **Delete a Anaplan cloudworks integration by ID** (Delete). Delete an integration. Use this call to delete an integration, import or export in CloudWorks. Required: id.
- **List all Anaplan cloudworks model integrations** (List). Get integrations by Model ID. Use this call to get all integrations from an Anaplan model. Required: model_id.
- **Get single Anaplan cloudworks notification by ID** (Get). Get a notification configuration. Use this to get your notification configuration details. Required: id.
- **Create a Anaplan cloudworks notification** (Create). Create a notification configuration. Use this call to cofigure a new integration notification.
- **Update a Anaplan cloudworks notification by ID** (Update). Edit a notification configuration. integrations/notifications/{notificationId}. Use this call to edit the configuration of an integration notification. Required: id.
- **Delete a Anaplan cloudworks notification by ID** (Delete). Delete a notification configuration. Use this call to delete an integration notification. Required: id.
- **List all Anaplan cloudworks process error logs** (List). Get a process error log. Use this call to get a process error log. Required: run_id, action_id.
- **List all Anaplan cloudworks run errors** (List). Get integration run errors. Use this call to review error messages from the integration run. Required: run_id.
- **Get single Anaplan cloudworks run by ID** (Get). Get run status. Use this call to get the status of a specific integration run. Required: id.
- **Create a Anaplan comparison report task** (Create). Create a full comparison report generation task. Use this endpoint to start a task that generates a full comparison report between two model revisions. Required: model_id, sourceModelId, sourceRevisionId, targetRevisionId.
- **Get single Anaplan comparison report task by ID** (Get). Retrieve the info for a full comparison report generation task. Use this call to retrieve information about a specific comparison report generation task. A successful response contains a link that you can use to download the comparison report file. Required: id, model_id.
- **Get single Anaplan comparison report by ID** (Get). Retrieve the content for a full comparison report. Use this endpoint to download the contents of the comparison report for a set of revisions. Before you use this endpoint, make sure the report is generated and ready to download. The report is identical to the report in the user interface. Required: id, model_id, target_revision_id.
- **Get single Anaplan current period by ID** (Get). Retrieve current period. Use this call to determine the value of the current period in Anaplan. If the current period is not set in Anaplan, this call returns empty strings for the periodText and lastDay values of the currentPeriod . Workspace Administrator only. Required: id (model id), workspace_id.
- **Anaplan current period bulk update** (Update). Set current period. Use this call to change or reset the current period in Anaplan. When the date value is set to blank in this call, the API resets the current period to blank. Workspace Administrator only. Required: workspace_id, model_id.
- **List all Anaplan dimension items** (List). Retrieve all items in a dimension. Use this call to retrieve the IDs, codes, and names for items in a specified dimension. The dimension must be a list, a list subset, a line item subset, or the Users dimension. Calls at model-level do not support the Time dimension. Workspace Administrator only. Required: model_id, dimension_id.
- **Anaplan dimension items search** (Search). Lookup dimension items by name or code. Retrieve the items from a dimension that match one of a list of names or a list or codes. This call does not return results for names or codes for which an item does not exist. Workspace Administrator only. Required: workspace_id, model_id, dimension_id.
- **Create a Anaplan export task** (Create). Run the export. This creates a task with the specified exportID and returns the newly-created taskID. Required: workspace_id, model_id, export_id.
- ...and 92 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
