TRAVEL PLANNER MCP Server

MCP server for travel planning and itinerary management

Local serverstdio

What is the TRAVEL PLANNER MCP server?

Travel planner mcp server connects TRAVEL PLANNER to AI assistants that speak the Model Context Protocol. MCP server for travel planning and itinerary management.

What TRAVEL PLANNER does

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.

Tools it exposes

Once connected, the assistant can call these 6 tools directly:

  • searchPlaces — Search for places using Google Places API
  • Input — - query (string): Search query for places
  • getPlaceDetails — Get detailed information about a specific place
  • calculateRoute — Calculate route between two locations
  • getTimeZone — Get timezone information for a location
  • Tools — The Tools tool exposed by this server

Installing the travel planner mcp server

The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply one environment variable: GOOGLE_MAPS_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. TRAVEL PLANNER sits in that group, and the shape of its toolset — searchPlaces, Input, getPlaceDetails among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by GongRzhe.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the travel planner mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
searchPlacesSearch for places using Google Places API
Input- query (string): Search query for places
getPlaceDetailsGet detailed information about a specific place
calculateRouteCalculate route between two locations
getTimeZoneGet timezone information for a location
ToolsThe Tools tool exposed by this server.

How to install the TRAVEL PLANNER MCP server

{
  "mcpServers": {
    "travel-planner": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "GOOGLE_MAPS_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
GOOGLE_MAPS_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use TRAVEL PLANNER to searchPlaces.
  • Use TRAVEL PLANNER to Input.
  • Use TRAVEL PLANNER to getPlaceDetails.

Frequently asked questions

It connects TRAVEL PLANNER to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (searchPlaces, Input, getPlaceDetails, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with TRAVEL PLANNER directly.