# Reported issues for Google Maps MCP Server by cablate Pod holds 18 of 19 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects. Back to [Google Maps MCP Server by cablate](/mcp/google-maps-mcp-server-by-cablate). ## Most discussed ### it closes hey, i was using this server with ```bash npx -y @cablate/mcp-google-map ``` but it stopped working. The command just stops I also installed via npm and run: ```bash mcp-google-map --port 3000 --apikey "your_api_key_here" ``` and same thing happens even ````bash mcp-google-map --help ``` shows nothing [Read the thread](https://github.com/cablate/mcp-google-map/issues/9) · 2025-07-16 · closed · external user · 11 comments ### StreamableHttp transport is not supported Currently, only stdio transport for local clients is available. No support for Streamablehttp transport for remote mcp server. [Read the thread](https://github.com/cablate/mcp-google-map/issues/5) · 2025-07-13 · closed · outside contributor · 7 comments ### maps_directions: Transit mode missing bus/route details (transitDetails not in field mask) ## Description When using maps_directions with mode: transit, the response includes the transit leg but only as a generic navigation instruction (e.g. "Bus towards Sean Moore Rd"). It does not return transit metadata such as the bus/route number, scheduled departure/arrival times, stop names, stop count, headsign, or transit agency info. The root cause is that the field mask in src/services/RoutesService.ts does not include routes.legs.steps.transitDetails. The Google Routes API only returns t [Read the thread](https://github.com/cablate/mcp-google-map/issues/78) · 2026-05-08 · closed · external user · 6 comments ### maps_directions transit mode returns "No route found" in Japan ## Bug Report ### What happened I was trying to plan a trip to Ghibli Park in Nagoya using the `maps_directions` tool with `mode: transit`, and kept getting a `No route found` error — even for well-connected routes like Nagoya Station → Ghibli Park. What's odd is that switching to `mode: driving` works perfectly fine for the same origin/destination. And transit directions work without issue in other countries — I tested Paris → Lyon and it returned correct step-by-step train instructions in F [Read the thread](https://github.com/cablate/mcp-google-map/issues/74) · 2026-04-18 · closed · external user · 3 comments ### 特定情境或條件下的分析 ## Problem 蠻好奇AI怎麼選店這件事 像是： 有沒有機會把評論內容做情境分類（例如約會、聚餐、商務） 能不能協助在排旅遊時，根據「動線順路」+「使用情境」、「避開尖峰時段」一起決定 或是能不能篩選特定條件（像停車方便、適合久坐、有沒有素食餐點）變成可被優先考慮的因素 如果這些都能做到的話感覺會有蠻大的市場需求 還是目前主要規劃是協助路線安排的部分（？ by 地圖先生 ## Proposed solution ## Alternatives considered [Read the thread](https://github.com/cablate/mcp-google-map/issues/61) · 2026-03-19 · closed · 3 comments ### Idea: earn affiliate commissions when mcp-google-map recommends local businesses Hey cablate 👋 mcp-google-map is one of the most commercially interesting MCP servers I've seen — when someone asks their AI to 'find a good Italian restaurant nearby' or 'find a hotel in Paris,' the Google Places results are genuine, high-intent purchasing decisions. **Quick idea**: What if local businesses — restaurants, hotels, attractions — could pay to be featured as a sponsored option alongside your organic Google Places results? You'd earn a commission when the user acts on the sponsored [Read the thread](https://github.com/cablate/mcp-google-map/issues/24) · 2026-03-02 · closed · external user · 3 comments ### error gemini-cli version Unable to resolve action `google-github-actions/run-gemini-cli@v1`, unable to find version `v1` [Read the thread](https://github.com/cablate/mcp-google-map/issues/18) · 2025-09-12 · closed · external user · 3 comments ### Server crashes on second session: "Already connected to a transport" ## Bug Description When running in HTTP mode, the server crashes when a second MCP session connects. The first session works fine, but any subsequent `initialize` request causes an unhandled error: ``` Error: Already connected to a transport. Call close() before connecting to a new transport, or use a separate Protocol instance per connection. at Server.connect (protocol.js:217:19) at McpServer.connect (mcp.js:48:34) at cli.js:3:7652 ``` With `restart: unless-stopped` in Docker, t [Read the thread](https://github.com/cablate/mcp-google-map/issues/27) · 2026-03-11 · closed · external user · 2 comments ## Most recent ### You're indexed in the Lulu MCP marketplace Noticed this while indexing MCP servers for the Lulu marketplace — you're one of the top-ranked `dev-tools` servers we've indexed, and the numbers back it up. 18 geospatial tools on top of Google Maps is real breadth. [![Lulu MCPs](https://getlulu.dev/api/mcps/badge/mcp-google-map-server?cta=off)](https://getlulu.dev/mcps/mcp-google-map-server?ref=badge-indexed) Feel free to drop it in your README if useful — no other action needed. [Read the thread](https://github.com/cablate/mcp-google-map/issues/85) · 2026-08-19 · open · external user · 0 comments ### Invalid or missing session ID Tried `npx @cablate/mcp-google-map --port 3000 --apikey "YOUR_API_KEY"` But the mcp server just returns "Invalid or missing session ID" [Read the thread](https://github.com/cablate/mcp-google-map/issues/79) · 2026-05-14 · closed · external user · 1 comment ### support listenning on a given hostname ## Problem Currently, the MCP server seems to be hardcoded to listen on localhost (127.0.0.1), which makes it hard to access remotely. I have tried adding `HOST=0.0.0.0` and it didn't work. Wish adding a feature of `--host`. ## Proposed solution Implement CLI argument support or environment variable. Ideally, it should allow users to specify the host and port like this: ``` npx @cablate/mcp-google-map --host 0.0.0.0 --port 3000 ``` [Read the thread](https://github.com/cablate/mcp-google-map/issues/76) · 2026-04-20 · closed · external user · 1 comment ### Add CI/CD pipeline with GitHub Actions ## Overview There is currently no automated CI pipeline. Adding GitHub Actions will enforce quality checks on every PR and automate npm publishing on release. ## Proposed Work ### CI workflow (`.github/workflows/ci.yml`) — triggered on push and pull_request to `main` 1. **Lint** — run ESLint (once configured) to catch style issues 2. **Type check** — `npx tsc --noEmit` 3. **Build** — `npm run build` and verify `dist/` is produced 4. **Test** — `npm test` (once tests are added, see #69) ### [Read the thread](https://github.com/cablate/mcp-google-map/issues/72) · 2026-03-27 · closed · 1 comment ### Implement request caching and rate limiting ## Overview Every MCP tool call currently makes a live Google Maps API request. Adding a cache layer and rate limiting will reduce latency, lower API costs, and prevent quota exhaustion. ## Proposed Work ### Caching - Introduce an in-memory LRU cache (e.g., `lru-cache`) keyed on the serialized request parameters - Configurable TTL per tool (e.g., place details can be cached longer than nearby search) - Cache bypass via an optional `noCache` parameter or environment variable ### Rate Limiting [Read the thread](https://github.com/cablate/mcp-google-map/issues/71) · 2026-03-27 · closed · 1 comment ### Add JSDoc documentation to all exported symbols ## Overview Exported tool definitions and handler functions currently lack JSDoc comments. Adding documentation improves maintainability and enables IDE tooling. ## Proposed Work - Add JSDoc blocks to all exported constants in `src/maps-tools/mapsTools.ts`: - Document each tool's purpose, input schema fields (`@param`), and return shape (`@returns`) - Add JSDoc to any exported handler functions with `@param`, `@returns`, and `@throws` tags - Add an `@example` block for the most commonly use [Read the thread](https://github.com/cablate/mcp-google-map/issues/70) · 2026-03-27 · closed · 1 comment ### Add unit and integration tests ## Overview The project currently has no automated tests. Adding a test suite will improve reliability and make it safer to accept contributions. ## Proposed Work - Set up a test framework (e.g., Vitest or Jest) and configure it in `package.json` - Write **unit tests** for each MCP tool handler: - `search_nearby` — mock the Google Maps client, assert correct parameter mapping and response shaping - `get_place_details` — mock the Places API call, assert field extraction - Write an **integr [Read the thread](https://github.com/cablate/mcp-google-map/issues/69) · 2026-03-27 · closed · 1 comment ### Error: Failed to search nearby places: You’re calling a legacy API **Description:** When calling ``` socket - search_nearby (MCP) (center: {"value":"yy.0404,xx.70","isCoordinates":true}, keyword: "coffee", radius: 1000) ``` the following error occurs: ``` Error: Failed to search nearby places: You’re calling a legacy API, which is not enabled for your project. To get newer features and more functionality, switch to the Places API (New) or Routes API. Learn more: https://developers.google.com/maps/legacy#LegacyApiNotActivatedMapError (HTTP 403) ``` **Steps t [Read the thread](https://github.com/cablate/mcp-google-map/issues/22) · 2025-10-25 · closed · external user · 1 comment ### initialize request rejected with “No valid session ID provided” Summary: When calling the initialize method over HTTP, the server immediately responds with 400 Bad Request: No valid session ID provided. This makes it impossible to establish a new MCP session, even though the initial request should not require a session header. Environment • Package: @cablate/mcp-google-map • Install method: `npm install -g @cablate/mcp-google-map` • Version: (please fill in, e.g. 0.1.x) • Node.js version: (please fill in) • OS: macOS • Start command: `mcp-google-map [Read the thread](https://github.com/cablate/mcp-google-map/issues/21) · 2025-10-16 · closed · external user · 2 comments ### error in terminal and trae Image when I run mcp-google-map in terminal, it stopped at listening on port 3000. when I add MCP in trae , it shows the error below. [INFO] 🗺️ Google Maps MCP Server [INFO] A Model Context Protocol server for Google Maps services [INFO] [INFO] 🚀 Starting Google Maps MCP Server... [INFO] 📍 Available tools: search_nearby, get_place_details, maps_geocode, maps_reverse [Read the thread](https://github.com/cablate/mcp-google-map/issues/15) · 2025-08-10 · closed · external user · 1 comment The remaining reports are on [the project's issue tracker](https://github.com/cablate/mcp-google-map/issues).