ita-matrix-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Listen port. | 3000 |
| ITA_MATRIX_API_KEY | No | Pin the upstream key instead of discovering it. | auto |
| ITA_MATRIX_TIMEOUT_MS | No | Upstream timeout. Multi-city searches are slow. | 150000 |
| ITA_MATRIX_SECRET_PATH | No | Mounts MCP at /mcp/<secret> instead of /mcp. The URL then acts as the credential. | |
| ITA_MATRIX_ALLOWED_HOSTS | No | Comma-separated Host allowlist, guarding against DNS rebinding. |
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_flightsA | Search ITA Matrix for itineraries. A trip is a list of legs (slices): • 1 slice = one-way • 2 slices = round-trip (second slice reverses the first) • 3+ = multi-city / open-jaw — legs need not connect Each leg takes its own routing code, so you can pin a carrier, force a connection city, or require a specific number of flights per leg. Expect 20-60s. Returns ranked itineraries and a Search ID for get_itinerary_details. |
| get_itinerary_detailsA | Show per-segment detail for one itinerary from a previous search: operating flight numbers, booking class (RBD), fare basis codes, and aircraft type. Reuses the earlier search session, so it is fast. |
| search_flexible_datesA | Scan a range of departure dates and report the cheapest fare on each, to find when to fly. Runs one search per date, so keep ranges modest (a 14-day scan takes several minutes). For a single date with ±flexibility, use search_flights with flexDays instead. |
| lookup_airportA | Resolve a partial city or airport name to IATA codes. Use this when the user names a place rather than a code, or to find the metro code that covers every airport in a city. |
| routing_language_referenceA | Full syntax for the |
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 5 tools
Each tool has a distinct purpose: search_flights for itinerary search, search_flexible_dates for date-range price scans, get_itinerary_details for segment-level details, lookup_airport for IATA code resolution, and routing_language_reference for syntax documentation. The only overlap is between the two search tools, but their descriptions clearly differentiate them (itinerary search vs. date-range scanning).
All tool names use snake_case and mostly follow a verb_noun pattern (search_flights, get_itinerary_details, lookup_airport). search_flexible_dates adds an adjective but remains consistent. routing_language_reference is a noun phrase rather than verb-led, but it still reads clearly and does not break the overall style.
With 5 tools, the server is well-scoped for ITA Matrix functionality. Each tool covers a necessary aspect: searching, exploring dates, getting details, resolving airports, and providing routing-language guidance. No redundant or extraneous tools.
The tool set covers the core ITA Matrix workflow: search flight itineraries, scan flexible dates, retrieve detailed segment information, look up airport codes, and understand routing language syntax. There are no obvious missing operations for typical fare-searching tasks, and the provided tools form a complete lifecycle for flight exploration.