> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-for-agents/mcp-server.md).

# CARTO MCP Server

The CARTO MCP Server is the AI integration into your CARTO platform: your workspace, saved Builder maps, workflows, and connected data warehouses. Through the [Model Context Protocol](https://modelcontextprotocol.io/) (MCP), agents like Claude or ChatGPT can explore your data, render interactive maps inline in the chat (ad-hoc visualizations or saved Builder maps), inspect data assets and column distributions, and run your organization's saved analytical workflows.

{% hint style="info" %}
CARTO will expand support over time by exposing core GIS operations (geocoding, isochrones, routing) directly as MCP Tools. Get in touch if you're interested.
{% endhint %}

## Using CARTO MCP Server

Get the **MCP Server URL** from your CARTO Workspace under **Developers > Workflow API & MCP Server** (shown in the CARTO AI section). It follows this pattern:

```
https://<region>.api.carto.com/mcp/<account_id>
```

Then connect to the server using one of the following methods:

* [**OAuth (U2M)**](/carto-for-agents/mcp-server/connecting-with-oauth.md#oauth-u2m). Interactive login with your CARTO account. Claude.ai and Claude Code connect with just the URL (no OAuth client needed); other clients use an SPA OAuth client. Best for interactive clients like Claude.ai or ChatGPT.
* [**OAuth (M2M)**](/carto-for-agents/mcp-server/connecting-with-oauth.md#oauth-m2m). Uses an [M2M OAuth client](/carto-user-manual/developers/managing-credentials/m2m-oauth-clients.md) for unattended access over OAuth.
* [**API Access Token**](/carto-for-agents/mcp-server/connecting-with-api-tokens.md). Unattended access using a token with predefined scopes.

{% hint style="warning" %}
With the **API Access Token** method, the `list_maps` tool is currently unavailable. Every other tool works. Use OAuth (U2M or M2M) if you need `list_maps`.
{% endhint %}

***

## Available tools

The CARTO MCP Server ships with a catalog of built-in tools. Your team can add to it by publishing any workflow as an MCP tool. The catalog is organized into three categories. Full per-tool documentation is in the [MCP Tools Reference](/carto-for-agents/mcp-server/tools-reference.md).

<table><thead><tr><th width="280">Category</th><th>What it does</th></tr></thead><tbody><tr><td><a href="/pages/3u5R5lcTK8JT7zygV3oW"><strong>Platform tools</strong></a></td><td>Help the agent find the right data. List connections, browse and search tables, inspect column distributions, and locate saved maps. Returns JSON for the agent to reason over.</td></tr><tr><td><a href="/pages/cEnllyMfFblR84A3Qb8s"><strong>Interactive tools</strong></a></td><td>Render an interactive map directly inline in the chat. Ad-hoc visualizations the agent composes from your data, or one of your saved CARTO Builder maps.</td></tr><tr><td><a href="/pages/AyFKSPLPoTBMtNk5H9a5"><strong>Workflows tools</strong></a></td><td>Run analytical workflows your team has published as MCP tools, in sync or async mode. Async jobs are driven by two built-in helper tools.</td></tr></tbody></table>

{% hint style="info" %}
Interactive tools render inline only in MCP clients that support [MCP Apps](https://modelcontextprotocol.io/specification/2025-06-18/server/utilities/apps): Claude.ai, ChatGPT, Claude Desktop, and others. In clients that don't, the tools return a text confirmation describing what would have been rendered.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.carto.com/carto-for-agents/mcp-server.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.