We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

Google Maps Grounding Lite, verified

MCP server by Google · Verified

Search places, check weather and compute routes using Google Maps data, and resolve place names and Maps URLs to Place IDs.

Needs an API key (Needs an API key from the vendor)Streamable HTTP

Connect to Google Maps Grounding Lite

Google Maps Grounding Lite needs an API key. Connect with its own URL and your key:

https://mapstools.googleapis.com/mcp

Send your key in the X-Goog-Api-Key header. mcp.tc never sees or stores keys. Where to get a key

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/google-maps

About

Maps Grounding Lite connects an assistant to Google Maps Platform data. It can search for places and businesses, look up current and forecast weather, compute driving or walking routes, and resolve place names or Google Maps links into canonical Place IDs. All five tools are read-only.

It runs as a hosted streamable HTTP endpoint at mapstools.googleapis.com/mcp, so nothing is installed locally. Google's documentation says to send a Google API key in the X-Goog-Api-Key header; OAuth is also supported.

What you can do

  • Search places, businesses and addresses with a text query
  • Get current conditions, hourly and daily weather forecasts
  • Compute driving or walking routes between two locations
  • Resolve place names and addresses to Place IDs in batches
  • Resolve Google Maps share URLs to Place IDs

Tools 6

  • search_placesRead-only

    Find places, businesses, addresses and points of interest from a text query.

  • lookup_weatherRead-only

    Get current conditions plus hourly and daily weather forecasts for a location.

  • compute_routesRead-only

    Compute a drive or walk route between an origin and a destination.

  • search_along_routeRead-only

    Call this tool when the user wants to find places, businesses, or points of interest along a travel route (e.g., "gas stations on my way to Tahoe", "coffee shops between SF and San Jose").

  • resolve_namesRead-only

    Resolve up to 20 place names or addresses into Google Maps Place IDs.

  • resolve_maps_urlsRead-only

    Resolve up to 20 Google Maps URLs into canonical Place IDs.

Read from the live server on 17 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.

Example prompts

  • Find pet friendly parks in Manhattan, New York

  • What is the weather forecast for Chicago this weekend?

  • How long does it take to walk from the Eiffel Tower to the Louvre?

  • Get the Place ID for this Google Maps link

Set up

Every client connects to mapstools.googleapis.com. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http google-maps https://mapstools.googleapis.com/mcp --header "X-Goog-Api-Key: <YOUR_API_KEY>"
  1. Replace the placeholder with your key before you run it, then check it with /mcp inside Claude Code.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Use the mcp-remote bridge, which keeps the key on this computer (a connector added on claude.ai with the key under Request headers also shows up here). Open Settings → Developer → Edit Config and add:
claude_desktop_config.json
{
  "mcpServers": {
    "google-maps": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mapstools.googleapis.com/mcp",
        "--header",
        "X-Goog-Api-Key: <YOUR_API_KEY>"
      ]
    }
  }
}
  1. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://mapstools.googleapis.com/mcp. Under Request headers, add X-Goog-Api-Key: <YOUR_API_KEY> with your key from Google, then click Add.
  2. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "google-maps": {
      "url": "https://mapstools.googleapis.com/mcp",
      "headers": {
        "X-Goog-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

VS Code

Add it to .vscode/mcp.json. VS Code asks for the key the first time and stores it securely:

.vscode/mcp.json
{
  "servers": {
    "google-maps": {
      "type": "http",
      "url": "https://mapstools.googleapis.com/mcp",
      "headers": {
        "X-Goog-Api-Key": "${input:x-goog-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "x-goog-api-key",
      "description": "X-Goog-Api-Key",
      "password": true
    }
  ]
}

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "google-maps": {
      "serverUrl": "https://mapstools.googleapis.com/mcp",
      "headers": {
        "X-Goog-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add google-maps --url https://mapstools.googleapis.com/mcp

codex mcp add can’t set the X-Goog-Api-Key header, so this step is required: put this entry in ~/.codex/config.toml instead of running the command, or add its env_http_headers line to the entry the command made:

config.toml
[mcp_servers.google-maps]
url = "https://mapstools.googleapis.com/mcp"
env_http_headers = { "X-Goog-Api-Key" = "X_GOOG_API_KEY" }

Codex reads the header values from the environment variables named in env_http_headers.

Gemini CLI

gemini mcp add --transport http --header "X-Goog-Api-Key: <YOUR_API_KEY>" google-maps https://mapstools.googleapis.com/mcp

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

{
  "mcpServers": {
    "google-maps": {
      "type": "http",
      "url": "https://mapstools.googleapis.com/mcp",
      "headers": {
        "X-Goog-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://mapstools.googleapis.com/mcp.

Embed

Show Google Maps Grounding Lite in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Google Maps Grounding Lite on mcp.tc](https://mcp.tc/i/google-maps/badge.svg)](https://mcp.tc/i/google-maps)
HTML
<a href="https://mcp.tc/i/google-maps"><img src="https://mcp.tc/i/google-maps/badge.svg" alt="Google Maps Grounding Lite on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/google-maps.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/google-maps" title="Google Maps Grounding Lite on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/google-maps.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Google Maps Grounding Lite card to your site.

Markdown
Add the mcp.tc card for Google Maps Grounding Lite, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/google-maps.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="google-maps"><a href="https://mcp.tc/i/google-maps">Google Maps Grounding Lite on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Google Maps Grounding Lite on mcp.tc](https://mcp.tc/i/google-maps/badge.svg)](https://mcp.tc/i/google-maps)
```

Reference: https://mcp.tc/embed

Change history

We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 05:33 UTC.

Follow Google Maps Grounding Lite and we’ll email you when something changes.

  1. , Automatic check

    2 tools changed.

    Details, 10 Nov 2026, 23:43 UTC

    Changed 2

    • lookup_weatherinput schema and output schema
    • search_placesdescription

      The text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.

  2. , Automatic check

    3 tools changed.

    Details, 8 Nov 2026, 17:53 UTC

    Changed 3

    • compute_routesdescription and input schema
      Before

      Computes travel routes between an origin and a destination, optionally through intermediate stops. Returns the distance and duration for each route. **Input Requirements (CRITICAL):** 1. **`origin` and `destination` (objects - MANDATORY):** Each must be provided using exactly one of: * **`address`** (string, e.g., `'Eiffel Tower, Paris'`). Named places, landmarks, and businesses are resolved directly, so do NOT call `search_places` first just to geocode a waypoint. Include any city, region, or country the user mentioned. * **`lat_lng`** (object, `{"latitude": number, "longitude": number}`). * **`place_id`** (string, e.g., `'ChIJOwE_Id1w5EAR4Q27FkL6T_0'`), for example from `search_places`. 2. **`intermediate_waypoints` (array of objects - OPTIONAL):** Up to 10 stops to pass through, in order, between the origin and destination. Same format as `origin`. Not supported with `TRANSIT`. Only include stops the user asked for. 3. **`travel_mode` (enum - OPTIONAL):** `DRIVE` (default), `WALK`,…

      After

      Computes travel routes between an origin and a destination, optionally through intermediate stops. Returns the distance and duration for each route. **Input Requirements (CRITICAL):** 1. **`origin` and `destination` (objects - MANDATORY):** Each must be provided using exactly one of: * **`address`** (string, e.g., `'Eiffel Tower, Paris'`). Named places, landmarks, and businesses are resolved directly, so do NOT call `search_places` first just to geocode a waypoint. Include any city, region, or country the user mentioned. * **`lat_lng`** (object, `{"latitude": number, "longitude": number}`). * **`place_id`** (string, e.g., `'ChIJOwE_Id1w5EAR4Q27FkL6T_0'`), for example from `search_places`. 2. **`intermediate_waypoints` (array of objects - OPTIONAL):** Up to 25 stops to pass through, in order, between the origin and destination. Same format as `origin`. Not supported with `TRANSIT`. Only include stops the user asked for; specifying more than 10 intermediate waypoints will incur a higher…

      • Description of intermediateWaypoints
        Before

        Optional. Intermediate stops between the origin and destination to pass through in order. At most 10 intermediate waypoints are supported. Intermediate waypoints are not supported when `travel_mode`…

        After

        Optional. Intermediate stops between the origin and destination to pass through in order. Up to 25 intermediate waypoints are supported. Specifying more than 10 intermediate waypoints will incur high…

    • search_along_routeinput schema
    • search_placesdescription and input schema

      The text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.

      • Description of pageSize
        Before

        Optional. The maximum number of places to return, up to 5. The service may return fewer than this value. The default value is 5. Requesting more than 5 places will trigger the Pro tier and incur high…

        After

        Optional. The maximum number of places to return, up to 10. The service may return fewer than this value. The default value is 5. Requesting more than 5 places will trigger the Pro tier and incur hig…

  3. , Automatic check

    1 tool added and 3 tools changed.

    Details, 6 Nov 2026, 05:44 UTC

    Added 1

    • search_along_routeRead-only

      Call this tool when the user wants to find places, businesses, or points of interest along a travel route (e.g., "gas stations on my way to Tahoe", "coffee shops between SF and San Jose"). Calling this tool incurs higher cost than `search_places`, so use `search_places` instead when searching near a single location rather than along a route. **Input Requirements (CRITICAL):** 1. **`text_query` (string - MANDATORY):** A natural language description of what to search for along the route. * **Examples:** `'ev chargers'`, `'coffee'`, `'vegetarian restaurants'`, `'rest stops'`. 2. **Route specification (MANDATORY - provide exactly ONE of the following):** * **`retrieval_token` (string):** The `retrieval_token` returned by a prior `compute_routes` call for a `DRIVE` route. Prefer this whenever the route was already computed. The token is valid for 10 minutes. * **`route_endpoints` (object):** The route's `origin` and `destination`. Each must be provided using one of `address`, `lat_lng`, or…

    Changed 3

    • compute_routesdescription

      The text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.

    • lookup_weatherdescription, input schema and output schema
      Before

      Retrieves comprehensive weather data including current conditions, hourly, and daily forecasts. **Specific Data Available:** Temperature (Current, Feels Like, Max/Min, Heat Index), Wind (Speed, Gusts, Direction), Celestial Events (Sunrise/Sunset, Moon Phase), Precipitation (Type, Probability, Quantity/QPF), Atmospheric Conditions (UV Index, Humidity, Cloud Cover, Thunderstorm Probability), and Geocoded Location Address. **Location & Location Rules (CRITICAL):** The location for which weather data is requested is specified using the `location` field. This field is a 'oneof' structure, meaning you MUST provide a value for ONLY ONE of the three location sub-fields below to ensure an accurate weather data lookup. 1. Geographic Coordinates (lat_lng) * Use it when you are provided with exact lat/lng coordinates. * Example: {"location": {"lat_lng": {"latitude": 34.0522, "longitude": -118.2437}}} // Los Angeles 2. Place ID (place_id) * An unambiguous string identifier (Google Maps Place ID).…

      After

      Retrieves comprehensive environmental intelligence for a location, including Weather, Air Quality (AQI & pollutants), and Pollen (tree, grass, weed, and plant species allergen levels): current conditions, hourly forecasts/history, and daily forecasts for Weather and Air Quality; Pollen is a daily forecast only (today through +4 days, no hourly or past data). **Available Environmental Domains & Capabilities (`capabilities`: `WEATHER`, `AIR_QUALITY`, `POLLEN` — CRITICAL):** * **Mandatory Explicit Selection:** You **MUST** include at least one of `WEATHER`, `AIR_QUALITY`, or `POLLEN` in `capabilities` on every call. Omitting `capabilities` is **NOT allowed**. * **Broad / Ambiguous Outdoor Queries (Full Ambient Outdoor Suite):** If the user asks a general outdoor, travel, or situational question without restricting to a specific domain (e.g., "What are outdoor conditions like right now for a run?"), **explicitly include all three capabilities** (`capabilities: ["WEATHER", "AIR_QUALITY", "…

      • Description of date
        Before

        Optional. The date of the required weather information. Note: This date is relative to the local timezone of the location specified in the location field. The date must be between 24 hours in the pas…

        After

        Optional. Specifies the date of the requested environmental information, relative to the local timezone of the location specified in the `location` field. Supported date ranges depend on the requeste…

      • Description of hour
        Before

        Optional. The hour of the requested weather information, in 24-hour format (0-23). This value is relative to the local timezone of the location specified in the location field. Hourly forecast beyond…

        After

        Optional. Specifies the hour of the requested environmental information, in 24-hour format (0-23), relative to the local timezone of the location specified in the `location` field. Requires `date` to…

    • search_placesinput schema
      • Description of pageSize
        Before

        Optional. The maximum number of places to return, up to 5. The service may return fewer than this value. The default value is 5.

        After

        Optional. The maximum number of places to return, up to 5. The service may return fewer than this value. The default value is 5. Requesting more than 5 places will trigger the Pro tier and incur high…

  4. , Automatic check

    1 tool changed.

    Details, 29 Oct 2026, 20:45 UTC

    Changed 1

    • lookup_weatheroutput schema
  5. , Automatic check

    2 tools changed.

    Details, 27 Oct 2026, 21:03 UTC

    Changed 2

    • compute_routesinput schema
      • Description of arrivalTime
        Before

        Optional. Indicates that the route should be computed based on arrival time.

        After

        Optional. Indicates that the route should be computed based on arrival time. Only one of this field or departureTime should be set.

      • Description of departureTime
        Before

        Optional. Indicates that the route should be computed based on departure time.

        After

        Optional. Indicates that the route should be computed based on departure time. Only one of this field or arrivalTime should be set.

    • lookup_weatherinput schema and output schema
  6. , Automatic check

    2 tools changed.

    Details, 26 Oct 2026, 23:39 UTC

    Changed 2

    • compute_routesdescription, input schema and output schema
      Before

      Computes a travel route between a specified origin and destination. **Supported Travel Modes:** DRIVE (default), WALK. **Input Requirements (CRITICAL):** Requires both **origin** and **destination**. Each must be provided using one of the following methods, nested within its respective field: * **address:** (string, e.g., 'Eiffel Tower, Paris'). Note: The more granular or specific the input address is, the better the results will be. * **lat_lng:** (object, {"latitude": number, "longitude": number}) * **place_id:** (string, e.g., 'ChIJOwE_Id1w5EAR4Q27FkL6T_0') Note: This id can be obtained from the search_places tool. Any combination of input types is allowed (e.g., origin by address, destination by lat_lng). If either the origin or destination is missing, **you MUST ask the user for clarification** before attempting to call the tool. **Example Tool Call:** {"origin":{"address":"Eiffel Tower"},"destination":{"place_id":"ChIJt_5xIthw5EARoJ71mGq7t74"},"travel_mode":"DRIVE"} * The ground…

      After

      Computes travel routes between an origin and a destination, optionally through intermediate stops. Returns the distance and duration for each route. **Input Requirements (CRITICAL):** 1. **`origin` and `destination` (objects - MANDATORY):** Each must be provided using exactly one of: * **`address`** (string, e.g., `'Eiffel Tower, Paris'`). Named places, landmarks, and businesses are resolved directly, so do NOT call `search_places` first just to geocode a waypoint. Include any city, region, or country the user mentioned. * **`lat_lng`** (object, `{"latitude": number, "longitude": number}`). * **`place_id`** (string, e.g., `'ChIJOwE_Id1w5EAR4Q27FkL6T_0'`), for example from `search_places`. 2. **`intermediate_waypoints` (array of objects - OPTIONAL):** Up to 10 stops to pass through, in order, between the origin and destination. Same format as `origin`. Not supported with `TRANSIT`. Only include stops the user asked for. 3. **`travel_mode` (enum - OPTIONAL):** `DRIVE` (default), `WALK`,…

      • New parameters: arrivalTime computeAlternativeRoutes departureTime includePolyline intermediateWaypoints locationBias routingPreference
    • lookup_weatherinput schema and output schema
      • New parameters: airQualityOptions capabilities languageCode weatherOptions
  7. , Automatic check

    1 tool changed.

    Details, 22 Oct 2026, 22:33 UTC

    Changed 1

    • search_placesoutput schema
  8. , Automatic check

    2 tools changed.

    Details, 7 Oct 2026, 22:32 UTC

    Changed 2

    • resolve_maps_urlsdescription and output schema
      Before

      Resolves a list of Google Maps URLs into canonical Google Maps Place IDs. **When to call this tool (CRITICAL):** * Use this tool when the user provides one or more Google Maps sharing links or URLs (e.g. 'https://maps.app.goo.gl/...', 'https://www.google.com/maps/place/...', or 'https://maps.google.com/...') and you need to extract the underlying canonical Place IDs. * You can specify up to 20 URLs to resolve in a single batch request. **Input Requirements (CRITICAL):** * **`urls` (array of strings - MANDATORY):** The list of Google Maps URLs to resolve. Each URL must be a valid, single-place Google Maps URL. **Error Handling (CRITICAL):** * This is a batch processing tool. A request might return "mixed results" (e.g. some URLs resolve successfully while others fail). * The output list of `entities` is guaranteed to map 1:1 with the input `urls` indices. A failed URL resolution will result in an empty `Entity` message (no fields are set) at its corresponding index in the `entities` li…

      After

      Resolves a list of Google Maps URLs into canonical Google Maps Place IDs. **When to call this tool (CRITICAL):** * Use this tool when the user provides one or more Google Maps sharing links or URLs (e.g. 'https://maps.app.goo.gl/...', 'https://www.google.com/maps/place/...', or 'https://maps.google.com/...') and you need to extract the underlying canonical Place IDs. * You can specify up to 20 URLs to resolve in a single batch request. **Input Requirements (CRITICAL):** * **`urls` (array of strings - MANDATORY):** The list of Google Maps URLs to resolve. Each URL must be a valid, single-place Google Maps URL. **Save to Google Maps:** * The response includes a `save_to_maps_url` field: a single Google Maps link containing all successfully resolved places. * When the user wants to save, share, or open the resolved places as a list in Google Maps (e.g. collecting places shared in a conversation), present this link to the user. Do NOT construct this link yourself. **Error Handling (CRITIC…

    • resolve_namesdescription and output schema

      The text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.

  9. , Automatic check

    Tracking started: 5 tools.

FAQ

Can I paste mcp.tc/i/google-maps into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mapstools.googleapis.com/mcp, so your client talks to Google Maps Grounding Lite directly. Your key goes there too, never to mcp.tc. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Google Maps Grounding Lite need an API key or a sign-in?

Yes. Google Maps Grounding Lite needs an API key, sent as the X-Goog-Api-Key header. Get one from Google and keep it in your client’s config, never in a shared file.

Is Google Maps Grounding Lite a remote or a local server?

Remote. Google hosts it at https://mapstools.googleapis.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can Google Maps Grounding Lite do?

It has 6 tools, including search_places, lookup_weather and compute_routes. You can search places, businesses and addresses with a text query, get current conditions, hourly and daily weather forecasts and compute driving or walking routes between two locations.

Which clients can use it?

Any client that supports remote MCP servers and can send your key: Claude Code, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. On claude.ai and Claude Desktop, add the key as a request header when you create the custom connector. ChatGPT can’t send a key, so it can’t use it.

Does mcp.tc track changes to Google Maps Grounding Lite?

Yes. Google Maps Grounding Lite’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read Google Maps Grounding Lite’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with Google. This page was built from Google Maps Grounding Lite’s public metadata, last checked on 17 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.