anaplan-mcp
MCP server wrapping the Anaplan SDK. Plug it into Claude Desktop, Cursor, or any MCP client and talk to Anaplan directly.
Setup
Add to your MCP client config (claude_desktop_config.json, Cursor settings, …):
{
"mcpServers": {
"anaplan": {
"command": "uvx",
"args": ["anaplan-mcp"],
"env": {
"ANAPLAN_WORKSPACE_ID": "...",
"ANAPLAN_MODEL_ID": "...",
"ANAPLAN_EMAIL": "me@example.com",
"ANAPLAN_PASSWORD": "secret"
}
}
}
}
Certificate auth is also supported — swap the last two vars for:
"ANAPLAN_CERTIFICATE": "/path/to/cert.pem",
"ANAPLAN_PRIVATE_KEY": "/path/to/key.pem"
Python API
For OAuth or any custom auth, use the Python API and pass any httpx.Auth subclass:
from anaplan_mcp import AnaplanMCP
# Basic / cert via env vars
AnaplanMCP.from_env().run()
# Explicit credentials
AnaplanMCP(workspace_id="...", user_email="...", password="...").run()
AnaplanMCP(workspace_id="...", certificate="...", private_key="...").run()
# Any httpx.Auth subclass (OAuth, token, …)
from anaplan_sdk._auth import AnaplanLocalOAuth
AnaplanMCP(workspace_id="...", auth=AnaplanLocalOAuth(...)).run()
Running locally with non-standard auth
For auth that can't be expressed as env vars (e.g. OAuth), create a local script and point your MCP client at it:
server.py:
from anaplan_sdk._auth import AnaplanLocalOAuth # or any httpx.Auth subclass
from anaplan_mcp import AnaplanMCP
AnaplanMCP(
workspace_id="<your-workspace-id>",
auth=AnaplanLocalOAuth(client_id="...", client_secret="...", redirect_uri="..."),
).run()
MCP client config:
{
"mcpServers": {
"anaplan": {
"command": "uv",
"args": ["run", "/path/to/server.py"]
}
}
}
Filtering tools
AnaplanMCP(..., include={"tr", "audit"}) # whitelist API groups
AnaplanMCP(..., exclude={"cw"}) # blacklist API groups
AnaplanMCP(..., exclude_methods={"tr__delete_list_items"}) # suppress specific tools
| Group | Covers |
|---|---|
| (root) | Bulk file I/O, imports, exports |
audit |
Audit log, users |
tr |
Lists, modules, transactional writes |
alm |
Application Lifecycle Management |
cw |
CloudWorks integrations & connections |
cw.flows |
CloudWorks flows |
scim |
User provisioning (SCIM) |
Metadata
Release files for anaplan-mcp 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| anaplan_mcp-0.0.1.tar.gz | 66.3 kB | Without provenance | Details for anaplan_mcp-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| anaplan_mcp-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for anaplan_mcp-0.0.1-py3-none-any.whl |
Total release size: 79.3 kB
Release files / anaplan_mcp-0.0.1.tar.gz
| Download URL | anaplan_mcp-0.0.1.tar.gz |
|---|---|
| Size | 66.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee5e7f0a16f41146d6d699ebc57d143c1869668eb9dc624899382226abbe4250
|
|
BLAKE2b-256 checksum How to use checksums |
ed7524c5feacc1a84ded11077dc432b2e56bfe5124b8b670cda4043a61105ca1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.4 {"installer":{"name":"uv","version":"0.10.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / anaplan_mcp-0.0.1-py3-none-any.whl
| Download URL | anaplan_mcp-0.0.1-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5aeef21ed5af21e3b11bd42a0f7eea88813e541cbb4ea40e78ad1db95f6205b1
|
|
BLAKE2b-256 checksum How to use checksums |
a7a55810b32d23c1ff19228d16adaaf49c9d9699b464865c17c0cb68f4e10a1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.4 {"installer":{"name":"uv","version":"0.10.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for anaplan-mcp 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.