Travel Planner MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEFAULT_LOCALE | No | Google hl language code, e.g. pt-BR | |
| DEFAULT_MARKET | No | Google gl country code, e.g. BR | |
| SERPAPI_API_KEY | No | SerpApi key for both engines | |
| TRAVEL_MCP_MOCK | No | Set to 1 to use mock data instead of SerpApi | |
| DEFAULT_CURRENCY | No | Default currency, e.g. BRL, USD | |
| SERPAPI_BASE_URL | No | Base URL for SerpApi, defaults to https://serpapi.com/search.json | https://serpapi.com/search.json |
| REQUEST_TIMEOUT_MS | No | Supplier call timeout, default 15000 | 15000 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_hotelsA | Search real hotel/accommodation options from Google Hotels (via SerpApi). Use this for hotel inventory, nightly/total prices, ratings, hotel class, amenities, coordinates, and booking links. Only recommend hotels returned by this tool; do not invent hotels. |
| search_flightsA | Search real flight options from Google Flights (via SerpApi). Use this for flight inventory, prices, carriers, durations, stops, and booking links. Only recommend flights returned by this tool; do not invent flights. |
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 2 tools
Each tool targets a distinct domain (flights vs. hotels) with no overlap, making it clear which to use for each purpose.
Both tools follow a consistent verb_noun pattern (search_flights, search_hotels), providing predictability and clarity.
With only 2 tools, the server feels thin for a 'Travel Planner'—search alone is insufficient for planning beyond information retrieval.
The server only offers search functionality, lacking critical operations like booking, itinerary management, or destination recommendations, which are essential for a full travel planner.