2,500+ MCP servers ready to use
Vinkius

CARTO MCP Server for Mastra AI 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect CARTO through Vinkius and Mastra agents discover all tools automatically. type-safe, streaming-ready, and deployable anywhere Node.js runs.

Vinkius supports streamable HTTP and SSE.

typescript
import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token. get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "carto": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "CARTO Agent",
    instructions:
      "You help users interact with CARTO " +
      "using 10 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with CARTO?"
  );
  console.log(result.text);
}

main();
CARTO
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About CARTO MCP Server

Connect your CARTO platform to any AI agent and take full control of your cloud-native spatial analytics without touching the GIS interface.

Mastra's agent abstraction provides a clean separation between LLM logic and CARTO tool infrastructure. Connect 10 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.

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.

The CARTO MCP Server exposes 10 tools through the Vinkius. Connect it to Mastra AI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect CARTO to Mastra AI via MCP

Follow these steps to integrate the CARTO MCP Server with Mastra AI.

01

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

Mastra discovers 10 tools from CARTO via MCP

Why Use Mastra AI with the CARTO MCP Server

Mastra AI provides unique advantages when paired with CARTO through the Model Context Protocol.

01

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add CARTO without touching business code

02

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

03

TypeScript-native: full type inference for every CARTO tool response with IDE autocomplete and compile-time checks

04

One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure

CARTO + Mastra AI Use Cases

Practical scenarios where Mastra AI combined with the CARTO MCP Server delivers measurable value.

01

Automated workflows: build multi-step agents that query CARTO, process results, and trigger downstream actions in a typed pipeline

02

SaaS integrations: embed CARTO as a first-class tool in your product's AI features with Mastra's clean agent API

03

Background jobs: schedule Mastra agents to query CARTO on a cron and store results in your database automatically

04

Multi-agent systems: create specialist agents that collaborate using CARTO tools alongside other MCP servers

CARTO MCP Tools for Mastra AI (10)

These 10 tools become available when you connect CARTO to Mastra AI via MCP:

01

calculate_isoline

The 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

02

calculate_route

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

03

create_async_sql_job

"}`. 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

04

execute_sql_query

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

05

geocode_address

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

06

geocode_batch_addresses

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

07

get_import_status

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

08

import_external_file

"}`. 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

09

list_map_datasets

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

10

poll_async_job_status

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

Example Prompts for CARTO in Mastra AI

Ready-to-use prompts you can give your Mastra AI agent to start working with CARTO immediately.

01

"Execute a SQL query limiting to 10 rows on my 'retail_stores' dataset to check the schema."

02

"Take these 5 addresses in Madrid and bulk geocode them to lat/lon coordinates."

03

"Generate a 15-minute drive-time isoline around Times Square, New York."

Troubleshooting CARTO MCP Server with Mastra AI

Common issues when connecting CARTO to Mastra AI through the Vinkius, and how to resolve them.

01

createMCPClient not exported

Install: npm install @mastra/mcp

CARTO + Mastra AI FAQ

Common questions about integrating CARTO MCP Server with Mastra AI.

01

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
02

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
03

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

Connect CARTO to Mastra AI

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.