Memungkinkan AI client untuk mencari tempat, melakukan geocoding alamat, mendapatkan rute, merencanakan perjalanan, mengecek cuaca, dan melakukan audit peringkat lokal melalui Google Maps APIs.
Juga dikenal sebagai cablate/mcp-google-map, mcp-google-map, @cablate/mcp-google-map
- Stars
- 498
- Tools
- —
- Unduhan, 30 hari
- 4.556
- Versi terbaru
- 0.0.69
- Commit terakhir
- 22 Okt 2026
- Lisensi
- MIT
Apa itu Google Maps MCP?
Google Maps adalah MCP server. Memungkinkan AI client untuk mencari tempat, melakukan geocoding alamat, mendapatkan rute, merencanakan perjalanan, mengecek cuaca, dan melakukan audit peringkat lokal melalui Google Maps APIs.
Ringkasan dibuat dari README proyek
Tentang Google Maps MCP server
Membangun rencana perjalanan atau melakukan audit visibilitas pencarian lokal adalah hal yang bisa Anda capai menggunakan integrasi kapabilitas Google Maps Platform ini. Server ini menyediakan 18 tool read-only dan tiga specialized skills yang memungkinkan AI agent menjalankan workflow berbasis lokasi yang kompleks, bukan sekadar pencarian satu langkah yang sederhana. Pengguna dapat mengakses fungsi-fungsi ini melalui berbagai metode termasuk stdio untuk client desktop lokal seperti Claude Desktop atau Cursor, CLI standalone untuk otomatisasi, atau setup Streamable HTTP untuk deployment jarak jauh.
Untuk menggunakan server ini, Anda harus menyediakan Google Maps Platform API key melalui environment variables, opsi command-line, atau HTTP request headers. Tergantung pada kebutuhan Anda, Anda mungkin perlu mengaktifkan API spesifik seperti Places API (New), Routes API, atau Geocoding API. Sistem ini mendukung kontrol granular, memungkinkan Anda untuk hanya mendaftarkan tool tertentu seperti maps_geocode atau maps_directions menggunakan pengaturan GOOGLE_MAPS_ENABLED_TOOLS untuk mengelola limit konteks.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Google Maps MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Google Maps MCP di Claude Code
$ claude mcp add --env 'GOOGLE_MAPS_API_KEY=<YOUR_GOOGLE_MAPS_API_KEY>' mcp-google-map -- npx -y @cablate/mcp-google-mapInstal Google Maps MCP di 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>"
}
}
}
}Instal Google Maps MCP di 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>"
}
}
}
}Instal Google Maps MCP di 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>"}}'Instal Google Maps MCP di 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>"
}
}
}
}Instal Google Maps MCP di Codex
$ codex mcp add mcp-google-map --env 'GOOGLE_MAPS_API_KEY=<YOUR_GOOGLE_MAPS_API_KEY>' -- npx -y @cablate/mcp-google-mapInstal Google Maps MCP di 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>"
Instal Google Maps MCP di 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-mapInstal Google Maps MCP di 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>"
}
}
}
}Konfigurasi
GOOGLE_MAPS_API_KEYWajibRahasiaGoogle 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.
| Nama | Deskripsi | Tipe |
|---|---|---|
| GOOGLE_MAPS_API_KEY | Google Maps API key (get one at https://console.cloud.google.com) | WajibRahasia |
| GOOGLE_MAPS_API_KEY | — | |
| GOOGLE_MAPS_ENABLED_TOOLS | — | |
| GOOGLE_MAPS_ENABLED_TOOLS | Comma-separated tool names to enable. Omit or * for all 18 tools. |
Pengecekan otomatis
Berjalan 12 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauLolos
- Lisensi open source (OSI)Lolos
- Ada commit atau release dalam satu tahun terakhirLolos
- Nama package tidak mirip dengan package populerLolos
- Remote endpoint menggunakan HTTPSTidak diperiksa
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Tidak ada instruksi tersembunyi untuk modelLolos
- Tidak ada advisory kritis pada paket atau dependensinyaLolos
README
Lihat di 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
Pertanyaan tentang Google Maps MCP
Bagaimana cara menambahkan Google Maps MCP ke Claude Code?
Jalankan claude mcp add --env 'GOOGLE_MAPS_API_KEY=<YOUR_GOOGLE_MAPS_API_KEY>' mcp-google-map -- npx -y @cablate/mcp-google-map di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Google Maps MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Apa yang bisa dilakukan AI agent dengan Google Maps MCP server?
AI dapat mencari tempat, mendapatkan detail tempat, melakukan geocoding alamat, menghitung rute dan distance matrices, merencanakan rute dengan banyak pemberhentian, serta mengecek cuaca, kualitas udara, elevasi, dan zona waktu. Server ini juga mendukung audit visibilitas pencarian lokal.
Bagaimana cara melakukan autentikasi pada Google Maps MCP server?
Anda perlu menyediakan Google Maps Platform API key, baik melalui environment variable GOOGLE_MAPS_API_KEY, opsi --apikey, atau HTTP header X-Google-Maps-API-Key.
Apakah saya memerlukan MCP untuk menggunakan tool Google Maps ini?
Tidak. Kemampuan yang sama tersedia melalui CLI standalone dengan subcommand singkat seperti geocode, search-places, dan directions, serta melalui plugin Codex atau Claude Code yang memuat Skills tanpa memerlukan MCP server.
Bisakah saya membatasi tool Google Maps mana saja yang diekspos?
Bisa. Atur GOOGLE_MAPS_ENABLED_TOOLS ke daftar allowlist yang dipisahkan dengan koma untuk mengekspos hanya tool yang Anda butuhkan, atau kosongkan atau gunakan * untuk mengakses seluruh katalog.
Apakah Google Maps server bisa berjalan melalui HTTP untuk penggunaan jarak jauh atau bersama?
Ya. Menjalankan dengan --host dan --port akan menyajikan MCP melalui Streamable HTTP di /mcp, dan isolasi API key per-sesi didukung melalui request header.