Google Maps Platform
Ground your AI applications with trusted geospatial data from Google Maps.
Official
The registry verified googleapis.com as the publisher’s domain, and the server runs on it.
- Registry name
com.googleapis.mapstools/mcp- Version
- 1.0.0
- Transports
- Streamable HTTP
- Remote endpoints
https://mapstools.googleapis.com/mcp- First published
- Apr 19, 2026
- Updated
- Apr 19, 2026
Add it to a client
Commands and config follow each client’s own MCP docs. Some servers also need an API key or environment variables; see the server’s documentation.
claude mcp add --transport http google-maps https://mapstools.googleapis.com/mcp Format from Claude Code’s docsCursor
mcp.json {
"mcpServers": {
"google-maps": {
"url": "https://mapstools.googleapis.com/mcp"
}
}
} Format from Cursor’s docsGemini CLI
settings.json {
"mcpServers": {
"google-maps": {
"httpUrl": "https://mapstools.googleapis.com/mcp"
}
}
} Format from Gemini CLI’s docsVS Code
.vscode/mcp.json {
"servers": {
"google-maps": {
"type": "http",
"url": "https://mapstools.googleapis.com/mcp"
}
}
} Format from VS Code’s docsClient compatibility
By transport: whether the client’s docs list a transport this server offers. It doesn’t cover sign-in or other requirements.
- Claude Code Transport supported
- Codex Transport supported
- Cursor Transport supported
- Gemini CLI Transport supported
- VS Code Client docs don’t list transports
- ChatGPT Transport supported
- Claude Client docs don’t list transports
- Cline Transport supported
- Devin Desktop Transport supported
- GitHub Copilot Client docs don’t list transports
- JetBrains AI Assistant Transport supported
- Kiro Transport supported
- OpenCode Client docs don’t list transports
- Zed Client docs don’t list transports
Sources
- Official MCP Registry registry.modelcontextprotocol.io · checked Sep 28, 2026
This data comes from the Official MCP Registry.