TRAVEL-PLANNER-MCP-Server

TRAVEL-PLANNER-MCP-Server avatar

by GongRzhe

What is TRAVEL-PLANNER-MCP-Server

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

smithery badge

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

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.

Leave a Comment

Frequently Asked Questions

What is MCP?

MCP (Model Context Protocol) is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications, providing a standardized way to connect AI models to different data sources and tools.

What are MCP Servers?

MCP Servers are lightweight programs that expose specific capabilities through the standardized Model Context Protocol. They act as bridges between LLMs like Claude and various data sources or services, allowing secure access to files, databases, APIs, and other resources.

How do MCP Servers work?

MCP Servers follow a client-server architecture where a host application (like Claude Desktop) connects to multiple servers. Each server provides specific functionality through standardized endpoints and protocols, enabling Claude to access data and perform actions through the standardized protocol.

Are MCP Servers secure?

Yes, MCP Servers are designed with security in mind. They run locally with explicit configuration and permissions, require user approval for actions, and include built-in security features to prevent unauthorized access and ensure data privacy.