Google Maps Travel Planner: Plan journeys, optimize itineraries, and get trip directions with AI-driven, automated trave
Add new capabilities to Claude beyond text generation
Example: Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example: Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example: Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Time estimate: 15-60 minutes depending on server complexity
Prerequisites
Jump
Trusted AI for advisors & financial professionals
Ninout
Design, publish, and analyze forms entirely in chat
EasyPost
Make smarter shipping decisions, instantly
Badger Maps (Standard)
Badger Maps is the #1 field sales platform
Synthflow
Build and manage AI voice agents from chat
Wonder
Create and edit designs with Claude on a canvas where every design is real code.
We evaluated Google Maps (Travel Planner) against two servers with overlapping tools; this profile had the clearer scope statement.
Strong directory entry: Google Maps (Travel Planner) surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We wired Google Maps (Travel Planner) into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Google Maps (Travel Planner) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
I recommend Google Maps (Travel Planner) for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Google Maps (Travel Planner) is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Google Maps (Travel Planner) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Google Maps (Travel Planner) is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
According to our notes, Google Maps (Travel Planner) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Strong directory entry: Google Maps (Travel Planner) surfaces stars and publisher context so we could sanity-check maintenance before adopting.
showing 1-10 of 53
Share your MCP server with the developer community
Select a client to integrate this server.
Claude Desktop configuration
{
"mcpServers": {
"travel-planner": {
"command": "npx",
"args": [
"@gongrzhe/server-travelplanner-mcp"
],
"env": {
"GOOGLE_MAPS_API_KEY": "your_google_maps_api_key"
}
}
}
}Connects to Google Maps API to search for places, get location details, and calculate travel routes for trip planning.
Google Maps (Travel Planner) is a community-built MCP server published by gongrzhe that provides AI assistants with tools and capabilities via the Model Context Protocol. Google Maps Travel Planner: Plan journeys, optimize itineraries, and get trip directions with AI-driven, automated trave It is categorized under productivity.
You can install Google Maps (Travel Planner) in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
A Travel Planner Model Context Protocol (MCP) server implementation for interacting with Google Maps and travel planning services. This server enables LLMs to perform travel-related tasks such as location search, place details lookup, and travel time calculations.
<a href="https://glama.ai/mcp/servers/y3u6yjiiq1"> <img width="380" height="200" src="https://glama.ai/mcp/servers/y3u6yjiiq1/badge" alt="Travel Planner Server MCP server" /> </a>To install Travel Planner for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @GongRzhe/TRAVEL-PLANNER-MCP-Server --client claude
# Using npx (recommended)
npx @gongrzhe/server-travelplanner-mcp
# With environment variable for Google Maps API
GOOGLE_MAPS_API_KEY=your_api_key npx @gongrzhe/server-travelplanner-mcp
Or install globally:
# Install globally
npm install -g @gongrzhe/server-travelplanner-mcp
# Run after global installation
GOOGLE_MAPS_API_KEY=your_api_key @gongrzhe/server-travelplanner-mcp
searchPlaces
query (string): Search query for placeslocation (optional): Latitude and longitude to bias resultsradius (optional): Search radius in metersgetPlaceDetails
placeId (string): Google Place ID to retrieve details forcalculateRoute
origin (string): Starting locationdestination (string): Ending locationmode (optional): Travel mode (driving, walking, bicycling, transit)getTimeZone
location: Latitude and longitude coordinatestimestamp (optional): Timestamp for time zone calculationTo use this server with the Claude Desktop app, add the following configuration to the "mcpServers" section of your claude_desktop_config.json:
{
"mcpServers": {
"travel-planner": {
"command": "npx",
"args": ["@gongrzhe/server-travelplanner-mcp"],
"env": {
"GOOGLE_MAPS_API_KEY": "your_google_maps_api_key"
}
}
}
}
Alternatively, you can use the node command directly if you have the package installed:
{
"mcpServers": {
"travel-planner": {
"command": "node",
"args": ["path/to/dist/index.js"],
"env": {
"GOOGLE_MAPS_API_KEY": "your_google_maps_api_key"
}
}
}
}
npm install
npm run build
GOOGLE_MAPS_API_KEY (required): Your Google Maps API key with the following APIs enabled:
This MCP server is licensed under the MIT License. For more details, please see the LICENSE file in the project repository.
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.