mcp · Global

CARTO MCP Server

Remote MCP over CARTO — explore data, render Builder maps inline, run saved spatial Workflows on your cloud warehouse

Claim this listing

Represent CARTO MCP Server? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Data offered docs-verified: warehouse connection and table browsing/search · column distribution inspection · Builder map create/edit with inline rendering · Workflow authoring, validation, run and scheduling · spatial SQL · geocoding · isolines and routes · Data Observatory enrichment · geospatial file import/export
Coverage llm-inferred: Global (catalogue tag; depends on the connected warehouse)
Formats llm-inferred: MCP streamable HTTP
Access docs-verified: OAuth (U2M or M2M) or API Access Token; usage counts toward CARTO quota; no licence given in catalogue metadata

Use cases llm-inferred: Query client warehouse layers (site boundaries, receptors, asset points) with spatial SQL for a constraints overlay · Geocode site addresses and compute isolines or routes for access or catchment-distance analysis · Build a Builder map of project data for client review, then schedule a Workflow that refreshes the enriched dataset
Audience llm-inferred: GIS analysts · environmental consultants · drainage engineers · planners · data analysts

Constraints llm-inferred: Interactive maps render inline only in MCP clients with MCP Apps support (Claude.ai, ChatGPT, Claude Desktop); other clients get a text reply and must open the map URL · API Access Token is read-and-discovery only: no map or Workflow authoring, no admin, and it can poll but not start Workflow runs · Available tools depend on the signed-in user's role; admin tools appear only for Admins · Works on the user's own connected warehouse data; the docs describe no built-in UK or water-specific datasets · Requires a CARTO account and counts toward usage quota · Self-hosted and dedicated deployments use a different URL path (/api/ prefix) · Tool catalogue is expanding over time, so tool names and parameters may change · No licence given in catalogue metadata

Verified 2026-10-15 via curl (HTTP 200). Listed in sparkgeo/geo-mcp-servers.

Metadata observed 14/10/2026 · research sweep: manual-2026-10-15 (sparkgeo/geo-mcp-servers)