ChatGPT
ChatGPT connects to CARTO through a custom MCP server over OAuth, giving ChatGPT access to CARTO's MCP tools.
ChatGPT can also render CARTO maps inline in the conversation, providing a richer experience when working with CARTO maps and spatial data.
Requirements
A ChatGPT Business, Enterprise, or Edu workspace with Developer mode enabled. Full MCP support, including write and modify actions, is currently available on these plans. Pro users can connect MCPs with read/fetch permissions. See OpenAI's Developer mode and MCP apps documentation
Your CARTO MCP Server URL.
A CARTO SPA OAuth Client with a Client ID. A client secret is supported and recommended for this setup. See Connecting with OAuth.
Access to configure the OAuth callback URL on the CARTO SPA OAuth Client.
Connecting via OAuth
In ChatGPT, open Settings > Security and login, scroll to Developer mode, and toggle it on. You may see an “ELEVATED RISK” warning; this is expected when enabling custom MCP servers.
Go to Settings > Plugins > Browse plugins and click the + button in the top-right.
In New Plugin, configure the MCP server:
Name: anything, such as
CARTO.Connection: leave as Server URL.
URL: your CARTO MCP Server URL.

Under Authentication, choose OAuth.
Expand Advanced OAuth settings > Registration method and change CIMD to User-Defined OAuth Client. Enter your CARTO Client ID and Client Secret, and add
offline_accessto the scopes.Accept the “I understand and want to continue” warning and click Create.
Before signing in, register ChatGPT's OAuth callback URL on your CARTO client. In CARTO, open the SPA client under Developers → Credentials → SPA OAuth Clients, turn off Use default logout/callback URLs and Origins, and add:
https://chatgpt.com/connector/oauth/<id>Use the exact
<id>from the authorization URL that ChatGPT opens. Save the CARTO client.Return to ChatGPT, click Sign in, and complete the CARTO consent flow.
Leave the OAuth registration method set to User-Defined OAuth Client. Do not use CIMD for this ChatGPT connection. CARTO's CIMD flow is used for supported Claude clients. If you see “Unknown client,” create a new CARTO SPA OAuth Client and use its Client ID.
Read-only alternative
If you don't control the CARTO OAuth client, you can use a CARTO API Access Token instead of OAuth. Choose Access token / API key in the authentication settings and provide a token with the MCP Server scope.
Add the SQL, Maps, or LDS scopes as needed for additional CARTO tools.
This provides a read-and-discovery subset of the CARTO tool surface and does not enable map or Workflow authoring.
Last updated
Was this helpful?
