← airsidelabs.com

INDIVIDUAL MCP TOOL

get_use_case

The full record for one use case, by id from a search or landscape result.

airsidelabs.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.airsidelabs.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_use_case and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

airsidelabs.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.airside-labs-aviation-tools]
url = "https://mcp.airsidelabs.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "airside-labs-aviation-tools": {
      "type": "http",
      "url": "https://mcp.airsidelabs.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: airside-labs-aviation-tools
Remote MCP URL: https://mcp.airsidelabs.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "airside-labs-aviation-tools": {
      "url": "https://mcp.airsidelabs.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "airside-labs-aviation-tools": {
      "type": "http",
      "url": "https://mcp.airsidelabs.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "airside-labs-aviation-tools",
  "transport": "streamable-http",
  "url": "https://mcp.airsidelabs.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • resolve_airport — Which aerodrome does this airport code or name refer to on a given date?
  • resolve_airline — Which airline does this designator, name or callsign refer to on a date?
  • resolve_aircraft_type — Which aircraft type does this designator or marketing name refer to?
  • resolve_registration — Which airframe wore this registration on a given date?
  • parse_flight_identifier — Split a flight designator into carrier and number, and identify the carrier.
  • flight_airframes — Which airframes have been heard operating this airline flight, how often and when -- from Airside Labs' own ADS-B receiver?
  • validate_identifiers — Do these aviation identifiers describe the same thing on this date?
  • report_unmet_need — Tell us what you came looking for and could not get from these tools.