Google Roads MCP Server for Mastra AI 4 tools — connect in under 2 minutes
Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Google Roads through Vinkius and Mastra agents discover all tools automatically. type-safe, streaming-ready, and deployable anywhere Node.js runs.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
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: {
"google-roads": {
url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
},
},
});
const tools = await mcpClient.getTools();
const agent = new Agent({
name: "Google Roads Agent",
instructions:
"You help users interact with Google Roads " +
"using 4 tools.",
model: openai("gpt-4o"),
tools,
});
const result = await agent.generate(
"What can I do with Google Roads?"
);
console.log(result.text);
}
main();
* 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 Google Roads MCP Server
Connect your Google Roads API to any AI agent and take full control of GPS map matching, road segment identification, and speed limit data retrieval through natural conversation.
Mastra's agent abstraction provides a clean separation between LLM logic and Google Roads tool infrastructure. Connect 4 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
- Snap to Roads — Match GPS coordinate paths to the most likely roads travelled with interpolated points for smooth road geometry
- Nearest Roads — Find the nearest road segment for up to 100 individual GPS coordinates independently
- Speed Limits — Get posted speed limit data for specific road segments using place IDs from road matching
- Snapped Speed Limits — Snap GPS coordinates to roads AND get speed limits in a single combined request
- Place ID Mapping — Obtain Google place IDs for road segments that can be used with other Google Maps APIs
- Fleet Tracking — Clean noisy GPS traces from fleet vehicles for accurate route visualization
- GPS Correction — Convert raw GPS points into accurate road-level positions for mapping applications
The Google Roads MCP Server exposes 4 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 Google Roads to Mastra AI via MCP
Follow these steps to integrate the Google Roads MCP Server with Mastra AI.
Install dependencies
Run npm install @mastra/core @mastra/mcp @ai-sdk/openai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token
Run the agent
Save to agent.ts and run with npx tsx agent.ts
Explore tools
Mastra discovers 4 tools from Google Roads via MCP
Why Use Mastra AI with the Google Roads MCP Server
Mastra AI provides unique advantages when paired with Google Roads through the Model Context Protocol.
Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add Google Roads without touching business code
Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation
TypeScript-native: full type inference for every Google Roads tool response with IDE autocomplete and compile-time checks
One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure
Google Roads + Mastra AI Use Cases
Practical scenarios where Mastra AI combined with the Google Roads MCP Server delivers measurable value.
Automated workflows: build multi-step agents that query Google Roads, process results, and trigger downstream actions in a typed pipeline
SaaS integrations: embed Google Roads as a first-class tool in your product's AI features with Mastra's clean agent API
Background jobs: schedule Mastra agents to query Google Roads on a cron and store results in your database automatically
Multi-agent systems: create specialist agents that collaborate using Google Roads tools alongside other MCP servers
Google Roads MCP Tools for Mastra AI (4)
These 4 tools become available when you connect Google Roads to Mastra AI via MCP:
get_nearest_roads
Returns the snapped coordinate, the original coordinate, and the place ID for each nearest road segment. Unlike snapToRoads which assumes coordinates form a continuous path, nearestRoads treats each point independently. Essential for reverse geocoding, finding which road a vehicle is on, identifying road segments for individual location points, and mapping scattered GPS points to roads. Each point is matched to the nearest road segment within a reasonable distance. Place IDs can be used with the speed limits endpoint. AI agents should reference this when users ask "what road is at these coordinates", "find the nearest road for each GPS point", or need to map individual location points to road segments without assuming a path. Get the nearest road segments for up to 100 individual GPS coordinates
get_snapped_speed_limits
Snaps GPS coordinates to the nearest road segments and returns both the snapped coordinates with place IDs AND the speed limits for each road segment. This is more efficient than making separate calls to snapToRoads and then speedLimits. Returns snapped points with place IDs, original coordinates, and speed limit data in km/h for each road segment. Essential for applications that need both map-matched road geometry and speed limit data, such as fleet management, driver safety monitoring, route planning with speed awareness, and GPS track analysis. AI agents should reference this when users ask "snap these GPS points to roads and show speed limits", "get both snapped coordinates and speed limits for this route", or need combined road matching and speed limit data in one call. Snap GPS coordinates to roads and get speed limits in a single request
get_speed_limits
Returns speed limit values in km/h along with the place IDs and corresponding road segment information. Place IDs are obtained from the snapToRoads or nearestRoads responses. Essential for speed compliance monitoring, fleet safety management, driver behavior analysis, and road safety applications. Speed limits reflect posted legal limits and may vary by road type, urban/rural designation, and local regulations. AI agents should use this when users ask "what is the speed limit on this road segment", "get speed limits for these place IDs", or need speed limit data for specific road segments identified through map matching. Get speed limit data for specific road segments using place IDs
snap_to_roads
Returns snapped coordinates with place IDs, original coordinates, and interpolated points along the road. Essential for map matching, GPS track correction, route reconstruction, fleet tracking visualization, and converting raw GPS traces into clean road geometries. The path parameter accepts up to 100 coordinate pairs in "lat,lng|lat,lng" format. Set interpolate=true to return additional points between input coordinates for smoother road geometry. Place IDs returned can be used with the speed limits endpoint to get speed limit data for each road segment. AI agents should use this when users ask "snap this GPS track to roads", "match these coordinates to the actual roads travelled", or need to clean up noisy GPS data for mapping and visualization. Snap GPS coordinates to the most likely roads travelled using Google Roads API
Example Prompts for Google Roads in Mastra AI
Ready-to-use prompts you can give your Mastra AI agent to start working with Google Roads immediately.
"Snap these GPS coordinates to roads: 40.7128,-74.0060|40.7135,-74.0055|40.7142,-74.0048"
"Get speed limits for these place IDs: ChIJd8BlQ2BZwokRAFUEcm_qrcA|ChIJd8BlQ2BZwokRAFUEcm_qrcB"
"Find the nearest road to these coordinates: 34.0522,-118.2437 and 34.0530,-118.2445"
Troubleshooting Google Roads MCP Server with Mastra AI
Common issues when connecting Google Roads to Mastra AI through the Vinkius, and how to resolve them.
createMCPClient not exported
npm install @mastra/mcpGoogle Roads + Mastra AI FAQ
Common questions about integrating Google Roads MCP Server with Mastra AI.
How does Mastra AI connect to MCP servers?
MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.Can Mastra agents use tools from multiple servers?
Does Mastra support workflow orchestration?
Connect Google Roads 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.
Connect Google Roads to Mastra AI
Get your token, paste the configuration, and start using 4 tools in under 2 minutes. No API key management needed.