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 |
17 tools (14 atomic + 3 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.json and package.json descriptions
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 |
1---2name: mcp-google-map-project3description: 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.4---56# mcp-google-map — Project Knowledge78## Overview910This 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.1112For the **agent skill** (how to USE the tools), see `skills/google-maps/SKILL.md`.1314---1516## Quick Orientation1718| Aspect | Summary |19|--------|---------|20| **What** | MCP server providing Google Maps tools for AI agents |21| **Stack** | TypeScript, Node.js, Express, MCP SDK, Zod |22| **Tools** | 17 tools (14 atomic + 3 composite) |23| **Transports** | stdio, Streamable HTTP, standalone exec CLI |24| **APIs** | Places API (New), Directions, Geocoding, Elevation, Timezone, Weather, Air Quality, Static Maps, Search Along Route |2526---2728## Reference Files2930| File | Content | When to read |31|------|---------|--------------|32| `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. |33| `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 |34| `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 |35| `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 |3637---3839## How to Add a New Tool4041See `references/architecture.md` § "9-File Tool Change Checklist" for the complete procedure. Summary:42431. Create `src/tools/maps/<toolName>.ts` (NAME, DESCRIPTION, SCHEMA, ACTION)442. Register in `src/config.ts`453. Add exec case in `src/cli.ts`464. Add to `tests/smoke.test.ts` (expectedTools + API call test)475. Update `README.md` (count + table + exec list + project structure)486. Update `skills/google-maps/SKILL.md` (Tool Map)497. Update `skills/google-maps/references/tools-api.md` (params + chaining)508. Check `server.json` and `package.json` descriptions5152---5354## When to Update This Skill5556| Trigger | What to update |57|---------|----------------|58| Architecture change | `references/architecture.md` |59| New Google Maps API integrated | `references/google-maps-api-guide.md` |60| New design decision made | `references/decisions.md` (add ADR) |61| New GIS concept relevant to tools | `references/geo-domain-knowledge.md` |
cablate