Google Maps MCP (CabLate) — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Dated implementation activity and relevant MCP role justify continued Radar monitoring.

Reviewed Oct 9, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Google Maps place search, routing and geographic analysis

What we know

MCP integration for Google Maps APIs providing geocoding, place and route data for agent workflows; Codex skills are a separate installation route.

Maintenance / activity evidence

GitHub REST repository pushed_at 2026-09-26T20:35:07Z for cablate/mcp-google-map

Tracking evidence observed Oct 9, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read Google Maps/route data Complete write authority is not verified.
Google Maps Platform API key
Sensitive access: Place searches, Location/travel intent

No real-world booking or route execution established
Google Maps API key is billable and location queries may disclose sensitive addresses; do not imply booking or navigation execution.
Google Maps API key, billable map APIs; HTTP transport may expose endpoint if bound beyond localhost.
Unknown vulnerabilities and client-side tool approvals were not exhaustively evaluated.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

469 repository stars · 9k package downloads / 30 days

Stars observed Oct 9, 2026. Downloads observed Oct 9, 2026.

Repository total for cablate/mcp-google-map.

Exact npm package @cablate/mcp-google-map; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.

All limitations / Review context

At the next review, has this exact implementation gained new releases, changed setup/security scope, or become suitable for Shortlist?

No verified blocker to PUBLIC RADAR TRACKING within the bounded first-party evidence reviewed; material permissions and mitigations are explicitly disclosed.

No real-world booking or route execution established
Google Maps API key is billable and location queries may disclose sensitive addresses; do not imply booking or navigation execution.
Google Maps API key, billable map APIs; HTTP transport may expose endpoint if bound beyond localhost.
Read Google Maps/route data
Google Maps Platform API key
Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component.
Sensitive access: Place searches, Location/travel intent
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Unknown vulnerabilities and client-side tool approvals were not exhaustively evaluated.
full exact tool inventory or deployment-specific access configuration
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Requires Maps API key and applicable Google API billing
Geographic queries reveal travel intent
Do not confuse skills install with MCP install
No independent release lifecycle audit; do not claim precise activity date.

Original activity observations

GitHub REST repository pushed_at 2026-09-26T20:35:07Z for cablate/mcp-google-map

Technical identity

github.com/cablate/mcp-google-map

Exact implementation source: https://www.npmjs.com/package/@cablate%2Fmcp-google-map ↗
Reviewed resource type: MCP Server
Repository identity: cablate/mcp-google-map
Package identity: npm:@cablate/mcp-google-map

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 9, 2026 · Latest source observation Oct 9, 2026

GitHub repository ↗
cablate/mcp-google-map
Recorded repository material and project history.
Package registry ↗
@cablate/mcp-google-map
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Use the publisher-documented command or connection method below; complete the prerequisites and client configuration before expecting a usable MCP connection.
Configure / authenticate
Publisher instructions
Set GOOGLE_MAPS_API_KEY in the MCP process environment, then configure the official stdio client JSON: npx -y @cablate/mcp-google-map --stdio. The separate Codex plugin marketplace installs Skills, NOT the MCP server; do not confuse them. Avoid keys on shell command lines.
Advanced configuration · claude desktop json
{ "mcpServers": { "google-maps": { "args": [ "-y", "@cablate/mcp-google-map", "--stdio" ], "command": "npx", "env": { "GOOGLE_MAPS_API_KEY": "YOUR_API_KEY" } } } }
Check connection
MCP100 setup guide
Run npx -y @cablate/mcp-google-map doctor for publisher non-billable local readiness. doctor --live and any real Maps request may incur Google Maps API charges; require explicit user choice before running live diagnostics.
npx -y @cablate/mcp-google-map doctor
Remove / uninstall / revoke
Remove the matching MCP configuration from the client. This does not uninstall the local package or revoke provider credentials. Remove only `google-maps` from this MCP client’s `mcpServers` configuration and restart/reload that client. Other entries must remain intact. In the MCP client settings remove only the `mcpServers.google-maps` entry and restart/reload. This is a concrete client disconnect, separate from uninstalling the local package.

Official Documentation & Sources

What it does

MCP integration for Google Maps APIs providing geocoding, place and route data for agent workflows; Codex skills are a separate installation route.

Capability: Search & Web
Resource type: MCP Server
Best fit: Google Maps place search, routing and geographic analysis

Representative uses

Search places
Geocode addresses
Get routes
Plan trips
Inspect local-search signals

Limitations

Requires Maps API key and applicable Google API billing
Geographic queries reveal travel intent
Do not confuse skills install with MCP install
No real-world booking or route execution established
No independent release lifecycle audit; do not claim precise activity date.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Google Maps Platform API key
Permissions: Read Google Maps/route data
Data handling: Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component.
Cost: unknown
Risk and cautions: No real-world booking or route execution established

Access scope and cautions

Write actions: Not verified
Sensitive access: Place searches Location/travel intent
Risk level: moderate
Security notes: Google Maps API key is billable and location queries may disclose sensitive addresses; do not imply booking or navigation execution. Google Maps API key, billable map APIs; HTTP transport may expose endpoint if bound beyond localhost.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Search places; Geocode addresses; Get routes; Plan trips; Inspect local-search signals.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @cablate/mcp-google-map. Recorded transport: stdio. Recorded environment-variable notes: GOOGLE_MAPS_API_KEY. No configuration values are supplied here. Prerequisites: Compatible MCP client. Client notes: Source docs and package may evolve; install according to confirmed release. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Google Maps Platform API key

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Read Google Maps/route data

What data-handling boundary should I consider?

Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component. Recorded sensitive-access context: Place searches; Location/travel intent.

What limitations and risks should I check before use?

No real-world booking or route execution established. Requires Maps API key and applicable Google API billing. Geographic queries reveal travel intent. Do not confuse skills install with MCP install. No independent release lifecycle audit; do not claim precise activity date. Google Maps API key is billable and location queries may disclose sensitive addresses; do not imply booking or navigation execution. Google Maps API key, billable map APIs; HTTP transport may expose endpoint if bound beyond localhost. Unknown vulnerabilities and client-side tool approvals were not exhaustively evaluated.