{"id":"2a5139bd-c7ce-4b48-a642-b3314bc5fc41","slug":"hermes-mcp-tomtom","kind":"skill","name":"hermes-mcp-tomtom","summary":"TomTom Maps MCP integration for Hermes-Agent — search, routing, traffic, maps, and EV via hosted MCP endpoint","owner":"Drknght4","repoUrl":"https://github.com/Drknght4/hermes-mcp-tomtom","license":"MIT","licenseTier":"permissive","trust":"community","stars":2,"match":null,"fewStars":true,"format":"skill","createdAt":"2026-06-06T20:10:49.000Z","addedAt":"2026-10-21T06:12:53.836Z","logoUrl":"https://avatars.githubusercontent.com/u/75950237?v=4","linkOnly":false,"collection":null,"skillPath":null,"categories":["search","memory-knowledge"],"tags":["hermes-agent","maps","routing","self-hosted","tomtom"],"runtime":"binary","local":true,"cloudCapable":false,"cloudCapability":"unknown","cloudReadyOnPlatform":false,"needsApiKey":false,"reviewed":false,"syncedAt":"2026-10-22T22:29:02.938Z","sample":false,"url":"https://conduits.dev/tools/hermes-mcp-tomtom","language":"","transports":["stdio"],"install":{},"requirements":{"env":[],"upstreamMayCharge":false},"tools":null,"readme":"# hermes-mcp-tomtom\n\nTomTom Maps MCP server integration for [Hermes-Agent](https://github.com/NousResearch/hermes-agent). Wire TomTom's search, routing, traffic, and mapping capabilities into your Hermes instance via the Model Context Protocol — no local server to run, just configure and go.\n\n## What This Gives You\n\n16 MCP tools registered as first-class Hermes tools — geocoding, fuzzy search, POI discovery, routing, EV routing, traffic incidents, interactive maps, and more. All powered by TomTom's hosted MCP endpoint at `https://mcp.tomtom.com/maps`.\n\n| Tool | Description |\n|------|-------------|\n| `tomtom-geocode` | Address → coordinates (+ interactive map) |\n| `tomtom-reverse-geocode` | Coordinates → address (+ interactive map) |\n| `tomtom-fuzzy-search` | Typo-tolerant search for addresses, POIs, geographies |\n| `tomtom-poi-search` | Search by business name or browse POI categories |\n| `tomtom-nearby` | Find places close to a specific point |\n| `tomtom-poi-categories` | Look up POI category codes from natural language |\n| `tomtom-area-search` | Find all POIs within a geographic boundary (polygon/bbox/circle) |\n| `tomtom-ev-search` | Find EV charging stations with real-time availability |\n| `tomtom-search-along-route` | Find POIs along a route (gas, restaurants, hotels) |\n| `tomtom-routing` | Calculate optimal routes through ordered locations |\n| `tomtom-reachable-range` | Area reachable within specified time or distance |\n| `tomtom-ev-routing` | EV routes with automatic charging stop optimization |\n| `tomtom-traffic` | Traffic incidents in an area on an interactive map |\n| `tomtom-dynamic-map` | Custom map images with markers, lines, polygons, overlays |\n| `tomtom-data-viz` | Custom GeoJSON data on a TomTom basemap |\n| `tomtom-get-api-key` | Internal — retrieve the configured API key |\n\n## Setup\n\n### 1. Get a TomTom API Key\n\nSign up at [developer.tomtom.com](https://developer.tomtom.com/) and create an API key with these products enabled:\n\n- Search API\n- Routing API\n- Traffic API\n- Map Display API\n- MCP Server access\n\n### 2. Add API Key\n\n```bash\necho 'TOMTOM_API_KEY=your_key_here' >> ~/.hermes/.env\n```\n\n### 3. Configure Hermes\n\nAdd the MCP server block to `~/.hermes/config.yaml` (see [`config-snippet.yaml`](./config-snippet.yaml)):\n\n```yaml\nmcp_servers:\n  tomtom:\n    url: https://mcp.tomtom.com/maps\n    headers:\n      tomtom-api-key: ${TOMTOM_API_KEY}\n    timeout: 120\n    connect_timeout: 60\n```\n\n### 4. Restart the Gateway\n\n```bash\nhermes gateway restart\n```\n\n### 5. Verify\n\n```bash\nhermes mcp list\n# Should show: tomtom  https://mcp.tomtom.com/maps  all  ✓ enabled\n```\n\nAll 16 tools register with the `mcp_tomtom_tomtom_` prefix (e.g., `mcp_tomtom_tomtom_routing`).\n\n## Orbis Maps (Optional)\n\nTo use TomTom's next-gen Orbis Maps platform, add the `tomtom-maps-backend` header:\n\n```yaml\nmcp_servers:\n  tomtom:\n    url: https://mcp.tomtom.com/maps\n    headers:\n      tomtom-api-key: ${TOMTOM_API_KEY}\n      tomtom-maps-backend: tomtom-orbis-maps\n    timeout: 120\n    connect_timeout: 60\n```\n\nDefaults to classic TomTom Maps when the header is omitted.\n\n## Common Tool Parameters\n\nAll search/geocoding tools accept:\n\n- `show_ui` (boolean) — interactive map widget visualization\n- `response_detail` (`\"compact\"` default, `\"full\"` for complete data)\n- `language` — IETF tag (e.g., `\"en-US\"`, `\"fr-FR\"`)\n- `countries` — array of ISO alpha-2 codes (e.g., `[\"US\"]`)\n- `limit` — max results 1–100, default 5\n\n## Coordinate Convention\n\nAll tools use **[longitude, latitude]** (GeoJSON convention). This applies to `locations` in routing, `position` in reverse geocode, `origin`/`destination` in search-along-route, and marker coordinates in dynamic maps.\n\n## Pitfalls\n\n- **API key exposure**: The `tomtom-get-api-key` tool returns the key to any caller. Restrict in untrusted contexts.\n- **Free tier**: Standard plan covers Search, Routing, Traffic, and Maps. Advanced APIs require paid access.\n- **Rate limits**: 5 QPS for Search, 1 QPS for Routing on standard tier.\n- **`${TOMTOM_API_KEY}` interpolation**: The Hermes MCP loader resolves `${VAR_NAME}` from `~/.hermes/.env` at connection time. Never hardcode keys in `config.yaml`.\n\n## Skill Reference\n\nSee [`SKILL.md`](./SKILL.md) for the full tool reference with parameters and usage examples.\n\n## License\n\nMIT\n\n---\n\nBuilt by NoVa AI — Your Data. Your Rules. Your AI."}