How to Use the Google Roads MCP in CrewAI

Q: Can a CrewAI analyst agent query Google Roads speed limits?

Yes, you can assign the getspeedlimits tool to a specific analyst agent in your crew. The analyst agent will fetch the speed data using place IDs provided by the mapping agent.

Q: Can I limit which CrewAI agents access the roads API?

Yes, you can use the MCPServerHTTP tool filter to expose specific tools to specific agents. For example, you can give your mapping agent access to snaptoroads while blocking your reporting agent from it.

Equip your CrewAI agent teams with Google Roads to snap tracks and monitor speed compliance autonomously.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Google Roads MCP to CrewAI

Create your Vinkius account to connect Google Roads to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Google Roads with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Clean noisy GPS tracks with CrewAI

The `snap_to_roads` tool cleans up noisy coordinate points by mapping them to the actual roads traveled. Send raw telematics data to this endpoint to convert it into clean, logical paths. Once the tracking agent cleans the path, it passes the clean coordinates to an analysis agent. This multi-agent setup lets you isolate raw data cleaning from your core business logic.

Audit speed compliance using this MCP Server

The `get_snapped_speed_limits` tool retrieves both snapped coordinates and posted speed limits for a given path. Run this tool to check if drivers are speeding. If the compliance agent detects a violation, it hands the case off to a moderator agent. The moderator agent can then draft an email or log the incident, running the entire audit autonomously.

Map scattered coordinates across agent teams

The `get_nearest_roads` tool maps individual GPS points to the nearest road segments without assuming a continuous path. Use this endpoint to locate scattered vehicles and find their exact road segments. This tool is critical when vehicles send sporadic location pings. The dispatch agent matches each independent ping to a road, letting your routing agent calculate the next pickup point.

Setup guide

Set up Google Roads MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Google Roads tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Google Roads Analyst",
    goal="Access and analyze Google Roads data via MCP.",
    backstory="Expert analyst with direct Google Roads access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Google Roads transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Google Roads Analyst",
        goal="Access and analyze Google Roads data via MCP.",
        backstory="Expert analyst with direct Google Roads access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Google Roads transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Google Roads. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Google Roads now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Google Roads MCP in CrewAI

Pass the Vinkius MCP server URL directly into your CrewAI Agent's `mcps` list. This gives the agent immediate access to tools like `snap_to_roads` and `get_speed_limits`.

Yes, you can assign the `get_speed_limits` tool to a specific analyst agent in your crew. The analyst agent will fetch the speed data using place IDs provided by the mapping agent.

CrewAI agents use shared memory to pass coordinates and place IDs. The mapping agent calls `snap_to_roads` and stores the resulting place IDs, which the compliance agent then uses to query speed limits.

Yes, you can use the `MCPServerHTTP` tool filter to expose specific tools to specific agents. For example, you can give your mapping agent access to `snap_to_roads` while blocking your reporting agent from it.

All place IDs and vehicle coordinates are processed through a secure, ephemeral V8 isolate on this MCP server. No telemetry data is logged or cached, keeping your fleet's operational routes completely confidential.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript