TomTom MCP server
7 operations0 webhooks
Search places and addresses, geocode both ways, calculate routes, and read live traffic incidents and flow.
Try TomTom with your agent
Connect TomTom, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in TomTom on my account, then run one read-only example and show me the result.
TomTom tools and triggers
Tools are what your agent can do in TomTom through Corsair's MCP server. Triggers are the TomTom events a routine can start from.
Search
- FuzzyRead-only
Search for places, addresses, streets and geography, with optional geo bias and country filters
search.fuzzy
- GeocodeRead-only
Turn an address into coordinates
search.geocode
- Reverse GeocodeRead-only
Turn coordinates into the nearest address
search.reverseGeocode
Traffic
- FlowRead-only
Read the current speed and free-flow speed on the road at a point
traffic.flow
- IncidentsRead-only
List live traffic incidents in a bounding box, with their delay and road numbers
traffic.incidents
- TileRead-only
Fetch one traffic flow or incident map tile
traffic.tile
Routing
- CalculateRead-only
Calculate a route between waypoints with travel mode, traffic and avoidance options; makes no booking
routing.calculate
Connect TomTom to Claude, ChatGPT or Cursor
- 1
Connect TomTom in Corsair
Add your TomTom API key once in Corsair. Corsair stores the credential encrypted and makes the TomTom API calls for your agent, so it never goes into a prompt or a config file. Connect TomTom
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs TomTom. On a ChatGPT personal plan, connect TomTom here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. Every TomTom operation only reads data, so it runs right away in every mode.
FAQ
Install corsair and @corsair-dev/tomtom, add the TomTom plugin, and connect with an API key. Then call methods like corsair.tomtom.api.routing.calculate() from your app. Corsair keeps each tenant isolated.
Yes. TomTom requires an API key from your TomTom account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit TomTom, GitHub, Notion, Stripe, and the rest. Trigger TomTom from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for search places and addresses, geocode both ways, calculate routes, and read live traffic incidents and flow. Common builds include sync jobs, admin tooling, and agents that call TomTom APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per TomTom API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/tomtom in the open repo. When TomTom ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your TomTom data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store TomTom data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put TomTom on a link in Strict mode and every write waits for your approval, while destructive actions are refused. Every TomTom operation only reads data, so there are no changes to approve today. You can change a link's mode at hub.corsair.dev/me.