Trvl MCP Server

AI travel agent for flights, hotels, rental cars, ground transport, price alerts, and award travel. That is what the trvl mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

It installs the binary, wires the MCP server, installs the skill, and verifies everything. Under a minute.

• Whole journey, door to door. — It plans the entire trip across modes — home to airport, flight, arrival transfer, hotel, onward train — and prices each leg in its real mode. Most tools stop at one flight, one hotel
• It optimizes, not just lists. — Shift-day pricing, split-airline routing, hidden-city checks, award sweet spots, round-trip fares. It hands back the cheaper option and shows what it saved
• It is honest when a source fails. — Typed statuses and labelled estimates, never an empty result dressed up as "nothing found."

The tools it exposes

The server publishes 14 tools. What each one is for:

• Scope — fenced.** Only flight and hotel search honour --stealth. Other paths never receive it
• Area — Highlights
• Flights — Google Flights + Kiwi + Skiplagged merged; LCC fares, AFKLM award scan, round-trip (both legs)
• Ground — 22 train/bus/ferry providers across Europe, API-first
• Hotels — 6 sources, discovery → verification trust model
• CLI — Standalone tool, 56 commands, table/JSON output
• Profile — Learns home airports, FF status, luggage, preferences from your booking history
• Variable — Enables
• AFKLM_KEY — AF-KLM native round-trip fares (see below)
• AFKL_KLM_COOKIES — AF-KLM Flying Blue award / miles search
• SERPAPI_KEY — Detail-verified hotel provider prices (trvl serpapi)
• TRAVELPAYOUTS_TOKEN — Historical price trends

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: TRVL_STEALTH_ALLOWLIST, TRVL_NO_TELEMETRY, NO_TELEMETRY, DO_NOT_TRACK, AFKLM_KEY, SERPAPI_KEY, TRAVELPAYOUTS_TOKEN, TRANSAVIA_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Trvl's toolset — Scope, Area, Flights and 11 more — is a fair guide to whether it matches your workflow. It is maintained by MikkoParkkola; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Trvl's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Trvl.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.