# How to connect Google Maps to Grok Bot (no API keys) > Connect Google Maps to Grok Bot with ClawLink in one click — 19 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/google-maps Grok Bot runs on its own cloud computer, so most Google Maps guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Google Maps setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Google Maps actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect google-maps` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Google Maps. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Google Maps** — `npx -y @useclawlink/cli connect google-maps`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect google-maps # connect Google Maps (browser OAuth) npx -y @useclawlink/cli actions google-maps # list available actions npx -y @useclawlink/cli run google-maps --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect google-maps ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Use Google Maps to autocomplete and walk me through the result in plain English. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Google Maps is connected in the dashboard, that agent calls the same 19 Google Maps tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Google Maps MCP for Grok Bot Looking for a Google Maps MCP server for Grok Bot? ClawLink connects Google Maps to Grok Bot and exposes 19 Google Maps tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Google Maps integration](https://claw-link.dev/openclaw/google-maps) and the [Hermes Google Maps integration](https://claw-link.dev/hermes/google-maps) connect the same ClawLink account the same way. ## What the Grok Bot Google Maps integration can do 19 Google Maps tools are ready for Grok Bot once the account is connected. ### All 19 Google Maps tools for Grok Bot | Tool | What it does | |---|---| | **Autocomplete** `google_maps_autocomplete` | 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** `google_maps_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. | | **Geocode address with query** `google_maps_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. | | **Geocode destinations** `google_maps_geocode_destinations` | Tool to perform destination lookup and return detailed destination information including primary place, containing places, sub-destinations, landmarks, entrances, and navigation points. | | **Geocode location** `google_maps_geocode_location` | Tool to convert geographic coordinates (latitude and longitude) to human-readable addresses using reverse geocoding. Use when you need to find the address or place name for a given set of coordinates. | | **Geocode place** `google_maps_geocode_place` | Tool to perform geocode lookup using a place identifier to retrieve address and coordinates. Use when you need to get detailed geographic information for a specific Google Place ID. | | **Geocoding API** `google_maps_geocoding_api` | Convert addresses into geographic coordinates (latitude and longitude) and vice versa (reverse geocoding), or get an address for a Place ID. | | **Geolocate** `google_maps_geolocate` | Tool to determine location based on cell towers and WiFi access points. Use when you need to find the geographic location of a device using network infrastructure data. | | **Get place details** `google_maps_get_place_details` | Retrieves comprehensive details for a place using its resource name (places/\{place_id\} format). Use when you need detailed information about a specific place. | | **Get route** `google_maps_get_route` | Calculates one or more routes between two specified locations. Uses various travel modes and preferences; addresses must be resolvable by Google Maps. | | **Get2d tile** `google_maps_get2d_tile` | Tool to retrieve a 2D map tile image at specified coordinates for building custom map visualizations. Use when you need to download individual map tile images for roadmap, satellite, or terrain views. | | **Get3d tiles root** `google_maps_get3d_tiles_root` | Tool to retrieve the 3D Tiles tileset root configuration for photorealistic 3D map rendering. | | **Lookup aerial video** `google_maps_lookup_aerial_video` | Look up an aerial view video by address or video ID | | **Maps embed API** `google_maps_maps_embed_api` | Generate an embeddable Google Map URL and HTML iframe code | | **Nearby search** `google_maps_nearby_search` | Searches for places (e.g., restaurants, parks) within a specified circular area, with options | | **Place photo** `google_maps_place_photo` | Retrieves high quality photographic content from the Google Maps Places database | | **Text search** `google_maps_text_search` | Searches for places on Google Maps using a textual query (e.g., "restaurants in London" | | **Render aerial video** `google_maps_render_aerial_video` | Starts rendering an aerial view video for a US postal address | | **Tiles create session** `google_maps_tiles_create_session` | Create a session token required for accessing 2D Tiles and Street View imagery | ## Example prompts **Autocomplete** > Use Google Maps to autocomplete and walk me through the result in plain English. **Compute Route Matrix** > Use Google Maps to compute route matrix and walk me through the result in plain English. **Geocode Address With Query** > Use Google Maps to geocode address with query and walk me through the result in plain English. **Geocode Destinations** > Use Google Maps to geocode destinations and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Maps working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Google Maps app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Google Maps through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Google Maps. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Google Maps actions to the runtime in a format your agent can reliably use. | 19 tools for Google Maps are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Google Maps to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Google Maps in the browser, and the 19 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect Google Maps from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Google Maps tools Google Maps tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Google Maps call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Google Maps returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Google Maps and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Grok Bot Google Maps integration? Yes. ClawLink is the fastest way to connect Grok Bot to Google Maps: link your Google Maps account once in the browser and Grok Bot can call the Google Maps API through 19 ready-made tools — no custom code or token handling. ### How do I connect Google Maps to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect google-maps` to authorize Google Maps. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage. ### How long does it take to connect Google Maps to Grok Bot? About two minutes. Sign in, click Connect next to Google Maps in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Google Maps up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Maps working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Grok Bot Google Super integration](https://claw-link.dev/grokbot/google-super) — Unified access to multiple Google services in one integration - [Grok Bot Google Drive integration](https://claw-link.dev/grokbot/google-drive) — Upload, search, and manage files - [Google Analytics](https://claw-link.dev/grokbot/google-analytics) — Connect Google Analytics properties through hosted Google OAuth