`airport_runways`

Pack: airports · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/airport_runways for the schema, then POST the same URL with its arguments for the data.

Per-runway length/width/surface/lighting/heading for one airfield.

Tool description as the model sees it

Runway details for one airfield from the OurAirports dataset: for each runway, length and width in feet, surface type, whether it is lighted, whether it is closed, and both ends’ ident/coordinates/elevation/heading/displaced threshold. Pass any code ourairports_lookup accepts (ICAO, IATA, GPS or local ident). An airfield with no fixed-wing runways on file (e.g. most heliports) returns an empty runways array with found:true, not an error. An unrecognized airfield code is refused with a clear error, never an empty success.

Parameters

Name	Type	Required	Description
`code`	string	yes	ICAO/IATA/GPS/local code, e.g. “KJFK” or “JFK”.

Example call

Arguments

{
  "code": "KJFK"
}

curl

curl -X POST https://gateway.pipeworx.io/airports/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"airport_runways","arguments":{"code":"KJFK"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('airport_runways', {
  "code": "KJFK"
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the airports pack

{
  "mcpServers": {
    "airports": {
      "url": "https://gateway.pipeworx.io/airports/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

airport_runways