Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP

Google Maps Platform + Grounding Lite MCP

Maps Grounding Lite is GA, hosted, and takes an X-Goog-Api-Key header or OAuth with the maps-platform.mapstools scope. A Cloud billing account with a payment method is required before the free caps apply.

TomTom Maps APIs + MCP

No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month. Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified.

Google Maps Platform + Grounding Lite MCP

1. Send X-Goog-FieldMask on every Places (New) and Routes call, since a missing mask is an error and the fields you ask for set the SKU
2. Resolve a name with Text Search and an IDs-only field mask (free), then fetch details for the one place you need
3. Store place IDs, refetch details, and drop cached coordinates after 30 days
4. Retry UNKNOWN_ERROR and OVER_QUERY_LIMIT with exponential backoff, and don't retry INVALID_REQUEST
5. Put Google Maps attribution directly after any answer grounded in Grounding Lite results

TomTom Maps APIs + MCP

1. Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address
2. Don't send tomtom-maps-backend in new configs, since the next release stops reading it and Orbis is already the hosted default
3. Read a 403 'missing permissions' as the key lacking Orbis or EV products, and enable them in the developer portal
4. Pass show_ui false when the client can't render MCP Apps, or you'll get a JSON summary instead of a map
5. Redact the key parameter before logging REST URLs