An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Google Roads to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Turn noisy GPS traces into clean, actionable road geometry.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 4 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Google Roads.

  1. 01

    Get nearest roads

    This capability finds the closest road segment for up to 100 individual GPS coordinates. It returns the snapped coordinate, the original point, and the place ID for each match.

  2. 02

    Get snapped speed limits

    This capability snaps GPS coordinates to the nearest roads and returns the speed limits in a single request. It provides the snapped coordinates, place IDs, and the legal speed limit for each segment.

  3. 03

    Get speed limits

    This capability retrieves posted speed limits for specific road segments using their place IDs. It returns the speed in km/h along with the corresponding road segment information.

  4. 04

    Snap to roads

    This capability matches a continuous path of GPS coordinates to the most likely roads traveled. It can return interpolated points to create a smooth, clean geometry for your maps.

Real work

What teams actually run

01

Fleet Route Cleaning

Clean up jittery GPS tracks from delivery vehicles to show exactly which streets they drove on.

02

Speed Compliance Audits

Compare vehicle telemetry against posted speed limits to identify speeding incidents.

03

Spatial Data Enrichment

Add road names and place IDs to raw coordinate datasets for better mapping.

04

Route Reconstruction

Build smooth, continuous paths from sparse GPS pings using interpolated points.

Automate a task

Put Google Roads to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Google Roads works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Google Roads to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

899ms average. Fast in production.

Google Roads is checked daily against the live service.

Daily averagePeak 1069ms
Oct 3Today
Fastest day
763ms
Slowest day
1069ms
14-day trend
Slowing+7%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Google Roads, so you can see the experience inside your AI.

It does not authenticate your account with Google Roads. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Google Roads Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_icL7P1wSdhqlP5hejAj1lwlYwJ0IrlWvNXEfqUmc/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Google Roads capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "google-roads-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_icL7P1wSdhqlP5hejAj1lwlYwJ0IrlWvNXEfqUmc/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Google Roads in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Google Roads owners hand off.

This MCP is built for professionals working with vehicle telemetry and geospatial data. You can hand off raw coordinate lists to your agent to get clean, road-aligned data back.

  • 01

    Fleet Managers

    They hand off raw vehicle GPS traces to clean up route visualizations and monitor speed compliance.

  • 02

    Mapping Developers

    They use the agent to convert messy telemetry into smooth, usable road geometries.

  • 03

    Safety Analysts

    They provide road segments to the agent to retrieve speed limits for driver behavior studies.

  • 04

    GIS Professionals

    They use the agent to snap scattered points to road networks for spatial analysis.

FAQ

Questions Google Roads owners ask.

  • 01

    How do I use this with my existing AI capabilities?

    You connect once to Vinkius, and then your AI client (like Claude or Cursor) can immediately use the capabilities through the Model Context Protocol.

  • 02

    Do I need my own Google API key?

    Yes, you will need to provide a Google Maps Platform API key that has the Roads API enabled to power the requests.

  • 03

    Can I snap a whole route at once?

    Yes, the snap_to_roads capability allows you to pass up to 100 coordinate pairs to match a continuous path.

  • 04

    What is the difference between snapping and finding nearest roads?

    Snapping assumes the points form a continuous path along a road, while finding nearest roads treats every coordinate as an independent point.

  • 05

    Does this provide speed limits in miles per hour?

    The API returns speed limits in km/h, though your AI agent can easily convert these to mph for you.

  • 06

    Can my AI snap a GPS track to the actual roads travelled?

    Yes! Use the snap_to_roads capability with your GPS coordinates in path format (latitude,longitude pairs separated by pipes). For example: path=40.7128,-74.0060|40.7135,-74.0055|40.7142,-74.0048. Set interpolate=true for smoother road geometry with additional interpolated points between your input coordinates. The response includes snapped coordinates, original coordinates, and place IDs for each road segment.

  • 07

    How do I get speed limit data for a specific road segment?

    Use the get_speed_limits capability with place IDs obtained from snap_to_roads or get_nearest_roads responses. For example: place_ids=ChIJplaceId1|ChIJplaceId2|ChIJplaceId3. The API returns speed limits in km/h for each road segment. If you need both snapped coordinates AND speed limits in one call, use get_snapped_speed_limits with a GPS path instead.

  • 08

    What is the difference between snap_to_roads and get_nearest_roads?

    snap_to_roads assumes your coordinates form a continuous path and snaps them to the most likely sequence of roads travelled, with optional interpolation for smoother geometry. get_nearest_roads treats each coordinate independently and finds the nearest road segment for each point without assuming they form a path. Use snap_to_roads for GPS tracks and routes, and get_nearest_roads for scattered individual points.

Explore

More in Industry Titans

Suggestions

Connect Google Roads to Claude, Cursor, ChatGPT & more