Reported issues for Google Maps MCP Server
Pod holds 14 of 14 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.
Back to Google Maps MCP Server.
Most discussed
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 · 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 · 2026-04-18 · 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 · 2026-03-11 · closed · external user · 2 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 · 2026-03-02 · closed · external user · 3 comments
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 · 2025-10-16 · closed · external user · 2 comments
error gemini-cli version
Unable to resolve action google-github-actions/run-gemini-cli@v1, unable to find version v1
Read the thread · 2025-09-12 · closed · external user · 3 comments
it closes
hey, i was using this server with
npx -y @cablate/mcp-google-map
but it stopped working. The command just stops
I also installed via npm and run:
mcp-google-map --port 3000 --apikey "your_api_key_here"
and same thing happens
even
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
## 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.
[](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
### 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
### error in terminal and trae
<img width="1055" height="247" alt="Image" src="https://github.com/user-attachments/assets/855e19ee-a246-4205-ada0-840d2f2fb003" />
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
### Glama listing is missing Dockerfile
Your MCP server is currently listed on the [Glama MCP directory](https://glama.ai/mcp/servers/cablate/mcp-google-map), but it is not available for others to use because it does not have a Dockerfile.
It takes only a few minutes to fix this:
1. Go to your server's listing: [cablate/mcp-google-map](https://glama.ai/mcp/servers/cablate/mcp-google-map)
2. Click "Claim" to verify ownership.
3. Once claimed, navigate to the [admin `Dockerfile` page](https://glama.ai/mcp/servers/cablate/mcp-google-ma
[Read the thread](https://github.com/cablate/mcp-google-map/issues/1) · 2025-04-23 · closed · outside contributor · 1 comment
The remaining reports are on [the project's issue tracker](https://github.com/cablate/mcp-google-map/issues).