CARTO MCP Server
Empower your AI agents to execute spatial SQL, generate routes, create driving isolines, and bulk geocode directly on CARTO.
Ask AI about this MCP Server
Vinkius supports streamable HTTP and SSE.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
What is the CARTO MCP Server?
The CARTO MCP Server gives AI agents like Claude, ChatGPT, and Cursor direct access to CARTO via 10 tools. Empower your AI agents to execute spatial SQL, generate routes, create driving isolines, and bulk geocode directly on CARTO. Powered by the Vinkius - no API keys, no infrastructure, connect in under 2 minutes.
Built-in capabilities (10)
Tools for your AI Agents to operate CARTO
Ask your AI agent "Execute a SQL query limiting to 10 rows on my 'retail_stores' dataset to check the schema." and get the answer without opening a single dashboard. With 10 tools connected to real CARTO data, your agents reason over live information, cross-reference it with other MCP servers, and deliver insights you would spend hours assembling manually.
Works with Claude, ChatGPT, Cursor, and any MCP-compatible client. Powered by the Vinkius - your credentials never touch the AI model, every request is auditable. Connect in under two minutes.
Why teams choose Vinkius
One subscription gives you access to thousands of MCP servers - and you can deploy your own to the Vinkius Edge. Your AI agents only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure and security, zero maintenance.
Build your own MCP Server with our secure development framework →Vinkius works with every AI agent you already use
…and any MCP-compatible client


















CARTO MCP Server capabilities
10 toolsThe range parameter is in seconds for time-based isolines. Returns a GeoJSON polygon representing the reachable area. Use for service area analysis, store catchment zones, and logistics planning. Generate travel-time or travel-distance isoline polygons from a center point using the CARTO LDS Isolines API, producing reachability contours showing areas accessible within a specified time or distance threshold
Returns the route as GeoJSON with total distance (meters) and duration (seconds). Consumes LDS routing credits. Calculate the optimal driving route between two points using the CARTO LDS Routing API, returning distance, duration, and route geometry suitable for visualization on CARTO maps
"}`. Returns a job_id that can be polled for completion status. Use for ETL operations, materialized view refreshes, and heavy geospatial computations. The job runs in your data warehouse and results are stored there. Submit a long-running SQL query as an asynchronous batch job via the CARTO SQL Job API, suitable for heavy spatial analytics, large table transformations, and complex multi-join operations that exceed the 60-second synchronous timeout
carto.com/api/v2/sql?q=`. The query runs synchronously with a 1-minute timeout. Use for quick analytical queries, spatial joins, and data exploration. For long-running queries exceeding 60 seconds, use the async job endpoint instead. Supports PostGIS/BigQuery spatial functions natively. Execute an arbitrary SQL query against your CARTO data warehouse connection using the SQL API v2, returning results as JSON rows directly from BigQuery, Snowflake, Redshift, or PostgreSQL
Returns latitude, longitude, and formatted address. Consumes LDS geocoding credits from your CARTO plan. Use sparingly for individual lookups; for bulk operations use the batch endpoint instead. Forward-geocode a single address string into geographic coordinates using the CARTO Location Data Services (LDS) geocoding endpoint, powered by TomTom or HERE depending on your CARTO plan configuration
Designed for bulk processing of customer lists, store locators, and CRM datasets. Consumes LDS credits per address. Returns an array of geocoded results with match quality indicators. Batch-geocode multiple addresses in a single request using the CARTO LDS batch geocoding API, efficiently converting large address lists into coordinates without making individual API calls per address
Poll periodically until state becomes "complete" or "failure". On success, the response includes the table_name of the newly created dataset in your warehouse. Check the status of a previously initiated CARTO data import job, returning progress percentage, current state (uploading, importing, complete, failure), and any error details if the import encountered issues
"}`. Supports CSV, GeoJSON, Shapefile (zipped), KML, GPX, and Excel files. Returns an import_id for status tracking. The file is downloaded, parsed, and loaded into your connected data warehouse. Import an external data file (CSV, GeoJSON, Shapefile, KML) into your CARTO data warehouse by providing a publicly accessible URL, creating a new managed table that can be used for spatial analysis and visualization
Returns an array of dataset/visualization objects. Use to discover available data layers, check dataset freshness, and audit organization assets. List all visualization datasets (maps and tables) available in your CARTO organization, returning metadata including creation dates, privacy settings, table names, and row counts
Poll periodically (every 5-10 seconds) until status changes to "done" or "failed". The response includes created_at, updated_at, and the original query for audit purposes. Check the execution status of a previously submitted CARTO async SQL job, returning the current state (pending, running, done, failed) and any error messages if the job encountered issues
What the CARTO MCP Server unlocks
Connect your CARTO platform to any AI agent and take full control of your cloud-native spatial analytics without touching the GIS interface.
What you can do
- Spatial SQL & Jobs — Command explicit SQL queries running directly against your BigQuery, Snowflake, or Redshift warehouse. Execute quick reads or spawn long-running, asynchronous batch transformations.
- Geocoding & Batching — Convert unstructured strings into precise lat/lon points. Bulk-process 100s of addresses using CARTO's native Location Data Services (LDS) gracefully.
- Isolines & Reachability — Calculate travel-time or distance polygons around origin points to instantly graph accessible zones via cars or walking.
- Routing — Generate optimal vector geometry paths connecting two points on the globe, measuring both physical distance and travel time securely.
- Data Management — Instruct your agent to list active mapping datasets or import massive external CSV/GeoJSON files directly via public URLs.
How it works
1. Subscribe to this server
2. Provide your active CARTO Organization and API Key
3. Start mapping, slicing spatial boundaries, and scripting data operations using Claude, Cursor, or any compatible AI
Who is this for?
- GIS Analysts & Data Scientists — Execute testing queries natively and bulk-geocode customer coordinates from a conversational terminal.
- Retail & Logistics Strategists — Ask your AI to calculate 15-minute delivery isolines and cross-reference them with population layers using SQL.
- Data Engineers — Trigger raw data imports and handle heavy dataset syncs without opening the graphical workspace.
Frequently asked questions about the CARTO MCP Server
Can my AI agent orchestrate heavy spatial analytics on large datasets directly?
Yes. While small checks use the immediate SQL endpoint, your agent knows how to use the async Job API to submit massive postGIS or BigQuery geospatial operations on millions of rows. It automatically polls the remote status and notifies you once your heavy data transformation is structurally completed.
Am I able to geocode raw customer addresses in bulk through the agent?
Definitely. Give your agent a list of unstructured addresses and it will fire the bulk geocode_batch_addresses tool. CARTO’s native LDS engine (powered by TomTom/HERE) returns the validated geo-coordinates for each row, avoiding manual CSV matching.
Can the agent create travel-time polygons (Isolines)?
Absolutely. The agent uses the calculate_isoline tool passing the desired travel duration and coordinate center. It immediately receives a precise GeoJSON polygon defining the catchment zone or service area, without requiring you to use the map UI.
More in this category
You might also like
Connect CARTO with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Give your AI agents the power of CARTO MCP Server
Production-grade CARTO MCP Server. Verified, monitored, and maintained by Vinkius. Ready for your AI agents — connect and start using immediately.






