Aviation Tools documentation

Connect

The server URL is the same everywhere:

https://mcp.airsidelabs.com/mcp

Claude (web, desktop, mobile, Cowork)

Settings, then Connectors, then search the directory for Airside and add it. Sign in when Claude asks; the first sign-in puts you on the free Explorer plan. You can still add it by hand instead — Add custom connector, paste the URL above, and leave client ID and secret empty.

ChatGPT

Open Plugins, search for aviation, and add Airside Aviation Tools. Sign in when asked; the first sign-in creates your free Explorer plan. Adding the URL above as a custom connector works too.

Company plans

On Claude Team or Enterprise, ChatGPT Team or Enterprise, and Copilot, a workspace admin enables connectors before members can add them. The admin brief is the page to send them: endpoint, sign-in, data handling, access, cost and the enabling steps.

Claude Code and other MCP clients

Claude Code signs in through your browser on first use:

claude mcp add --transport http airside-aviation https://mcp.airsidelabs.com/mcp

Clients that cannot sign in use an API key from your account page, sent as either header:

X-Api-Key: avt_live_...
Authorization: Bearer avt_live_...

Tools

Four tools need no account at all (marked free), within a daily per-address limit. Everything else needs a sign-in or a key on any plan, including the free Explorer plan.

• use_case_landscapefreeCounts across the AI use-case catalogue by organisation type, sector, role, EASA AI level, hazard class or data cadence. The place to start.
• get_use_casefreeOne full use-case record by ID, with data requirements, cadence, EASA screen and nearest neighbours.
• submit_suggestionfreeThe suggestion box: corrections, missing use cases, data sources, feature or commercial feedback.
• feedback_statusfreeWhether a suggestion or unmet-need report has been read, shipped or declined.
• search_use_casesFull-text search over the catalogue.
• similar_use_casesThe nearest use cases to a given one.
• data_requirementsA use case's data needs, or the data profile of a role or organisation type.
• trace_data_lineageWhere a data requirement's knowledge comes from.
• easa_ai_frameworkThe EASA AI-level, hazard-class and technique-ceiling tables, page-cited.
• trace_workflowWhere a use case sits in a real operational sequence: what runs before and after it, which role hands off to whom, and what passes between them at each step.
• resolve_airport, resolve_airline, resolve_aircraft_type, resolve_registration, parse_flight_identifierAviation identity resolution over validated registry data, with confidence, temporal validity and per-field provenance. Pass as_of for a past date.
• validate_identifiersCross-checks a set of identifiers against each other on a date.
• airport_network_integrationAn airport's level of integration with the EUROCONTROL Network Manager, or the FAA's TFDM programme, as of a date, from the published notices.
• airport_operator, airport_operations_status, airport_connectivity, airport_size_bandWho operates an airport, whether it is open for ordinary engagement, its nonstop destinations, and its ACI passenger size band, each with sources.
• route_capacityMonthly departures, seats, passengers and load factor on a directional US route, by carrier and aircraft type, from BTS T-100 over a rolling 24 months. Reported three months in arrears; never a schedule.
• airport_fleet_mixWhich carriers and aircraft types serve a US airport and how much of its scheduled traffic each carries, from BTS T-100.
• flight_airframesWhich airframes have operated an airline flight, how often and when: heard by our own ADS-B receiver, or filed in FAA flight plans. What was observed, not a prediction.
• scenarios, get_scenarioOne real day at a US airport as a timeline of public records, with lenses on the use cases it illustrates: what the data actually did, and the caveats that travel with it.
• report_unmet_needTell us what you looked for and could not get.

Every tool is read-only except submit_suggestion and report_unmet_need, which file a note for a person to read. None modifies or deletes anything.

How to read an answer

Answers say what they are: resolved, unresolved, lapsed, or not covered, with a confidence band and the sources behind each field. An empty or unresolved result is a real answer, not an error. Identity questions about the past need an as_of date, because codes are reused. Airport facts come from published documents with the date they were read and never guess from an airport's size or country.

Plans and limits

Explorer is free with 500 tool calls a month and one key. Pro is $59 a month with 10,000 calls. Team is $249 a month with 50,000 calls shared across five keys. All plans carry a per-minute rate limit. Calls past an allowance are refused with a message that says so and how to lift it. See plans and the account page.

Data and accuracy

Public and licensed reference sources, and observations from our own ADS-B receiver, each named in the answer with a date and method. Nothing here is real-time or operational data, and nothing should be relied on for flight operations or safety decisions. See the terms and the privacy policy.

Support

Email tools [at] airsidelabs [dot] com. Agents can also file what they could not get with report_unmet_need, and anyone can check what happened to a report with feedback_status.