travel-mcp
Searches Google Flights via SerpAPI for one-way, round-trip, and multi-city itineraries, with filters for stops, cabin class, times, price, airlines, and carry-on bags; also retrieves return or next-leg flights and booking options for an itinerary.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@travel-mcp Find one-way flights from Brussels to Rome on June 12, direct, under €150"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
travel-mcp
Formerly flights-mcp.
An MCP server that searches Google Flights through SerpAPI, locally over stdio or, for ChatGPT, over HTTP. It follows the idea of ravinahp/flights-mcp but shares no code with it. It uses SerpAPI instead of Duffel, so low-cost carriers such as Ryanair appear as they do on Google Flights. It only searches; it cannot book.
Tools
Tool | What it does |
| One-way or round-trip search. Several airports per side, e.g. |
| Two or more legs; returns options for the first leg. |
| With an offer's |
| With an offer's |
Every tool call is one SerpAPI search and counts against the monthly quota.
SerpAPI needs the original search parameters with a token, so each token the
server returns carries them: base64url(zlib(JSON)), a dot, and SerpAPI's own
token. Tokens therefore keep working after a restart of the server. When a token
comes back, the server accepts only the parameters its own search tools set, and
rejects anything else without calling SerpAPI.
Defaults: prices in EUR, Google Flights for Belgium (gl=be), English labels
(hl=en).
Related MCP server: flight-search-mcp-server
Setup
Store the SerpAPI key in the login Keychain. security prompts for it, so it
stays out of the shell history:
security add-generic-password -U -a "$USER" -s serpapi-api-key -wDo not add -T "": the server reads the key through /usr/bin/security, and a
confirmation dialog on every search would block it.
Install the dependencies and register the server in Claude Code for all projects:
cd ~/Repos/travel-mcp
uv sync
claude mcp add --scope user travel -- ~/.local/bin/uv --directory ~/Repos/travel-mcp run travel-mcpRestart Claude Code; the tools appear as mcp__travel__*.
HTTP for ChatGPT
travel-mcp-http serves the same tools over stateless streamable HTTP on port
8000, only at /<TRAVEL_MCP_PATH>/mcp and only for the Host header
TRAVEL_MCP_HOST. Every other path returns 404, and another host returns 421.
ChatGPT offers no static token or API key, so the path is the secret: at least
32 URL-safe characters. The server writes no access log, because that would log
the path. Without both variables, or with a path that is too short, it refuses to
start. Hosting on Azure is described in docs/azure-plan.md.
Deploying to Azure
The Dockerfile builds travel-mcp-http for linux/amd64, as a non-root user.
deploy_azure.sh builds it on the Mac from main's HEAD and pushes it to the
registry of pluk-de-dag, because ACR Tasks do not exist in Belgium Central. It
then rolls it out to app-travel-mcp, using Steven's own az login:
./deploy_azure.sh
./deploy_azure.sh --build-only
./deploy_azure.sh 1a2b3c4The first command builds and rolls out. The second only builds and pushes: that is the first image, before Terraform creates the app. The third rolls back to an image already in the registry.
After a rollout the script checks that /mcp returns 404 and that the secret
path answers initialize with 200. It reads the path from the Key Vault and
passes it to curl on stdin, so the path stays out of the process list.
How the key is handled
On the Mac, the server reads the key from the Keychain at each search, in its own process. There it is never put in an environment variable, a file or a tool result.
In a container, where there is no Keychain, the server reads
SERPAPI_API_KEYinstead. The container platform fills it from a secret store (docs/azure-plan.md). When the variable is set it takes precedence, and an empty value is an error rather than a silent fallback to the Keychain.Errors the server expects, such as a wrong date, an invalid token or a SerpAPI error, reach the model with their message. Any other failure shows only "Error executing tool ".
SerpAPI takes
api_keyas a URL parameter. The server runs its loggers at WARNING, because httpx logs every request URL at INFO and MCP clients keep server stderr in their logs. A test checks this.Error messages carry SerpAPI's error text or the HTTP status, never the URL.
Development
uv sync --extra test
uv run pytestThe tests use httpx.MockTransport and never call SerpAPI.
Checked against one live round trip (CRL–BCN on Ryanair, 2026-11-20); the SerpAPI documentation does not describe these points:
Round-trip prices in the outbound list are totals for the whole trip: the outbound offer, its return flight and the booking option all showed EUR 59.
A booking option bookable as one ticket comes as
togetherwithbook_with,airline(true when booked with the airline itself),marketed_as(flight numbers),priceandbaggage_prices(text such as1 carry-on bag: 25-72). Separate tickets (departingandreturning) have not been seen yet.google_flights_urlwas present in all three responses, but one trip does not prove that it is always there; the tools returnnullwhen it is missing.
Available Tools
4 toolsget_booking_optionsBRead-only
List where, and at what price, an offer's booking_token itinerary can be booked.
Inputs: booking_token (required). Returns: Booking options as SerpAPI returns them, minus logos and form posts.
get_next_flightsARead-only
List return flights, or the next multi-city leg, for an offer's departure_token.
Inputs: departure_token (required), max_results. Returns: Normalized flight options, best first, then the others.
search_flightsARead-only
Search one-way or round-trip flights on Google Flights.
origin and destination are IATA codes; separate several with commas, e.g. "BRU,CRL". With return_date the result lists outbound flights and get_next_flights(departure_token) lists the return flights. outbound_times and return_times are hour ranges, "6,12" for departure or "6,12,10,18" for departure and arrival. max_stops 0 is nonstop only; bags counts carry-on bags. Airline filters take 2-letter IATA codes or STAR_ALLIANCE, SKYTEAM, ONEWORLD. deep_search is slower but closer to the browser.
Inputs: origin (required), destination (required), departure_date (required), bags, +14 more. Returns: Normalized flight options, best first, then the others.
search_multi_cityARead-only
Search a multi-city trip of two or more legs.
Each leg has origin and destination (IATA codes), date (YYYY-MM-DD) and optional times (hour ranges as in search_flights). The result lists the first leg; get_next_flights(departure_token) lists the next one.
Inputs: legs (required), adults, children, currency, +3 more. Returns: Normalized flight options, best first, then the others.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a distinct role: single/round-trip flight search, multi-city search, continuation of an existing search via token, and booking option retrieval. The boundary between search_flights and search_multi_city is clear from the trip type, and the token-based tools are explicitly scoped.
All tools use consistent snake_case verb_noun naming: search_flights, search_multi_city, get_next_flights, get_booking_options. The pattern is predictable and easy for an agent to follow.
Four tools are well-scoped for a focused flight-search server. Each tool earns its place in the search and booking-option workflow, with no redundant or filler tools.
The surface covers core flight search workflows: one-way/round-trip, multi-city, continuation, and booking options. Minor gaps exist around ancillary needs like airport lookup or explicit offer details, but core workflows are covered without dead ends.
Maintenance
Related MCP Connectors
Google Flights for any route and date: price, airlines, flight numbers, times, stops, layovers, aircraft, legroom and CO2. One way or round trip, any cabin and currency. Runs on Apify, $0.20 per 1,000 flights.
Google Flights fares, airlines, stops and durations for any route. Paid, on Apify's hosted MCP.
Google Flights prices for any route and date: round trips, cabins, stops, airlines, cheapest dates.
Live Google Flights fares for AI agents: prices, airlines, stops, times, CO2 and price history.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables flight search and fare calendar exploration by interacting with Google Flights' API, supporting detailed filters for origin, destination, dates, cabin class, airlines, and more.5,091 PyPI3,504MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to search for real-time flights between airports using the SearchAPI.io Google Flights API, returning prices, schedules, airlines, and carbon emissions.-
- AlicenseAqualityDmaintenanceSearch flights using Google Flights data via SerpAPI, covering all airlines including low-cost carriers like Ryanair and easyJet.2MIT
- AlicenseAqualityBmaintenanceEnables searching and analyzing Google Flights data including prices, emissions, cabin classes, layovers, and price tracking, all without an API key.12205 npm5ISC