{
  "markdown": "# mcp-google_maps\n\nGoogle Maps MCP Pack — geocoding, places, directions, distance matrix, elevation.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `maps_geocode` | \"Geocode [address] via Google Maps\" / \"Google Maps coordinates of [place]\" / \"lat lng for [address] using Google\" — convert an address to lat/lng + formatted address via Google Maps Platform. Premium-quality geocoding (highest accuracy for US addresses); requires Google Maps API key. Use when Mapbox/MapTiler/OpenStreetMap miss the address. |\n| `maps_reverse_geocode` | \"Reverse geocode [lat,lng] via Google Maps\" / \"what address is at [coords] in Google\" — coordinates → address via Google Maps Platform. Requires Google Maps API key. Use when you need Google's street-address parsing (most accurate for US). |\n| `maps_place_search` | \"Find restaurants / hotels / coffee shops / [businesses] near [location]\" / \"nearby [type] within [radius]\" / \"places to eat in [area]\" — find nearby businesses and points of interest via Google Maps Places. Returns names, addresses, Google ratings, distances. Premium-quality POI data; requires Google Maps API key. Use over Yelp/OSM when you want Google's POI coverage and ratings. |\n| `maps_place_details` | \"Hours / phone / reviews of [business]\" / \"Google business info for [place]\" / \"is [restaurant] open\" — full details for a Google Place: address, phone, hours, website, ratings, user reviews. Requires a place ID from `maps_place_search`. Use after search to drill into one specific business. |\n| `maps_directions` | \"Google Maps directions from A to B\" / \"transit / public-transport directions\" / \"bus / subway / train route\" / \"best way to get from [X] to [Y]\" — turn-by-turn directions via Google Maps. Modes: driving, walking, transit (bus/subway/train), bicycling. Requires Google Maps API key. PREFER over Mapbox/OpenRouteService specifically for public-transit routing — Google has the best transit data. |\n| `maps_distance_matrix` | \"Travel time matrix between [N] origins and [M] destinations\" / \"drive-time grid via Google Maps\" / \"transit times between addresses\" — N×M distance and duration matrix between many points via Google Maps. Modes: driving, walking, bicycling, transit. Use for delivery routing, multi-stop optimization, transit-heavy planning. |\n| `maps_elevation` | \"Elevation at [coords] via Google\" / \"altitude / height above sea level\" — elevation in meters for one or more lat/lng pairs via Google Maps Elevation API. Pipe-separated locations for batch queries. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"google_maps\": {\n      \"url\": \"https://gateway.pipeworx.io/google_maps/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/google_maps/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Google_maps data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 4668,
  "sha": "2e245d6d68e2e03b2b3f07db6a197b1083450c55777a93838999858729825863",
  "repo_slug": "pipeworx-io/mcp-google_maps",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_google_maps_37b36675/readme"
}