Connect your AI Agents to Anaplan in minutes
Available tools
list_exports
List all export actions defined in an Anaplan model. Export actions extract data from modules or lists to files. Returns export IDs, names, types, and source/target information. Use export IDs with run_export to execute data extractions.
get_export
Get detailed information about a specific Anaplan export action. Returns export name, type, source module/view, target file, and format configuration. Use to understand export configuration before running.
run_export
Execute an Anaplan export action to extract data from a model. Starts an asynchronous export task and returns task ID for monitoring. Use get_export_task to monitor progress and get_export_data to retrieve the exported data once the task completes successfully.
get_export_task
Get the status and progress of a running or completed Anaplan export task. Returns task state (NOT_STARTED, IN_PROGRESS, COMPLETE, CANCELLED, FAILED), progress percentage, current step, and any failure details. Poll this endpoint until task state is COMPLETE, then use get_export_data.
get_export_data
Download the data from a completed Anaplan export task. Only call after get_export_task shows state=COMPLETE. Returns the exported data content (typically CSV format). Requires workspace_id, model_id, export_id, and task_id.
list_files
List all files available in an Anaplan model. Files are used as sources for imports and targets for exports. Returns file IDs, names, formats, delimiters, and chunk information. Use file IDs with upload_file to prepare data for imports.
get_file
Get detailed information about a specific Anaplan file. Returns file name, format, delimiter, encoding, header row, first data row, and chunk count. Use to understand file structure before uploading or downloading.
upload_file
Upload content to an Anaplan file (for small files). Replaces the entire file content with the provided string data. Typically used for CSV data to be imported. For large files, use upload_file_chunk to upload in parts. File must already exist in the model (created via Anaplan UI or API).
upload_file_chunk
Upload a chunk of a large file to Anaplan. For files larger than 50MB, split content into chunks and upload sequentially. Chunk index is 0-based. Data should be base64-encoded binary content. After uploading all chunks, the file is automatically assembled.
download_file
Download the content of an Anaplan file. Returns the file content (typically CSV data from exports). For large files with multiple chunks, this downloads the first chunk. Use get_file first to check chunk_count if downloading large files.
delete_file
Delete a file from an Anaplan model. Removes the file and its content. Cannot be undone. Use with caution as imports relying on this file will fail.
list_imports
List all import actions defined in an Anaplan model. Import actions load data from files or other sources into modules or lists. Returns import IDs, names, types, and source/target information. Use import IDs with run_import to execute data loads.
How to set up Merge Agent Handler
In an mcp.json file, add the configuration below, and restart Cursor.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.
Make sure Claude is using the Node v20+.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "yMt*****"
14 }
15 }
16 }
17}Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "<ah-production-access-key>"
14 }
15 }
16 }
17 }In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".
You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.
Learn more in the official documentation ↗
1{
2 "inputs": [
3 {
4 "type": "promptString",
5 "id": "agent-handler-auth",
6 "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7 "password": true
8 }
9 ],
10 "servers": {
11 "agent-handler": {
12 "type": "stdio",
13 "command": "npx",
14 "args": [
15 "-y",
16 "mcp-remote@latest",
17 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18 "--header",
19 "Authorization: Bearer ${input:agent-handler-auth}"
20 ]
21 }
22 }
23}FAQs on using Merge's Anaplan MCP server
FAQs on using Merge's Anaplan MCP server
Explore other MCP servers built and managed by Merge
Ready to try it out?
Whether you're an engineer experimenting with agents or a product manager looking to add tools, you can get started for free now
