Skip to content

cablate/mcp-google-map / skills/google-maps-travel-planning

google-maps-travel-planning

Verified

Build evidence-backed day trips, multi-day itineraries, and efficient stop sequences with Google Maps data through the standalone CLI. Use when the desired output is a practical travel plan, not merely a route or list of places.

Google Maps Travel Planning

Build a time-ordered itinerary whose geography, travel times, opening constraints, and along-route stops have been checked. Use the standalone CLI; no MCP connection is required.

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 expose its value.
  • Read ../_shared/content-attribution.md before presenting reviews, photos, or Google-generated summaries.

Workflow

  1. Establish destination, dates or duration, fixed anchors, mobility constraints, pace, and relevant preferences. Ask only for omissions that materially change the itinerary.
  2. Read references/travel-planning.md before designing the itinerary.
  3. Use maps_search_places to find candidate anchors, then group nearby anchors into one-direction daily arcs.
  4. Use maps_search_along_route for meals and breaks between anchors. Use maps_place_details for hours, ratings, and source metadata.
  5. Validate every day with maps_plan_route or maps_directions. Do not present estimated timing as validated timing.
  6. Check weather and air quality when they affect the plan. Respect regional weather limitations described in the reference.
  7. When useful, produce a numbered static map after the stop order is final.
  8. Present a day-by-day schedule with travel time, visit duration, reservations or opening-hour caveats, and clearly marked fallbacks.

CLI

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

For exact tool parameters, read ../google-maps/references/tools-api.md only for the tools selected by the plan.

Boundaries

  • A request for only A-to-B directions or a simple multi-stop ordering belongs to google-maps.
  • A request to assess business visibility or local search rankings belongs to google-maps-local-seo.
  • Do not infer that a venue is accessible, open, safe, or suitable when the API response does not establish it.
  • Do not silently substitute web estimates for unavailable Google Maps results; identify the alternate source.

References

  • references/travel-planning.md: required methodology, timing budgets, geographic arcs, and anti-patterns.
  • ../google-maps/references/tools-api.md: exact parameters and response shapes for selected tools.
  • ../_shared/setup-and-diagnostics.md: first-run and failure recovery.
  • ../_shared/content-attribution.md: Places presentation requirements.
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 117kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall