4,500+ servers built on MCP Fusion
Vinkius
TomTom logo
Vinkius
CrewAI logo

How to Use the TomTom MCP in CrewAI

Run autonomous operations with TomTom using CrewAI multi-agent teams.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

TomTom MCP on Cursor AI Code Editor MCP Client TomTom MCP on Claude Desktop App MCP Integration TomTom MCP on OpenAI Agents SDK MCP Compatible TomTom MCP on Visual Studio Code MCP Extension Client TomTom MCP on GitHub Copilot AI Agent MCP Integration TomTom MCP on Google Gemini AI MCP Integration TomTom MCP on Lovable AI Development MCP Client TomTom MCP on Mistral AI Agents MCP Compatible TomTom MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
CrewAI

Connect TomTom MCP to CrewAI

Create your Vinkius account to connect TomTom 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

Coordinating complex travel analysis

A dedicated agent can use `calculate_route` to determine the best path and summary time. Another specialized agent handles feasibility checks with `calculate_reachable_range`, confirming if the destination is physically possible given a time budget. The crew works together: one researches routes, another analyzes the necessary travel time, making the whole operation autonomous.

Gathering deep Point of Interest data

One agent can use `search_poi_by_category` to find general locations like 'restaurants' near a center coordinate. A second agent then uses `get_poi_details` on the specific ID found, pulling rich metadata like operating hours or reviews. This role-based specialization ensures that you get both the list of candidates and the deep dive details needed for action.

Processing raw location inputs

When input is messy, one agent uses `fuzzy_geocoding` to clean up a partial or misspelled physical address into precise coordinates. This ensures the subsequent agents have reliable starting data. If you only get coordinates but need a formal street name, another specialized agent runs `reverse_geocoding`, turning raw points into usable addresses.

Setup guide

Set up TomTom MCP in CrewAI

Prerequisites

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

    Install CrewAI

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

  2. 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. 3

    Kick off your crew

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

crew.py
from crewai import Agent, Task, Crew

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

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

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

Why Choose Vinkius

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

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 TomTom MCP in CrewAI

The crew uses `calculate_route` to establish the initial path and summary. If traffic is a concern, one agent runs `get_traffic_flow_segment` to check segment quality, allowing the team to automatically recommend an alternate route.
The server manages both `structured_geocoding` for highly reliable input (like ZIP codes and country codes) and `fuzzy_geocoding` when the user provides vague or misspelled address strings. The crew selects the right tool based on input quality.
Absolutely. One agent can call `get_traffic_incidents` using a min/max coordinate bounding box to check for accidents or closures. This live data feeds into the team, allowing them to adjust the final plan immediately.
This server manages geographic coordinates, detailed Point of Interest metadata, and real-time traffic flow speed metrics. It handles all necessary spatial data for autonomous operations.
Yes. One agent searches using `search_poi_by_category`, and another takes the resulting ID to call `get_poi_details`. The collaborative approach ensures you get both a list of candidates and their full metadata.

Start using the TomTom MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for TomTom. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.