In-depth architectural comparison of the Stadiamaps MCP Server Ts and Tomtom MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Stadiamaps MCP Server Ts
Location Services · Local stdio
Quality: 40/100 (Fair) | Auth: API Key required
Tomtom
Location Services · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Stadiamaps MCP Server Ts if you need specialized Location Services tools running via a local process. Choose Tomtom if your workspace requires Location Services integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Stadiamaps MCP Server Ts when:
You need dedicated capabilities in the Location Services domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: API_KEY.
Primary tools included: Address and place geocoding, Current time and time-zone lookup, Routing and travel-time calculation.
Geocoding: convert an address, place name, or free-text location query into geographic coordinates (latitude/longitude). Returns formatted address, country, lat, lon, type, and match score. Example: geocode({ query: "350 5th Ave, New York" })
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Stadiamaps MCP Server Ts is categorized under Location Services and uses a local stdio subprocess. In contrast, Tomtom belongs to Location Services using local stdio subprocess. Select Stadiamaps MCP Server Ts when you need capabilities focused on location services and Tomtom when you require tools for location services.
Search for points of interest (POIs) — businesses, landmarks, restaurants, gas stations, etc. — by name or category, optionally near a lat/lon center within a radius. Returns name, category, address, coordinates, phone, url, and distance. Example: search_poi({ query: "coffee", lat: 40.748, lon: -73…
reverse_geocode
Reverse geocoding: convert latitude/longitude coordinates into a human-readable street address. Returns the freeform address, country, municipality, street name, postal code, and position. Example: reverse_geocode({ lat: 40.748, lon: -73.985 })
route
Traffic-aware routing / directions: calculate the best route between two points and return distance plus travel time computed with live traffic. Reports traffic delay so you get realistic ETAs, not free-flow estimates. Supports car, truck, pedestrian, and bicycle travel modes. Example: route({ from…