Google Maps logo
ConnectorGoogle Maps

Google Maps integration for Claude and Codex

Create a Google Maps connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.

Use Google Maps from Claude

Add the Google Maps connection to a Space that runs Claude, then use it from every channel in that Space.

Use Google Maps from Codex

Add the Google Maps connection to a Space that runs Codex, then use it from every channel in that Space.

Use Google Maps from Sidekick

Connect your own OpenClaw to Sidekick while Type provides the conversations, permissions, connections, skills, and automations.

Developer Tools & IT

What the Google Maps connector can do

Integrate Google Maps to access location data, geocoding, directions, and mapping services in your application.

One connection, many Spaces

Connect Google Maps once, then decide which Spaces can use it in threads, skills, automations, and coding work.

Representative actions

  • Autocomplete Place Predictions

    Returns place and query predictions for text input. Use when implementing as-you-type autocomplete functionality for place searches. Returns up to five predictions ordered by relevance.

  • Compute Route Matrix

    Calculates travel distance and duration matrix between multiple origins and destinations using the modern Routes API; supports OAuth2 authentication and various travel modes. Matrix is capped at 625 elements (e.g., 25×25); chunk larger sets to avoid RESOURCE_EXHAUSTED errors. Response elements may be returned out of input order — always use originIndex and destinationIndex to map results. Only use elements where condition='ROUTE_EXISTS'; the matrix may be incomplete.

  • Distance Matrix (Legacy)

    DEPRECATED: Legacy API that calculates travel distance and time for a matrix of origins and destinations. This API only works with API keys (no OAuth2 support). Use the modern 'Compute Route Matrix' action instead, which supports OAuth2 authentication. Supports different modes of transportation and options like departure/arrival times. Capped at 100 elements per request (elements = origins × destinations count); split large sets into batches.

  • Geocode Address

    DEPRECATED: Legacy API to convert street addresses into geographic coordinates (latitude and longitude). This API works best with API key authentication. For OAuth connections without an API key, you may need to provide the 'key' parameter or use the newer 'Text Search' action instead. Use when you need to geocode an address or location to get its precise latitude/longitude coordinates.

  • Geocode Address With Query

    Tool to map addresses to geographic coordinates with query parameter. Use when you need to convert a textual address into latitude/longitude coordinates using the modern v4beta API. Results may match multiple places — always verify `formattedAddress`, `region`, and `addressComponents` in the response before using returned coordinates.

Connection

API and auth details

Google Maps Platform APIs primarily use API keys for server-side web service requests, with product-specific endpoints for geocoding, places, routes, maps, and time zones.

FAQ

Questions people ask before connecting Google Maps

Can Claude use Google Maps?

Yes. Add a Google Maps connection to a Space that runs Claude, then use its approved tools and data from any channel in that Space.

Can Codex work with Google Maps through Type?

Yes. Add a Google Maps connection to a Space that runs Codex, then use its approved tools and data from any channel in that Space.

Is this the same as a Google Maps MCP server?

Not exactly. Type uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.

More developer tools & it connectors