Google Maps

Community

cablate

google-maps

Search places, resolve addresses, compare routes, inspect neighborhoods, and retrieve geographic or environmental facts through the standalone @cablate/mcp-google-map CLI. Use for concrete location questions; use the travel-planning or local-seo Skill for those specialized outcomes.

Overview

Publisher	cablate
Repository	`mcp-google-map`
Skill name	`google-maps`
Stars	479
Forks	93
Bundled files	1
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by cablate on GitHub. Read the source before you install it.

Installation

Install the Google Maps AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/cablate/mcp-google-map/tree/main/skills/google-maps
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/cablate/mcp-google-map.git /tmp/mcp-google-map
mkdir -p .claude/skills
cp -r /tmp/mcp-google-map/skills/google-maps .claude/skills/google-maps

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Google Maps in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Google Maps on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Google Maps is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Google Maps

Answer real-world location questions with the package's standalone exec CLI. Do not start or configure an MCP server for this workflow.

Before calling the CLI

On the first call in a session, or after an execution failure, read ../_shared/setup-and-diagnostics.md and run the non-billable local preflight.
The user must supply GOOGLE_MAPS_API_KEY. Never print it or place it in a command unless the user explicitly accepts shell-history and process-list exposure.
Before presenting Places reviews, photos, or AI summaries, read ../_shared/content-attribution.md.

Workflow

Identify the concrete location outcome and missing inputs. Do not request details that can be resolved by geocoding or place search.
Read references/tools-api.md when exact parameters, response fields, or a multi-tool recipe are needed.
Prefer coordinates over ambiguous addresses and place_id over repeated name searches.
Chain only the calls needed for the outcome. Reuse returned identifiers and coordinates.
Treat nonzero exit status or { "success": false } as a failure, not as geographic data.
Summarize the useful result rather than returning raw JSON. Preserve source and attribution metadata where required.

Tool selection

Outcome	Preferred tools
Address or landmark to coordinates	`maps_geocode`
Coordinates to address	`maps_reverse_geocode`
Nearby discovery	`maps_search_nearby`, then `maps_place_details`
Natural-language place search	`maps_search_places`, then `maps_place_details`
Compare candidate places	`maps_compare_places` or search → details → distance matrix
Route or travel-mode comparison	`maps_directions`, `maps_distance_matrix`
Multi-stop route without a broader itinerary	`maps_plan_route`
Things along a route	`maps_search_along_route`
Neighborhood facts	`maps_explore_area` plus targeted nearby searches
Elevation, timezone, weather, or air quality	corresponding environment tool; geocode first when needed
Visual map	`maps_static_map` after locations or a route are known

Invocation

bash
npx -y @cablate/mcp-google-map exec <tool> '<json_params>'

The CLI accepts both MCP-style names such as maps_geocode and short names such as geocode. Each call is stateless and returns JSON on stdout.

Boundaries

For a multi-day itinerary, trip schedule, or travel-day optimization, use google-maps-travel-planning instead.
For Google Business Profile visibility, grid ranking, keyword coverage, or competitor audits, use google-maps-local-seo instead.
maps_weather is unavailable in Japan, China, South Korea, Cuba, Iran, North Korea, and Syria; use a current web source there.
Transit waypoint optimization is unsupported; use optimize: false for transit routes.
Geographic proximity and elevation alone do not establish safety, accessibility, flood risk, or suitability. State those limitations when relevant.

References

references/tools-api.md: read for exact parameters, response shapes, and generic chaining recipes.
../_shared/setup-and-diagnostics.md: read for first-run checks and error classification.
../_shared/content-attribution.md: read before displaying regulated Google Maps content.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/tools-api.md26 KB

Frequently asked questions

What does the Google Maps AI skill do?

Why use Google Maps on TypingMind?

Because you install it once and use it with any model. Google Maps is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Google Maps in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cablate/mcp-google-map/tree/main/skills/google-maps. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Google Maps?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Google Maps?

As many as you like. As long as a model supports skills, you can use Google Maps with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Google Maps AI skill free?

Yes. It is published on GitHub by cablate under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Executing Plans

obra

CommunityPopular

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Context And Decisions

affaan-m

CommunityPopular

Govern stable domain context with a narrowly scoped CONTEXT.md when needed, and route hard-to-reverse decisions to ECC's existing architecture-decision-records skill. Use when domain terms require…

Docs Governance

Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Google Maps

Before calling the CLI

Workflow

Tool selection

Invocation

Boundaries

References

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now