Anaplan AI Gateway is a remote MCP server. It gives external AI systems read-only access to Anaplan models and data. Your AI system must support remote MCP servers.
AI Gateway is an entitled service that requires a subscription. AI Gateway is then enabled for selected Anaplan workspaces using Agent Studio. AI Gateway uses your Anaplan credentials for access control and only lets you see data that you are allowed to see.
In your external AI system, you need to create a connector to Anaplan. Typically, you need to configure your connector with:
- The Anaplan AI Gateway URL for your region. See your region in the list below.
- Client ID. External AI systems are assigned a client ID that identifies that system type to Anaplan. Client IDs are region specific and are created by Anaplan. See your region in the list below.
Note: Depending on the MCP client used in your organization, a connector may already exist. Check with your IT department.
Connect AI systems
Below is information on connecting to AI systems that have client IDs.
Allowed callback URLs
Anaplan creates callback URLs for AI systems as part of creating client IDs. They are included in the sections below. You don't need to provide the callback URL when making the connection. However, the URL can be useful when diagnosing callback mismatch errors at sign-in. The URLs must match exactly.
Gemini Enterprise
Claude on the web and Claude Desktop
Claude Code
Cursor
Microsoft Visual Studio Code
Whichever external AI system you use, the calculations returned through AI Gateway will be correct. However, how your external AI interprets these calculations is outside Anaplan control. Also, external LLMs have no inherent knowledge of model logic or semantics. Anaplan Analyst has greater drill-down capabilities and offers an enhanced and fully auditable experience grounded in Anaplan planning fundamentals. Learn more at Anaplan Analyst
Region AI Gateway URLs and client IDs
Note: In the listings below, Microsoft client IDs are for Microsoft Visual Studio Code.
ae1: Cloud - UAE
ap1: Cloud - Japan
AST (Amazon single tenant)
au1: Cloud - Australia
ca1: Cloud - Canada
eu1 (DC Netherlands), eu2 (DC Germany), and eu4 (Cloud Europe)
eu3: Cloud - Europe
eu5: Cloud - Europe
gb1: Cloud - UK
GST (Google single tenant)
id1: Cloud - Indonesia
in1: Cloud - India
me1: Cloud - Saudi Arabia
sg1: Cloud - Singapore
us1, us2, us5 to us8
us9: Cloud - US
MCP client ID not listed?
If your external AI system isn’t listed for your region above, your Customer Success Business Partner can advise you. To be suitable for a client ID, the MCP client must support:
- the
streamableHTTPprotocol. - OAuth 2.1 with PKCE as a public client with no secret.
- OAuth discovery, or manual entry of authorization and token endpoints.
- an allowed callback URL. Anaplan will add this as part of creating the new client IDs.
MCP clients that use Dynamic Client Registration (DCR) or client secrets aren't suitable for use with AI Gateway.