Google Maps MCP Server

Name: Google Maps MCP Server
Author: cablate

作者：cablate版本 0.0.69i★ –i在你的电脑上运行

注册名称io.github.cablate/google-map

安装

概览

作者提供的说明（英文原文）

18 Google Maps tools for AI agents — geocode, search, directions, weather, and more.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 搜索与 AI 记忆
你需要填写：GOOGLE_MAPS_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： GOOGLE_MAPS_API_KEY, GOOGLE_MAPS_ENABLED_TOOLS

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "google-map": {
      "command": "npx",
      "args": [
        "-y",
        "@cablate/mcp-google-map"
      ],
      "env": {
        "GOOGLE_MAPS_API_KEY": "your-value",
        "GOOGLE_MAPS_ENABLED_TOOLS": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add google-map --env GOOGLE_MAPS_API_KEY=your-value --env GOOGLE_MAPS_ENABLED_TOOLS=your-value -- npx -y @cablate/mcp-google-map

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "google-map": {
      "command": "npx",
      "args": [
        "-y",
        "@cablate/mcp-google-map"
      ],
      "env": {
        "GOOGLE_MAPS_API_KEY": "your-value",
        "GOOGLE_MAPS_ENABLED_TOOLS": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "google-map": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@cablate/mcp-google-map"
      ],
      "env": {
        "GOOGLE_MAPS_API_KEY": "your-value",
        "GOOGLE_MAPS_ENABLED_TOOLS": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

GOOGLE_MAPS_API_KEY 机密必填 env
Google Maps API key (get one at https://console.cloud.google.com)
GOOGLE_MAPS_ENABLED_TOOLS env
Comma-separated tool names to enable. Omit or * for all 18 tools.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 cablate 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 7220 个服务器的 0%
发布到注册中心的时间比此分类中其他 7220 个服务器的 49% 更新
基础检查结果等于或优于此分类中其他 7220 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Google Maps MCP Server 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：GOOGLE_MAPS_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.0.69）于40天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者：upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT3天前更新

安装

Codebase Memory

作者：DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

在你的电脑上运行★ 48,148MIT20天前更新

安装

Exa

作者：exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

在云端运行★ 5,213MIT44天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Google 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.

English · 繁體中文

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 exec CLI 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-Key HTTP request header
--apikey command-line option
GOOGLE_MAPS_API_KEY environment 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

MIT