# How to connect Tomtom to OpenClaw (paste one key, 82 tools) > Connect Tomtom to OpenClaw with ClawLink: paste your Tomtom key once and 82 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/tomtom The usual route to Tomtom access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Tomtom setup: install one ClawHub skill, connect Tomtom in the browser, and OpenClaw can call real Tomtom actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Tomtom. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Tomtom** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect tomtom # connect Tomtom (browser OAuth) npx -y @useclawlink/cli actions tomtom # list available actions npx -y @useclawlink/cli run tomtom --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Tomtom in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Tomtom API key once. Verify the connection by asking OpenClaw: > Use Tomtom to assets list fonts and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Tomtom is connected in the dashboard, that agent calls the same 82 Tomtom tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Tomtom MCP for OpenClaw Looking for a Tomtom MCP server for OpenClaw? ClawLink connects Tomtom to OpenClaw and exposes 82 Tomtom tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Tomtom integration](https://claw-link.dev/hermes/tomtom) works the same way. ## What the OpenClaw Tomtom integration can do 82 Tomtom tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 82. ### 30 of 82 Tomtom tools for OpenClaw | Tool | What it does | |---|---| | **Assets list fonts** `tomtom_assets_list_fonts` | List available font asset versions for map rendering | | **Assets list sprites** `tomtom_assets_list_sprites` | List available sprites for a given asset version | | **Assets list styles** `tomtom_assets_list_styles` | List available map styles | | **Calculate long distance ev route** `tomtom_calculate_long_distance_ev_route` | Calculate long-distance electric vehicle routes with optimal charging stops | | **Calculate matrix routing sync** `tomtom_calculate_matrix_routing_sync` | Calculate route matrix synchronously for multiple origins and destinations (up to 200 cells) | | **Calculate reachable range** `tomtom_calculate_reachable_range` | Calculate the reachable range from a starting point given time, fuel, or energy constraints | | **Calculate route** `tomtom_calculate_route` | Calculate driving routes | | **Calculate route with body** `tomtom_calculate_route_with_body` | Calculate routes with advanced options via POST request | | **Category search** `tomtom_category_search` | Search for Points of Interest by category | | **Create routing batch sync** `tomtom_create_routing_batch_sync` | Execute synchronous batch routing requests for multiple routes or reachable ranges | | **Create routing waypointoptimization** `tomtom_create_routing_waypointoptimization` | Optimize the sequence of waypoints to find the fastest route | | **Create search geometryfilter** `tomtom_create_search_geometryfilter` | Filter POIs by geometric boundaries (circles or polygons) | | **Create snap to roads** `tomtom_create_snap_to_roads` | Snap GPS track points to the road network, correcting for GPS inaccuracies | | **Download batch search async** `tomtom_download_batch_search_async` | Download results of an asynchronous batch search job | | **Download matrix routing async result** `tomtom_download_matrix_routing_async_result` | Download results of asynchronous matrix routing job | | **Download snap to roads async result** `tomtom_download_snap_to_roads_async_result` | Download results of asynchronous snap to roads batch job | | **Ev charging stations available** `tomtom_ev_charging_stations_available` | Retrieve EV charging station availability info | | **Flow segment data** `tomtom_flow_segment_data` | Retrieve traffic flow data for a specific road segment | | **Fuzzy search** `tomtom_fuzzy_search` | Perform a fuzzy search for addresses and points of interest | | **Geocode query** `tomtom_geocode_query` | Convert a free-form address query into geographic coordinates | | **Get autocomplete** `tomtom_get_autocomplete` | Get search suggestions as user types a query | | **Get copyrights** `tomtom_get_copyrights` | Retrieve copyright information for TomTom map tiles | | **Get geometry search** `tomtom_get_geometry_search` | Search for POIs and locations within specified geometric areas (circles or polygons) | | **Get hillshade tile** `tomtom_get_hillshade_tile` | Retrieve hillshade terrain map tiles for specified coordinates and zoom | | **Get incident viewport** `tomtom_get_incident_viewport` | Retrieve incident viewport information including Traffic Model ID | | **Get map copyrights bounding box** `tomtom_get_map_copyrights_bounding_box` | Retrieve copyright information for a geographic bounding box | | **Get map copyrights caption** `tomtom_get_map_copyrights_caption` | Retrieve the copyright caption text for TomTom maps | | **Get map copyrights format** `tomtom_get_map_copyrights_format` | Retrieve copyright information for the whole world in the Maps API Raster Tile Service | | **Get map style metadata** `tomtom_get_map_style_metadata` | Retrieve map style metadata | | **Get map styles** `tomtom_get_map_styles` | Retrieve map style metadata as a Mapbox Style Specification JSON | ## Example prompts **Assets List Fonts** > Use Tomtom to assets list fonts and walk me through the result in plain English. **Assets List Sprites** > Use Tomtom to assets list sprites and walk me through the result in plain English. **Assets List Styles** > Use Tomtom to assets list styles and walk me through the result in plain English. **Calculate Long Distance Ev Route** > Use Tomtom to calculate long distance ev route and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Tomtom working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Tomtom API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Tomtom account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Tomtom. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Tomtom actions to the runtime in a format your agent can reliably use. | 82 tools for Tomtom are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Tomtom to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Tomtom in the browser, and the 82 tools above work from chat. There is no SDK and no config file, and the Tomtom key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Tomtom skill but can't call the tools The ClawHub skill teaches OpenClaw about Tomtom, but the calls run through the ClawLink plugin and your connected account. Make sure Tomtom is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Tomtom from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Tomtom tools Tomtom tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Tomtom call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Tomtom returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Tomtom has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Tomtom integration? Yes. ClawLink is the fastest way to connect OpenClaw to Tomtom: link your Tomtom account once in the browser and OpenClaw can call the Tomtom API through 82 ready-made tools — no custom code or token handling. ### How do I add Tomtom to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Tomtom skill from ClawHub, then you click Connect in the dashboard to authorize Tomtom. OpenClaw calls the tools from the next message — no config files, and the Tomtom key you paste is stored server-side instead of in your environment. ### How long does it take to connect Tomtom to OpenClaw? About two minutes. Sign in, click Connect next to Tomtom in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Tomtom up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Tomtom working from chat. ### OpenClaw installed the Tomtom skill but can't call the tools The ClawHub skill teaches OpenClaw about Tomtom, but the calls run through the ClawLink plugin and your connected account. Make sure Tomtom is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.