Maps & transport · Remote MCP server
CARTO
Query your data warehouses, run workflows, and render maps from your CARTO workspace.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.carto/carto- Version
- 1.0.1
- Status
- Active
- Category
- maps & transport
- Transport
- Streamable HTTP
- Published
- 2026-08-19
- Updated
- 2026-08-19
- Publisher
- com.carto
- Namespace
- Namespace verified by the MCP Registry via the domain carto.com · how
- Listed under
- Maps MCP servers
- Website
- docs.carto.com/carto-for-agents/mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://{region}.api.carto.com/mcp/{account_id} | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect CARTO
CARTO is a remote MCP server: there is nothing to install. Its endpoint is https://{region}.api.carto.com/mcp/{account_id}, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {account_id} and {region}.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, docs.carto.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More maps & transport servers
| Server | Runs |
|---|---|
| CarShakeVehicle handover checklists, damage-documentation best practices, valet/rental/service FAQs. | Remote · HTTPLive check: ✓ handshake |
| CarsMultiverse - the recall recordVehicle safety recalls from four registers, matched across borders on the maker's own code. | Remote · HTTPLive check: ✓ handshake |
| Carso Exchange EngineAI-native platform: cybernetic freight agents transact, verify, find services. Get verified leads. | Remote · HTTPLive check: sign-in required |
| Carsxe MCPMCP server for CarsXE vehicle data: VIN, specs, history, images, recalls, and OBD codes. | Remote · HTTPLive check: sign-in required |
| Carvector MCPVehicle specs, federal recalls, complaints, TSBs, investigations and OBD-II DTC data for AI agents. | Local · stdio |
| CatalogMaritime VSAT spares: part search, fitment, supersession and quote requests for satmarin.com. | Remote · HTTPLive check: ✓ handshake |
| Catastro GPSCadastral parcels in 31 European countries and regions: reference, coordinates, address, geometry. | Local · stdio |
| CbmCalculate shipment volume (CBM/CFT), weight, and how cargo fits standard shipping containers. | Remote · HTTPLive check: ✓ handshake |