mcp-google-map-project
Skill480 starsChanged 48 days agoMITView on GitHub
Project knowledge for developing and maintaining @cablate/mcp-google-map. Architecture, Google Maps API guide, GIS domain knowledge, and design decisions. Read this skill to onboard onto the project or make informed development decisions.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- google-maps-local-seoSkill
- google-mapsSkill
- google-maps-travel-planningSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 48
Create src/tools/maps/<toolName>.ts (NAME, DESCRIPTION, SCHEMA, ACTION)
- Very specific: line 50
Add exec case in src/cli.ts
- Very specific: line 51
Add to tests/smoke.test.ts (expectedTools + API call test)
- Distinctive: line 52
Update README.md (count + table + exec list + project structure)
- Very specific: line 53
Update skills/google-maps/SKILL.md (Tool Map)
- Very specific: line 54
Update skills/google-maps/references/tools-api.md (params + chaining)
- Very specific: line 55
Check server.json and package.json descriptions
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
mcp-google-map — Project Knowledge
Overview
This skill contains everything needed to develop, maintain, and extend the @cablate/mcp-google-map MCP server. Reading these files gives you full context on architecture, API specifics, domain knowledge, and the reasoning behind design decisions.
For the agent skill (how to USE the tools), see skills/google-maps/SKILL.md.
Quick Orientation
| Aspect | Summary |
| What | MCP server providing Google Maps tools for AI agents |
| Stack | TypeScript, Node.js, Express, MCP SDK, Zod |
| Tools | 18 tools (14 atomic + 4 composite) |
| Transports | stdio, Streamable HTTP, standalone exec CLI |
| APIs | Places API (New), Directions, Geocoding, Elevation, Timezone, Weather, Air Quality, Static Maps, Search Along Route |
Reference Files
| File | Content | When to read |
references/architecture.md | System architecture, 3-layer design, transport modes, tool registration flow, 9-file checklist, code map | Start here when onboarding. Also read when adding new tools. |
references/google-maps-api-guide.md | All Google Maps API endpoints used, pricing, coverage limits, rate limits, common gotchas, Places New vs Legacy | When debugging API errors, evaluating new APIs, or checking costs |
references/geo-domain-knowledge.md | GIS fundamentals — coordinates, distance, geocoding, place types, spatial search, map projection, Japan-specific knowledge | When making tool design decisions that involve geographic concepts |
references/decisions.md | 10 Architecture Decision Records (ADR) with context and rationale | When asking "why was X built this way?" or considering changes to existing design |
How to Add a New Tool
See references/architecture.md § "9-File Tool Change Checklist" for the complete procedure. Summary:
- Create
src/tools/maps/<toolName>.ts(NAME, DESCRIPTION, SCHEMA, ACTION) - Register in
src/config.ts - Add exec case in
src/cli.ts - Add to
tests/smoke.test.ts(expectedTools + API call test) - Update
README.md(count + table + exec list + project structure) - Update
skills/google-maps/SKILL.md(Tool Map) - Update
skills/google-maps/references/tools-api.md(params + chaining) - Check
server.jsonandpackage.jsondescriptions
When to Update This Skill
| Trigger | What to update |
| Architecture change | references/architecture.md |
| New Google Maps API integrated | references/google-maps-api-guide.md |
| New design decision made | references/decisions.md (add ADR) |
| New GIS concept relevant to tools | references/geo-domain-knowledge.md |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

