get_flights_in_area
Pack: flights · 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/get_flights_in_area for the schema, then POST the same URL with its arguments for the data.
Find aircraft currently airborne in a geographic area, by bounding box. LIVE ADS-B data, no key required. Returns per aircraft: ICAO24 hex, callsign, registration (tail number), aircraft type, position, altitude, ground speed, heading, vertical rate, squawk, and any emergency code. Use for “what planes are over
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
lamin | number | yes | Minimum (south) latitude of the bounding box, degrees |
lomin | number | yes | Minimum (west) longitude of the bounding box, degrees |
lamax | number | yes | Maximum (north) latitude of the bounding box, degrees |
lomax | number | yes | Maximum (east) longitude of the bounding box, degrees |
limit | number | no | Max aircraft to return (1-500, default 200), nearest the box centre first. |
Example call
Arguments
{
"lamin": 40.6,
"lomin": -74,
"lamax": 40.8,
"lomax": -73.8
}
curl
curl -X POST https://gateway.pipeworx.io/flights/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_flights_in_area","arguments":{"lamin":40.6,"lomin":-74,"lamax":40.8,"lomax":-73.8}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('get_flights_in_area', {
"lamin": 40.6,
"lomin": -74,
"lamax": 40.8,
"lomax": -73.8
});
More examples
{
"lamin": 51.4,
"lomin": -0.5,
"lamax": 51.6,
"lomax": -0.2
}
Response shape
Full JSON Schema
{
"type": "object",
"oneOf": [
{
"type": "object",
"properties": {
"count": {
"type": "number",
"description": "Number of aircraft found in the bounding box"
},
"aircraft": {
"type": "array",
"items": {
"type": "object",
"properties": {
"icao24": {
"type": "string",
"description": "ICAO24 transponder address"
},
"callsign": {
"type": [
"string",
"null"
],
"description": "Aircraft callsign (trimmed)"
},
"origin_country": {
"type": "string",
"description": "Country of origin"
},
"longitude": {
"type": [
"number",
"null"
],
"description": "Current longitude in degrees"
},
"latitude": {
"type": [
"number",
"null"
],
"description": "Current latitude in degrees"
},
"altitude": {
"type": [
"number",
"null"
],
"description": "Barometric altitude in meters"
},
"velocity": {
"type": [
"number",
"null"
],
"description": "Velocity in meters per second"
},
"heading": {
"type": [
"number",
"null"
],
"description": "True track heading in degrees"
},
"on_ground": {
"type": "boolean",
"description": "Whether aircraft is on ground"
},
"registration": {
"type": [
"string",
"null"
]
},
"aircraft_type": {
"type": [
"string",
"null"
]
},
"description": {
"type": "null"
},
"operator": {
"type": "null"
},
"altitude_ft": {
"type": "number"
},
"ground_speed_kt": {
"type": [
"number",
"null"
]
},
"track_deg": {
"type": [
"number",
"null"
]
},
"vertical_rate_fpm": {
"type": [
"number",
"null"
]
},
"squawk": {
"type": [
"string",
"null"
]
},
"emergency": {
"type": "null"
},
"seconds_since_position": {
"type": "number"
}
},
"required": [
"icao24",
"callsign",
"longitude",
"latitude",
"on_ground"
]
}
},
"found": {
"type": "boolean",
"enum": [
true
],
"description": "Present and true on an answer; a miss is the found:false branch."
}
},
"required": [
"count",
"aircraft"
]
},
{
"type": "object",
"description": "A miss or an unavailable upstream: found:false with a reason and a hint (the shape check-found-false-schemas.mjs expects).",
"properties": {
"found": {
"type": "boolean",
"enum": [
false
]
}
},
"required": [
"found"
]
}
]
}
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 flights pack
{
"mcpServers": {
"flights": {
"url": "https://gateway.pipeworx.io/flights/mcp"
}
}
}
See Getting Started for client-specific install steps.