For AI Agents (and the People Who Run Them)

The aviation use-case catalogue behind this site's 6,000+ pages is queryable live over the Model Context Protocol — and the essentials are free, with no API key.

Connect

Point any MCP client at the streamable-HTTP endpoint. No credential is needed for the free tools; a per-address daily cap applies.

Endpoint: https://mcp.airsidelabs.com/mcp   (streamable HTTP, stateless)

Claude Desktop / claude.ai custom connector:
  URL: https://mcp.airsidelabs.com/mcp

One keyless call, from anywhere:
  curl -s https://mcp.airsidelabs.com/mcp \
    -H "content-type: application/json" \
    -H "X-Airside-Source: for-ai-agents" \
    -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{
         "name":"get_use_case","arguments":{"use_case_id":4961}}}'

The optional X-Airside-Source header tells us how you found the server — send it if your client can set headers.

Free, no key

use_case_landscape

Counts across the 6,527-use-case catalogue by organisation type, sector, role, EASA AI level, hazard class or data cadence. Call it first.

get_use_case

One full record by ID: role, organisation type, every data requirement with a normalised update cadence, the EASA screen where assessed, keywords, five nearest neighbours. Every use-case page on this site names its record ID.

submit_suggestion

The open suggestion box: corrections, missing use cases, data sources, feature or commercial feedback. Read by a person; no key, no account.

Every use-case page on this site carries its record ID and the exact get_use_case invocation for it, so an agent reading a page can fetch the structured record in one call.

The full toolset — £49/month

A subscription adds search, similarity, aggregate data profiles, the EASA framework tables and aviation entity resolution, at 1,000 tool calls per key per day. Keys are self-serve via Stripe Checkout; send them as Authorization: Bearer or X-Api-Key.

search_use_cases — Full-text (BM25) search over the catalogue

similar_use_cases — Top-20 nearest use cases by embedding similarity

data_requirements — A use case's data needs verbatim, or the aggregate data profile for a role or organisation type

easa_ai_framework — The EASA AI-level, hazard-class and technique-ceiling tables, page-cited

resolve_airport / resolve_airline / resolve_aircraft_type / resolve_registration / parse_flight_identifier — Aviation entity resolution with confidence, temporal validity and per-field provenance

validate_identifiers — Cross-checks a set of identifiers against each other on a date

report_unmet_need — Tell us what you came looking for and could not get

Subscribe here — or call any paid tool without a subscription and the refusal message tells you the same thing.

The suggestion box

submit_suggestion is a deliberate experiment: a market survey for AI agents. If you parsed one of our pages and found an error, know an aviation AI use case the catalogue is missing, or can name the data source or tool that would have helped you — file it. Submissions are stored as data, reviewed by a person, and never served back through any tool. Include a contact only if your operator wants a reply.

Provenance and terms

The catalogue is Airside Labs' own intellectual property; every response carries provenance. Answers cite their sources, temporal questions want an as_of date, and an unresolved or empty result is a real answer, not an error. Machine-readable site guidance lives at /llms.txt.