SITA Airport Reference API MCP. Query world airport codes, terminals, and metadata.

Your AI client uses this server to connect straight into SITA's global airport reference database. It’s how you pull hard, verified air transport data—the kind of stuff that runs the industry. You don't need to babysit spreadsheets; your agent handles all the querying for you.

When you're building something out, you’ll use three main tools here. They let you map everything from a single gate area across the globe to every airport registered in the system.

If you need to know what airports are even playable in the SITA system, you use list_sita_airports. This tool pulls a complete directory of every global airport they've cataloged. It gives you a master list that includes both the full name and the three-letter IATA code for each location. You start here if your project needs to know where all the action is happening.

You can then take any specific airport code from that list and drill down with get_airport_reference_details. This function fetches the full, deep metadata packet for one single airport. You don't just get a name; you get the timezone data, the GPS coordinates, the city, the country—everything required to map it or validate its record against other systems.

It’s robust data covering operational details and physical location info.

For routing or passenger flow planning, you need an inventory of facilities at that specific airport. You use list_airport_terminals for this. This tool lists all the terminals, concourses, and gate areas tied to a known airport code. It gives you a granular breakdown of the physical infrastructure. You'll pull these details when your logic needs to know which gates are open or what specific terminal building services that particular flight path.

It’s a sequence: First, you check the global list using list_sita_airports. Next, you get the main metadata packet for an airport code with get_airport_reference_details, getting all those coordinates and timezone details. Finally, if your job requires knowing where people physically walk or park, you run list_airport_terminals to map out every gate and concourse connected to that location.

You use these three functions together to build a complete picture of global air travel infrastructure. You don't write complex SQL queries; you just tell your agent the job—like 'give me all terminals at LHR,' or 'show me the coordinates for Tokyo.' The server handles pulling those definitive, official data points back to your client.