Skip to main content
Glama
Travel Planner MCP Server

Travel Planner MCP Server

by GongRzhe

Travel Planner MCP Server (@gongrzhe/server-travelplanner-mcp)

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.

Installation & Usage

Installing via Smithery

To install Travel Planner for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @GongRzhe/TRAVEL-PLANNER-MCP-Server --client claude

Installing Manually

# 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

Related MCP server: Google Maps MCP Server

Components

Tools

  • searchPlaces

    • Search for places using Google Places API

    • Input:

      • query (string): Search query for places

      • location (optional): Latitude and longitude to bias results

      • radius (optional): Search radius in meters

  • getPlaceDetails

    • Get detailed information about a specific place

    • Input:

      • placeId (string): Google Place ID to retrieve details for

  • calculateRoute

    • Calculate route between two locations

    • Input:

      • origin (string): Starting location

      • destination (string): Ending location

      • mode (optional): Travel mode (driving, walking, bicycling, transit)

  • getTimeZone

    • Get timezone information for a location

    • Input:

      • location: Latitude and longitude coordinates

      • timestamp (optional): Timestamp for time zone calculation

Configuration

Usage with Claude Desktop

To 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"
      }
    }
  }
}

Development

Building from Source

  1. Clone the repository

  2. Install dependencies:

    npm install
  3. Build the project:

    npm run build

Environment Variables

  • GOOGLE_MAPS_API_KEY (required): Your Google Maps API key with the following APIs enabled:

    • Places API

    • Directions API

    • Geocoding API

    • Time Zone API

License

This MCP server is licensed under the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

5 tools
create_itineraryC

Creates a personalized travel itinerary based on user preferences

Inputs: destination (required), endDate (required), origin (required), startDate (required), +2 more.

get_accommodationsC

Searches for accommodation options in a specified location

Inputs: checkIn (required), checkOut (required), location (required), budget.

get_transport_optionsB

Retrieves available transportation options between two points

Inputs: date (required), destination (required), origin (required).

optimize_itineraryC

Optimizes an existing itinerary based on specified criteria

Inputs: itineraryId (required), optimizationCriteria (required).

search_attractionsC

Searches for attractions and points of interest in a specified location

Inputs: location (required), categories, radius.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: itinerary creation, accommodation search, transport options retrieval, itinerary optimization, and attraction search. There is no overlap in functionality, making it easy for an agent to select the right tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., create_itinerary, get_accommodations, optimize_itinerary). This uniformity enhances readability and predictability for agents.

    Tool Count5/5

    With 5 tools, the server is well-scoped for travel planning, covering key aspects like itinerary management, accommodations, transport, and attractions. Each tool serves a distinct and necessary function.

    Completeness4/5

    The toolset covers core travel planning operations, but minor gaps exist, such as updating or deleting itineraries and booking accommodations or transport. However, agents can likely work around these with the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers