STDIO-based MCP server for Google Maps Platform APIs
STDIO-based MCP server for Google Maps Platform APIs. The google mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 10 defined tools rather than through you.
A Model Context Protocol (MCP) server that provides comprehensive access to Google Maps Platform APIs. This server enables LLMs to perform geocoding, places search, routing, and other geospatial operations through a standardized interface.
Everything the assistant can do here goes through one of these:
elevation_get — Elevation APItimezone_get — Time Zone APIgeolocation_estimate — Geolocation APIroads_nearest — Roads APICursor — Add to your Cursor MCP settings (~/.cursor/mcp.json or through Command Palette > Open MCP Settings > New MCP Server):Geocoding — The Geocoding tool exposed by this serverPlaces — The Places tool exposed by this serverRouting — The Routing tool exposed by this serverUtilities — The Utilities tool exposed by this serverTesting — The Testing tool exposed by this serverYou will need 4 environment variables: GOOGLE_MAPS_API_KEY, GOOGLE_MAPS_RATE_LIMIT_ENABLED, GOOGLE_MAPS_RATE_LIMIT_WINDOW_MS, GOOGLE_MAPS_RATE_LIMIT_MAX_REQUESTS. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at google-maps-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Google's toolset — elevation_get, timezone_get, geolocation_estimate and 7 more — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| elevation_get | Elevation API |
| timezone_get | Time Zone API |
| geolocation_estimate | Geolocation API |
| roads_nearest | Roads API |
| Cursor | Add to your Cursor MCP settings (~/.cursor/mcp.json or through Command Palette > Open MCP Settings > New MCP Server): |
| Geocoding | The Geocoding tool exposed by this server. |
| Places | The Places tool exposed by this server. |
| Routing | The Routing tool exposed by this server. |
| Utilities | The Utilities tool exposed by this server. |
| Testing | The Testing tool exposed by this server. |
{
"mcpServers": {
"google-maps": {
"command": "npx",
"args": ["-y", "google-maps-mcp-server"],
"env": {
"GOOGLE_MAPS_API_KEY": "your-api-key-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GOOGLE_MAPS_API_KEY | Credential the server authenticates with. | Yes |
| GOOGLE_MAPS_RATE_LIMIT_ENABLED | Configuration value read at startup. | Optional |
| GOOGLE_MAPS_RATE_LIMIT_WINDOW_MS | Configuration value read at startup. | Optional |
| GOOGLE_MAPS_RATE_LIMIT_MAX_REQUESTS | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.