How to Use the TomTom Alternative MCP in CrewAI

Q: Does TomTom Alternative support advanced routing constraints in CrewAI?

It does. You can task a specific agent with calling calculateadvancedroute and giving it complex parameters, like mandatory waypoints or vignette avoidance rules, making the resulting operation highly specialized.

Run autonomous mapping operations with TomTom Alternative and CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect TomTom Alternative MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinated Geocoding Tasks with CrewAI

You can assign one agent to research addresses using `fuzzy_search`. Once that agent identifies potential POIs, a second specialist agent takes over and calls `geocode` on the selected results. This team structure ensures role specialization. The first agent finds candidates; the second acts as the data converter, providing clean coordinates for action.

Multi-Step Routing Protocols with CrewAI

A core function is calculating routes. You can give one agent the task of calling `calculate_advanced_route` with complex constraints like avoiding vignettes. A second, monitoring agent then checks for current conditions by invoking `get_traffic_incidents`, ensuring the final suggested route is viable before presenting it.

Building Map Visualizations with CrewAI

For visualization, have a dedicated 'Mapper' agent. This agent takes confirmed coordinates and uses the `get_map_tile` tool to fetch the corresponding URL. The output is pure data—a usable tile link. The shared memory of the crew ensures that all previous steps (like the original address input) are available contextually for the final map generation.

Setup guide

Set up TomTom Alternative 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 TomTom Alternative tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent TomTom Alternative 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="TomTom Alternative Analyst",
        goal="Access and analyze TomTom Alternative data via MCP.",
        backstory="Expert analyst with direct TomTom Alternative access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent TomTom Alternative 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 TomTom. 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 TomTom Alternative 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 TomTom Alternative MCP in CrewAI

CrewAI runs specialized agents, and they all use the MCP Server tools. You assign roles—one agent researches addresses using `fuzzy_search`, another calculates routes using `calculate_route`—and the crew manages the handoff between them.

Yes. You can build an autonomous operation where Agent A finds the address via `fuzzy_search`, and Agent B immediately converts that result to coordinates using `geocode`. The crew handles the entire sequence.

The server deals heavily with geographic coordinate and address data. When designing your autonomous workflow, you must ensure that all agents adhere to strict protocols when handling this location information via the MCP Server.

It does. You can task a specific agent with calling `calculate_advanced_route` and giving it complex parameters, like mandatory waypoints or vignette avoidance rules, making the resulting operation highly specialized.

The advantage of CrewAI is delegation. Instead of one massive API call, you break down the task: Agent A handles search, Agent B checks traffic via `get_traffic_incidents`, and Agent C confirms the final map tile URL using `get_map_tile`.

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