Skip to content
Conduit

skill

hermes-mcp-tomtom

TomTom Maps MCP integration for Hermes-Agent — search, routing, traffic, maps, and EV via hosted MCP endpoint

Drknght4/hermes-mcp-tomtomcommunitylistedunreviewed

Set up

Skills are installed by placing their folder where your agent loads skills.

The download comes from github.com/Drknght4/hermes-mcp-tomtom itself, not from our server, so what you get is exactly what its author published.

Install instructions come from the README

Skills do not use an MCP config. Follow the steps in the README below.

README

synced Oct 22, 2026

hermes-mcp-tomtom

TomTom Maps MCP server integration for 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.

What This Gives You

16 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.

ToolDescription
tomtom-geocodeAddress → coordinates (+ interactive map)
tomtom-reverse-geocodeCoordinates → address (+ interactive map)
tomtom-fuzzy-searchTypo-tolerant search for addresses, POIs, geographies
tomtom-poi-searchSearch by business name or browse POI categories
tomtom-nearbyFind places close to a specific point
tomtom-poi-categoriesLook up POI category codes from natural language
tomtom-area-searchFind all POIs within a geographic boundary (polygon/bbox/circle)
tomtom-ev-searchFind EV charging stations with real-time availability
tomtom-search-along-routeFind POIs along a route (gas, restaurants, hotels)
tomtom-routingCalculate optimal routes through ordered locations
tomtom-reachable-rangeArea reachable within specified time or distance
tomtom-ev-routingEV routes with automatic charging stop optimization
tomtom-trafficTraffic incidents in an area on an interactive map
tomtom-dynamic-mapCustom map images with markers, lines, polygons, overlays
tomtom-data-vizCustom GeoJSON data on a TomTom basemap
tomtom-get-api-keyInternal — retrieve the configured API key

Setup

1. Get a TomTom API Key

Sign up at developer.tomtom.com and create an API key with these products enabled:

  • Search API
  • Routing API
  • Traffic API
  • Map Display API
  • MCP Server access

2. Add API Key

echo 'TOMTOM_API_KEY=your_key_here' >> ~/.hermes/.env

3. Configure Hermes

Add the MCP server block to ~/.hermes/config.yaml (see config-snippet.yaml):

mcp_servers:
  tomtom:
    url: https://mcp.tomtom.com/maps
    headers:
      tomtom-api-key: ${TOMTOM_API_KEY}
    timeout: 120
    connect_timeout: 60

4. Restart the Gateway

hermes gateway restart

5. Verify

hermes mcp list
# Should show: tomtom  https://mcp.tomtom.com/maps  all  ✓ enabled

All 16 tools register with the mcp_tomtom_tomtom_ prefix (e.g., mcp_tomtom_tomtom_routing).

Orbis Maps (Optional)

To use TomTom's next-gen Orbis Maps platform, add the tomtom-maps-backend header:

mcp_servers:
  tomtom:
    url: https://mcp.tomtom.com/maps
    headers:
      tomtom-api-key: ${TOMTOM_API_KEY}
      tomtom-maps-backend: tomtom-orbis-maps
    timeout: 120
    connect_timeout: 60

Defaults to classic TomTom Maps when the header is omitted.

Common Tool Parameters

All search/geocoding tools accept:

  • show_ui (boolean) — interactive map widget visualization
  • response_detail ("compact" default, "full" for complete data)
  • language — IETF tag (e.g., "en-US", "fr-FR")
  • countries — array of ISO alpha-2 codes (e.g., ["US"])
  • limit — max results 1–100, default 5

Coordinate Convention

All 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.

Pitfalls

  • API key exposure: The tomtom-get-api-key tool returns the key to any caller. Restrict in untrusted contexts.
  • Free tier: Standard plan covers Search, Routing, Traffic, and Maps. Advanced APIs require paid access.
  • Rate limits: 5 QPS for Search, 1 QPS for Routing on standard tier.
  • ${TOMTOM_API_KEY} interpolation: The Hermes MCP loader resolves ${VAR_NAME} from ~/.hermes/.env at connection time. Never hardcode keys in config.yaml.

Skill Reference

See SKILL.md for the full tool reference with parameters and usage examples.

License

MIT


Built by NoVa AI — Your Data. Your Rules. Your AI.

↑↓ navigate openesc close