
This wraps the AirportGap API, giving you access to airport data without needing authentication. The source doesn't list specific tools, but AirportGap typically provides airport lookups by IATA code, city, or location along with details like runways, terminals, and distance calculations. It's part of the Pipeworx gateway ecosystem, so you can either use this standalone endpoint or connect through their main gateway for combined access to 600+ other data sources. Useful when you're building travel tools, flight trackers, or need to validate airport codes and pull structured airport metadata on the fly.
Airports MCP — wraps AirportGap API (free, no auth required)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
search_airports | Look up an airport by city name (e.g. "Tokyo", "New York", "London") OR by 3-letter IATA code (e.g. "JFK", "LHR"). City lookup uses a bundled map of the top ~150 international hubs; cities with multiple airports return all primary ones. For airports not in the bundle, pass an IATA code or use the aviationstack pack for full-text name/country search. |
get_airport | Get airport details by IATA code (e.g., "JFK", "LHR"). Returns name, city, country, coordinates, altitude, timezone. |
calculate_distance | Calculate straight-line distance between two airports by IATA code (e.g., "JFK" to "LHR"). Returns kilometers and miles. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"airports": {
"url": "https://gateway.pipeworx.io/airports/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/airports/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Airports data" })
The gateway picks the right tool and fills the arguments automatically.
MIT