MCP Server for interacting with Google Maps (Places API and Routes API). Written in TypeScript, Node and Hono.dev
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"maps-streamable-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Streamable HTTP MCP server for Google Maps — search places, get details, and plan routes.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in maps
Real-time BART departures, trip planning, fares, stations, and advisories.
A Model Context Protocol (MCP) server providing TomTom's location services, search, routing, and traffic data to AI agents.
MCP server for the VesselAPI — maritime vessel tracking, port events, emissions, and navigation data
Global weather API: forecasts, historical data, marine, ski, astronomy and timezone.
MCP Security Weekly
Get CVE alerts and security updates for Maps Streamable Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Streamable HTTP MCP server for Google Maps — search places, get details, and plan routes.
Repository: github.com/iceener/maps-streamable-mcp-server
Author: overment
This MCP server is designed for location-aware AI agents running on mobile devices like Apple Watch or iPhone. Your client provides the current position, and the AI can:
It also pairs well with other MCP tools — for example, combining with a Tesla MCP to set navigation destinations directly in your car.
This repo works in two ways:
Prerequisites: Bun, Google Cloud project.
Your client needs to be aware of the current time and your current location, as both values will be used for searching and planning.
cd google-maps-mcp
bun install
cp .env.example .env
Edit .env:
PORT=3000
AUTH_ENABLED=true
AUTH_STRATEGY=bearer
# Generate with: openssl rand -hex 32
BEARER_TOKEN=your-random-auth-token
# Your Google Maps API key
API_KEY=your-google-maps-api-key
Run:
bun dev
# MCP: http://127.0.0.1:3000/mcp
wrangler kv:namespace create TOKENS
Update wrangler.toml with your KV namespace ID
Set secrets:
# Auth token for clients (generate it using: openssl rand -hex 32). This makes the connection to your MCP not open to everyone, but only to those who have this API key.
wrangler secret put BEARER_TOKEN
# Your Google Maps API key
wrangler secret put API_KEY
wrangler deploy
Endpoint: https://<worker-name>.<account>.workers.dev/mcp
{
"mcpServers": {
"google-maps": {
"command": "npx",
"args": ["mcp-remote", "http://localhost:3000/mcp", "--transport", "http-only"],
"env": { "NO_PROXY": "127.0.0.1,localhost" }
}
}
}
{
"mcpServers": {
"google-maps": {
"command": "npx",
"args": ["mcp-remote", "https://your-worker.workers.dev/mcp", "--transport", "http-only"]
}
}
}
Add as MCP server with:
https://your-worker.workers.dev/mcpstreamable-httpAuthorization: Bearer <your-BEARER_TOKEN>search_placesFind places by text qu