travel-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind address (SSE mode only) | 0.0.0.0 |
| PORT | No | Port (SSE mode only) | 8000 |
| MCP_TRANSPORT | No | Transport mode: stdio (local) or sse (HTTP) | stdio |
| MCP_SERVER_URL | No | URL the Next.js UI uses to reach the MCP server | http://localhost:8000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_flightsA | Search for available flights between two cities. Args: origin: Departure city name or airport code (e.g. "New York" or "JFK") destination: Arrival city name or airport code (e.g. "Tokyo" or "NRT") departure_date: Departure date in YYYY-MM-DD format return_date: Return date for round trips in YYYY-MM-DD format (omit for one-way) passengers: Number of passengers (default: 1) |
| search_hotelsA | Search for available hotels in a destination. Args: destination: City name (e.g. "Tokyo", "Paris", "London") check_in: Check-in date in YYYY-MM-DD format check_out: Check-out date in YYYY-MM-DD format guests: Number of guests (default: 1) max_price: Maximum price per night in USD (optional) |
| get_weatherA | Get day-by-day weather forecast for a destination over a date range. Args: destination: City name (e.g. "Tokyo", "Bali", "Sydney") date_from: Start date in YYYY-MM-DD format date_to: End date in YYYY-MM-DD format |
| search_poiA | Search for points of interest in a destination. Args: destination: City name (e.g. "Tokyo", "Barcelona", "Rome") category: Type of place — restaurants, attractions, activities, nightlife, shopping, or transport limit: Maximum number of results to return (default: 5) |
| plan_tripA | Generate a complete day-by-day travel itinerary combining weather, attractions, dining, and travel options. Args: destination: Travel destination city (e.g. "Tokyo", "Paris") start_date: Trip start date in YYYY-MM-DD format end_date: Trip end date in YYYY-MM-DD format origin: Departure city for flight search (e.g. "New York", "London") total_budget: Total trip budget in USD — enables budget planning and suggested allocation (optional) preferences: Comma-separated interests to tailor the itinerary (e.g. "food, history, beaches") |
| create_trip_budgetA | Create a budget tracker for a trip. Args: trip_id: Unique identifier for the trip (e.g. "tokyo-oct-2024") total_budget: Total budget amount currency: Currency code (default: "USD") |
| add_expenseA | Record an expense against a trip budget. Args: trip_id: The trip identifier used when creating the budget category: Expense category — flights, hotels, food, activities, transport, shopping, or misc amount: Amount spent description: Brief description of the expense (e.g. "ANA flight JFK→NRT") |
| get_budget_summaryA | Get a full budget summary: total spent, remaining balance, and per-category breakdown. Args: trip_id: The trip identifier used when creating the budget |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: budgeting (add_expense, create_trip_budget, get_budget_summary), weather, itinerary planning, flight search, hotel search, and POI search. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_expense, create_trip_budget, search_flights). No mixing of conventions.
8 tools cover the essential travel planning domains (budget, weather, itinerary, flights, hotels, POI) without being excessive or sparse. Well-scoped for a focused travel assistant.
Covers core travel planning workflows, but minor gaps exist: no budget update/delete, no transportation other than flights, and no tool to modify generated itineraries. Still fairly complete.