Permet à un client IA de rechercher des lieux, de géocoder des adresses, d'obtenir des itinéraires, de planifier des trajets, de consulter la météo et d'auditer le référencement local via les API Google Maps.
Aussi connu sous cablate/mcp-google-map, mcp-google-map, @cablate/mcp-google-map
- Étoiles
- 498
- Outils
- —
- Téléchargements, 30 jours
- 4 556
- Dernière version
- 0.0.69
- Dernier commit
- 22 oct. 2026
- Licence
- MIT
Qu'est-ce que Google Maps MCP ?
Google Maps est un serveur MCP. Permet à un client IA de rechercher des lieux, de géocoder des adresses, d'obtenir des itinéraires, de planifier des trajets, de consulter la météo et d'auditer le référencement local via les API Google Maps.
Résumé généré à partir du README du projet
À propos du MCP server Google Maps
La création d'itinéraires de voyage ou l'audit de la visibilité dans les recherches locales sont des tâches que les développeurs peuvent accomplir grâce à cette intégration des capacités de Google Maps Platform. Le serveur propose 18 outils en lecture seule et trois skills spécialisées qui permettent aux agents IA d'exécuter des workflows complexes basés sur la localisation plutôt que de simples recherches en une étape. Les utilisateurs peuvent accéder à ces fonctions via différentes méthodes, notamment stdio pour les clients de bureau locaux comme Claude Desktop ou Cursor, un CLI autonome pour l'automatisation, ou une configuration Streamable HTTP pour les déploiements à distance.
Pour utiliser le serveur, vous devez fournir une clé API Google Maps Platform via des variables d'environnement, des options en ligne de commande ou des en-têtes de requête HTTP. Selon vos besoins, vous devrez peut-être activer des API spécifiques telles que Places API (New), Routes API ou Geocoding API. Le système offre un contrôle granulaire, vous permettant de n'enregistrer que des outils spécifiques comme maps_geocode ou maps_directions en utilisant le paramètre GOOGLE_MAPS_ENABLED_TOOLS afin de gérer les limites de contexte.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer Google Maps MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller Google Maps MCP dans Claude Code
$ claude mcp add --env 'GOOGLE_MAPS_API_KEY=<YOUR_GOOGLE_MAPS_API_KEY>' mcp-google-map -- npx -y @cablate/mcp-google-mapInstaller Google Maps MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-google-map": {
"command": "npx",
"args": [
"-y",
"@cablate/mcp-google-map"
],
"env": {
"GOOGLE_MAPS_API_KEY": "<YOUR_GOOGLE_MAPS_API_KEY>"
}
}
}
}Installer Google Maps MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"mcp-google-map": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cablate/mcp-google-map"
],
"env": {
"GOOGLE_MAPS_API_KEY": "<YOUR_GOOGLE_MAPS_API_KEY>"
}
}
}
}Installer Google Maps MCP dans VS Code CLI
$ code --add-mcp '{"name":"mcp-google-map","type":"stdio","command":"npx","args":["-y","@cablate/mcp-google-map"],"env":{"GOOGLE_MAPS_API_KEY":"<YOUR_GOOGLE_MAPS_API_KEY>"}}'Installer Google Maps MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-google-map": {
"command": "npx",
"args": [
"-y",
"@cablate/mcp-google-map"
],
"env": {
"GOOGLE_MAPS_API_KEY": "<YOUR_GOOGLE_MAPS_API_KEY>"
}
}
}
}Installer Google Maps MCP dans Codex
$ codex mcp add mcp-google-map --env 'GOOGLE_MAPS_API_KEY=<YOUR_GOOGLE_MAPS_API_KEY>' -- npx -y @cablate/mcp-google-mapInstaller Google Maps MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-google-map] command = "npx" args = ["-y", "@cablate/mcp-google-map"] [mcp_servers.mcp-google-map.env] GOOGLE_MAPS_API_KEY = "<YOUR_GOOGLE_MAPS_API_KEY>"
Installer Google Maps MCP dans Gemini CLI
$ gemini mcp add -s user -e 'GOOGLE_MAPS_API_KEY=<YOUR_GOOGLE_MAPS_API_KEY>' mcp-google-map npx -- -y @cablate/mcp-google-mapInstaller Google Maps MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-google-map": {
"command": "npx",
"args": [
"-y",
"@cablate/mcp-google-map"
],
"env": {
"GOOGLE_MAPS_API_KEY": "<YOUR_GOOGLE_MAPS_API_KEY>"
}
}
}
}Configuration
GOOGLE_MAPS_API_KEYRequisSecretGoogle Maps API key (get one at https://console.cloud.google.com)
GOOGLE_MAPS_API_KEYGOOGLE_MAPS_ENABLED_TOOLSGOOGLE_MAPS_ENABLED_TOOLSComma-separated tool names to enable. Omit or * for all 18 tools.
| Nom | Description | Type |
|---|---|---|
| GOOGLE_MAPS_API_KEY | Google Maps API key (get one at https://console.cloud.google.com) | RequisSecret |
| GOOGLE_MAPS_API_KEY | — | |
| GOOGLE_MAPS_ENABLED_TOOLS | — | |
| GOOGLE_MAPS_ENABLED_TOOLS | Comma-separated tool names to enable. Omit or * for all 18 tools. |
Vérifications automatisées
Exécuté le 12 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications
- Dépôt source lié et accessibleRéussi
- Licence open source (OSI)Réussi
- Commit ou version publiée au cours de l'année écouléeRéussi
- Nom du package non proche d'un package populaireRéussi
- L'endpoint distant utilise HTTPSNon vérifié
- Les outils destructifs sont étiquetésNon vérifié
- Aucune instruction cachée destinée au modèleRéussi
- Aucun avis critique dans le package ou ses dépendancesRéussi
README
Voir sur GitHubGoogle Maps for AI agents
Stop rebuilding place search, routing, and location workflows for every AI app.
@cablate/mcp-google-map turns Google Maps Platform into 18 read-only agent tools and three focused Skills. An agent can find real places, verify routes, compare options, build practical itineraries, or audit local search visibility—through MCP or a standalone CLI.
You choose the integration model: Codex or Claude Code Plugin when you want Skills without MCP setup, stdio for desktop MCP clients, or Streamable HTTP for shared and remote deployments.
Why use it?
Giving an agent a raw Maps API is only the beginning. Useful answers often require several dependent calls: resolve a place, preserve its identity, search around it, check opening details, calculate travel time, and explain what was actually verified. This project packages that work into one consistent interface.
- Move from lookup to outcome. Atomic tools handle geocoding, place details, directions, weather, air quality, and maps. Composite tools explore areas, compare candidates, optimize stops, and measure local rankings.
- Use the same capabilities with or without MCP. The standalone
execCLI works with Agent Skills and automation; the MCP server exposes the same 18 tools over stdio or HTTP. - Give agents workflow guidance, not just function names. Three Skills cover general map research, evidence-backed travel planning, and local SEO. Codex loads their full instructions only when a request matches.
- Keep deployment and credentials under your control. Run locally or self-host. API keys remain in your environment or request headers, with per-session isolation for HTTP deployments.
- Start narrow and grow later. Register only the tools you need with
GOOGLE_MAPS_ENABLED_TOOLS, or use the full catalog.
What can an agent do?
| Outcome | How the project helps |
|---|---|
| Find and evaluate real places | Natural-language and nearby search, place details, ratings, hours, reviews, and distance comparison |
| Build a trip that works geographically | Candidate discovery, along-route stops, travel-time checks, multi-stop optimization, weather, and static maps |
| Research a neighborhood | Multi-category exploration plus targeted distance, elevation, timezone, weather, and air-quality checks |
| Plan field work or deliveries | Route matrices and optimized stop ordering for up to 25 stops |
| Audit local search visibility | Geographic grid ranking, competitor discovery, ARP, ATRP, and SoLV metrics |
| Enrich location data | Single or batch geocoding, reverse geocoding, and structured JSON output |
These are data and planning tools, not guarantees of safety, accessibility, opening status, or ranking outcomes. Applications displaying Places reviews, photos, or AI summaries must follow the content attribution and storage guidance.
Choose your integration
| Use | Best for | What runs |
|---|---|---|
| Codex Plugin | Asking Codex map, travel, or local SEO questions without MCP configuration | A matching Skill loads on demand and calls the standalone CLI |
| Claude Code Plugin | Installing the same three Skills from a Claude marketplace | Skills are namespaced under mcp-google-map and call the standalone CLI |
| Standalone CLI | Scripts, automation, and other Skill-compatible agents | One stateless command returns JSON |
| MCP stdio | Claude Desktop, Cursor, VS Code, and other local MCP clients | The client starts a local MCP process |
| Streamable HTTP | Multi-session, containerized, LAN, or remote access | A self-hosted server exposes /mcp |
All options require Node.js 22+ and a Google Maps Platform API key. Live calls may be billable. Enable the APIs needed by your selected tools; common place and route workflows require Places API (New), Routes API, and often Geocoding API.
Start with Codex—no MCP required
codex plugin marketplace add cablate/mcp-google-map --ref main
codex plugin add mcp-google-map@cablate
Set GOOGLE_MAPS_API_KEY in the environment where Codex runs, then start a new conversation. Verify the local setup without making a Google API request:
npx -y @cablate/mcp-google-map doctor
Success means the node, package, and api-key checks pass and live-api is skipped. Use doctor --live only when you intend to send potentially billable checks to Geocoding, Places, and Routes.
Try asking:
Plan a practical two-day Kyoto itinerary. Group nearby places, check travel times, and explain any opening-hour assumptions.
Codex selects google-maps for general location research, google-maps-travel-planning for itineraries, or google-maps-local-seo for business visibility analysis. The plugin does not register or start an MCP server. See the no-MCP walkthrough for a reproducible example.
Install in Claude Code—no MCP required
claude plugin marketplace add cablate/mcp-google-map
claude plugin install mcp-google-map@cablate-maps
Start a new Claude Code session, set GOOGLE_MAPS_API_KEY in its environment, and run the same doctor check shown above. Claude exposes the installed Skills with the plugin namespace, for example /mcp-google-map:google-maps-travel-planning.
Each GitHub release also includes a versioned mcp-google-map-claude-plugin-v*.zip and SHA-256 checksum for direct distribution. The release workflow builds this archive from the same skills/ source and validates it with Claude Code's official strict validator before publishing.
Use the standalone CLI
Every MCP tool also has a short CLI name:
npx -y @cablate/mcp-google-map exec geocode '{"address":"Tokyo Tower"}'
npx -y @cablate/mcp-google-map exec search-places '{"query":"quiet cafes in Kyoto"}'
npx -y @cablate/mcp-google-map exec directions '{"origin":"Tokyo Station","destination":"Tokyo Skytree","mode":"transit"}'
Each call is stateless. Successful calls return { "success": true, "data": ... } on stdout; failures exit nonzero and write structured JSON to stderr.
For bulk address enrichment:
npx @cablate/mcp-google-map batch-geocode -i addresses.txt -o results.json
cat addresses.txt | npx @cablate/mcp-google-map batch-geocode -i -
Connect an MCP client
stdio
{
"mcpServers": {
"google-maps": {
"command": "npx",
"args": ["-y", "@cablate/mcp-google-map", "--stdio"],
"env": { "GOOGLE_MAPS_API_KEY": "YOUR_API_KEY" }
}
}
}
To reduce tool-list context, add a comma-separated allowlist such as "GOOGLE_MAPS_ENABLED_TOOLS": "maps_geocode,maps_directions,maps_search_places". Omit it or use * to expose all tools.
Streamable HTTP
npx @cablate/mcp-google-map --host 127.0.0.1 --port 3000 --apikey "YOUR_API_KEY"
{
"mcpServers": {
"google-maps": {
"type": "http",
"url": "http://127.0.0.1:3000/mcp"
}
}
}
Bind to 0.0.0.0 only when the server must accept external connections. For multi-tenant deployments, prefer the X-Google-Maps-API-Key request header so keys remain isolated by session.
Tool catalog
| Group | Tools |
|---|---|
| Places and discovery | maps_search_places, maps_search_nearby, maps_place_details, maps_explore_area, maps_compare_places, maps_search_along_route |
| Location and routing | maps_geocode, maps_reverse_geocode, maps_directions, maps_distance_matrix, maps_plan_route, maps_batch_geocode |
| Context and visualization | maps_elevation, maps_timezone, maps_weather, maps_air_quality, maps_static_map |
| Local SEO | maps_local_rank_tracker |
All 18 tools declare readOnlyHint: true and destructiveHint: false. Exact parameters, response shapes, and workflow recipes live in the tool reference.
API key and Google Cloud setup
The key must belong to a Google Cloud project with billing enabled and restrictions compatible with the runtime. The setup and diagnostics guide maps each capability to its required API and explains common failures.
Credential priority is:
X-Google-Maps-API-KeyHTTP request header--apikeycommand-line optionGOOGLE_MAPS_API_KEYenvironment variable
Prefer environment variables or request headers. Command-line secrets can appear in shell history and process listings.
Trust and limits
- Place and route facts come from the Google Maps Platform APIs enabled for your project; weather availability has regional limitations.
- A successful API response does not prove accessibility, safety, legal suitability, or real-time availability.
- The package preserves source and disclosure metadata where returned, but your interface remains responsible for compliant attribution and storage.
- HTTP mode supports per-session API-key isolation and DNS rebinding protection.
- This project is MIT licensed and self-hostable. See SECURITY.md for vulnerability reporting and Security Assessment Clarifications for the review checklist.
Development
git clone https://github.com/cablate/mcp-google-map.git
cd mcp-google-map
npm ci
npm run build
npm run test:unit
npm test
Live E2E calls require GOOGLE_MAPS_API_KEY and may be billable: npm run test:e2e.
Contributions are welcome. Read CONTRIBUTING.md before opening a pull request. Release history is in CHANGELOG.md.
Acknowledgements
Thanks to @junyinnnn for helping add Streamable HTTP support.
License
Questions sur Google Maps MCP
Comment ajouter Google Maps MCP à Claude Code ?
Exécutez claude mcp add --env 'GOOGLE_MAPS_API_KEY=<YOUR_GOOGLE_MAPS_API_KEY>' mcp-google-map -- npx -y @cablate/mcp-google-map dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter Google Maps MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Que peut faire un agent IA avec le MCP server Google Maps ?
Il peut rechercher des lieux, obtenir des détails sur un établissement, géocoder des adresses, calculer des itinéraires et des matrices de distance, planifier des trajets avec plusieurs étapes, et consulter la météo, la qualité de l'air, l'altitude et le fuseau horaire. Il permet également d'auditer la visibilité dans les recherches locales.
Comment authentifier le MCP server Google Maps ?
Vous devez fournir une clé API Google Maps Platform, soit via la variable d'environnement GOOGLE_MAPS_API_KEY, soit via l'option --apikey, soit via l'en-tête HTTP X-Google-Maps-API-Key.
Ai-je besoin de MCP pour utiliser ces outils Google Maps ?
Non. Les mêmes fonctionnalités sont disponibles via un CLI autonome avec des sous-commandes courtes telles que geocode, search-places et directions, ainsi que via des plugins Codex ou Claude Code qui chargent des Skills sans passer par un MCP server.
Puis-je limiter les outils Google Maps exposés ?
Oui. Définissez GOOGLE_MAPS_ENABLED_TOOLS avec une liste blanche séparée par des virgules pour n'exposer que les outils dont vous avez besoin, ou laissez vide ou utilisez * pour accéder à l'ensemble du catalogue.
Le serveur Google Maps peut-il fonctionner via HTTP pour une utilisation à distance ou partagée ?
Oui. En l'exécutant avec --host et --port, le serveur sert le MCP via Streamable HTTP sur /mcp, et l'isolation des clés API par session est prise en charge via l'en-tête de requête.