Vinkius
SITA Airport Reference API

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

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

SITA Airport Reference API MCP on Cursor AI Code EditorSITA Airport Reference API MCP on Claude Desktop AppSITA Airport Reference API MCP on OpenAI Agents SDKSITA Airport Reference API MCP on Visual Studio CodeSITA Airport Reference API MCP on GitHub Copilot AI AgentSITA Airport Reference API MCP on Google Gemini AISITA Airport Reference API MCP on Lovable AI DevelopmentSITA Airport Reference API MCP on Mistral AI AgentsSITA Airport Reference API MCP on Amazon AWS Bedrock

Connect to your AI in seconds.

SITA Airport Reference API provides access to global airport infrastructure data through your AI agent. Use it to query specific IATA codes, list all active terminals and gates at an airport, or pull a complete directory of worldwide airports registered in the SITA database.

What your AI can do

Get airport reference details

Gets full metadata for one airport using its 3-letter IATA code (e.g., LHR).

List sita airports

Provides a full list of every global airport registered in the SITA database.

List airport terminals

Lists all terminals and gate areas associated with a specific airport code.

List All Global Airports

Pull the full directory of every airport in the SITA system using list_sita_airports.

Retrieve Full Airport Metadata

Fetch complete reference data for a single airport by providing its 3-letter IATA code, using get_airport_reference_details.

List Terminal and Gate Areas

Get an inventory of all terminals, concourses, and gates belonging to a specific airport code via list_airport_terminals.

Included with Plan

Waiting for input…

AI Agent

SITA Airport Reference API MCP Server: 3 Tools for Aviation Data

Use these three tools to query comprehensive airport data: list all global airports, get detailed metadata on a single location, or map out a specific airport's terminals.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using SITA Airport Reference API on Vinkius

Get Airport Reference Details

Gets full metadata for one airport using its 3-letter IATA code (e.g., LHR).

List Sita Airports

Provides a full list of every global airport registered in the SITA database.

List Airport Terminals

Lists all terminals and gate areas associated with a specific airport code.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Claude AI

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

3

Start a conversation

Open a new chat. The SITA Airport Reference API integration is available immediately — no restart needed.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with SITA Airport Reference API, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 5,100+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week
SITA Airport Reference API MCP server cover

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by SITA. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 3 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Finding airport infrastructure details shouldn't involve a dozen API calls.

Today, if your app needs to map out an itinerary, you often hit a wall. You might first use one service just for the IATA code, then switch to another tool that gives basic metadata, and finally hunt down a third endpoint just for terminal names—copying codes from one dashboard into another.

With this MCP server, your agent handles it all in two steps. Ask your client: 'Give me everything about Paris.' It runs the necessary tools, aggregates the location data via `get_airport_reference_details`, and gives you a single, structured object. Simple.

Using list_airport_terminals gets you facility maps, not just names.

Manually listing terminals is worse. You pull basic airport details and get 'Terminals exist.' That tells you nothing about the actual layout or how many active gates are in Terminal 4 versus Terminal 5. It's useless for routing logic.

The `list_airport_terminals` tool solves this by giving you an inventory: it lists every concourse, terminal name, and gate area associated with that code. You get the full structural map right in your data stream.

What your AI can actually do with this

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.

Built · Hosted · Managed by Vinkius SITA Airport Reference API - Global Flight Data
Server ID 019d8481-363a-714b-977d-bbf63c170f46
Vinkius Inspector
Compliance Grade A+
Score 100/100
Vinkius Inspector Badge — Score 100/100

Questions you might have

How do I find all airports using list_sita_airports? +

You just ask your agent to run list_sita_airports. This tool immediately returns a comprehensive directory of every global airport registered in the SITA database, giving you a master list of codes and names.

Does get_airport_reference_details give me coordinates? +

Yes. The get_airport_reference_details tool returns comprehensive metadata, including precise latitude/longitude coordinates, timezone data, city, and country for the specified airport code.

What is the difference between list_sita_airports and get_airport_reference_details? +

They serve different purposes. Use list_sita_airports when you need a full directory to search through codes. Use get_airport_reference_details when you already have the code (like JFK) and need all its specific details.

Can list_airport_terminals show me gate capacity? +

The tool lists all terminals, concourses, and gate areas for an airport. While it doesn't report current capacity, it gives you the full inventory of every assigned gate area.

What IATA codes can I use with these tools? +

You must provide a 3-letter IATA code (like LHR or GRU). The tool requires this specific format to correctly identify the airport in the SITA database.

How do I authenticate my calls to get_airport_reference_details? +

You must acquire an API Key from the SITA Developer Portal. Your AI client passes this key in the request headers for every call. This step authenticates your session and grants access to the live reference database.

What happens if I provide an invalid code when calling list_airport_terminals? +

The tool returns a specific error message that indicates failure, preventing system crashes. You must pass a valid 3-letter IATA code for the target airport. The agent will receive a structured 'Code Not Found' response.

How can I use results from list_sita_airports with get_airport_reference_details? +

You chain the tools by taking an IATA code found via list_sita_airports and passing it as a direct argument to get_airport_reference_details. This allows you to query metadata for multiple airports in one workflow.

What format are airport codes in? +

The API uses standard 3-letter IATA airport codes (e.g., 'LHR' for London Heathrow, 'JFK' for New York JFK, 'GRU' for São Paulo Guarulhos).

Is this a read-only API? +

Yes, all 3 tools are strictly read-only queries. The integration retrieves reference data and cannot modify anything in the SITA database.

Built & Managed by Vinkius 30s setup 3 tools

We've already built the connector for SITA Airport Reference API. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 3 tools are live and waiting. You're up and running in seconds.

Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.