P
pipeworx-io/mcp-aviationstack
Aviationstack MCP — global flight + airport + airline data
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
远端端点(Claude Desktop / Cursor / Windsurf 共用 mcpServers)
{
"mcpServers": {
"pipeworx-io-mcp-aviationstack": {
"url": "https://gateway.pipeworx.io/aviationstack/mcp"
}
}
}把这段粘进 Claude Desktop / Cursor 的 mcpServers 配置即可。端点来自公开证据,我们没有替你安装或托管它。 官方 Registry 记录:这个端点没有列出任何请求头。这不等于免密 —— 以项目文档为准。
VS Code(.vscode/mcp.json —— 键名是 servers,远程要 type: http)
{
"servers": {
"pipeworx-io-mcp-aviationstack": {
"type": "http",
"url": "https://gateway.pipeworx.io/aviationstack/mcp"
}
}
}VS Code 的配置文件和另外三家不同:顶层键是 <code>servers</code>,远程端点还要写 <code>"type": "http"</code>。复制到 .vscode/mcp.json。
Claude Code(命令行)
claude mcp add --transport http pipeworx-io-mcp-aviationstack https://gateway.pipeworx.io/aviationstack/mcp
Claude Code 不收 JSON 文件,用这条命令直接加。
配置项的键名以你的客户端为准:客户端与 CLI
- ★ 数取值
- 0 ★ · pipeworx-io/mcp-aviationstack · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-10-31 · 最近见到 2026-11-14 · 共见到 15 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 1 个来源 · repo
常见问题(答案都来自我们的记录)
怎么安装?
我们【没有】从该仓库取到安装命令(我们的 install 覆盖率只有约 4%)。请看它的 README 或 releases 页。
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
pipeworx-io/mcp-aviationstack;我们收录于 2026-10-31;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# @pipeworx/aviationstack
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Aviationstack MCP — global flight tracking + airport / airline / route reference data.
Part of Pipeworx — an MCP gateway connecting AI agents to 1863+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
flights(flightiata?, flighticao?, depiata?, arriata?, airlineiata?, flightstatus?, limit?, offset?) — real-time + scheduled flights
airports(search?, iatacode?, icaocode?, limit?, offset?) — airport database (~10k airports)
airlines(search?, iatacode?, icaocode?, limit?, offset?) — airline database
cities(search?, iatacode?, countryiso2?, limit?) — city → primary airport mapping
countries(search?, countryiso2?, limit?) — country reference
routes(depiata?, arriata?, airlineiata?, flightnumber?, limit?) — scheduled routes
aviationstackfutureflights(iataCode, type, date, airlineiata?, airlineicao?, flightnumber?, limit?, offset?) — scheduled future flights at one airport for a specific date (type: departure or arrival). Backed by Aviationstack's /flightsFuture endpoint, which apilayer's 2026-10-06 notice opened only for the next 7 days — date must be tomorrow..today+7 (UTC); the pack refuses out-of-window dates itself before calling upstream (fleet #2700).
## Auth
Platform key: gateway env PLATFORMAVIATIONSTACKKEY
BYO: ?apiKey= after registering at https://aviationstack.com/signup/free
### Plan tier
As of 2026-10-06 the shared platform key is on a plan that reaches flights, airports,
airlines, cities, countries and routes live (verified: airports/JFK and
routes/JFK→LAX both returned non-empty data — neither is free-tier-only any more; an
earlier version of this README, written 2026-08-28, said otherwise and was stale).
aviationstackfutureflights was added the same day the vendor emailed that they opened
/flightsFuture more broadly; whether our specific plan reaches that endpoint was not
independently confirmed before this tool shipped (the platform key's raw value is a
Cloudflare/Supabase secret, not available to a pack-authoring session) — if a live call
answers HTTP 403 functionaccessrestricted, that means the plan doesn't cover this
endpoint yet and is a money/plan decision, not a pack bug.
The free plan (if the platform key ever reverts to it) is capped at 100 requests per
month, and once that is spent every endpoint answers 429 — including ones the tier would
otherwise allow. Free plan is also HTTP-only (no https) — the pack already uses http://.
Reading a 429 here: Aviationstack labels the monthly-allowance refusal with the code
ratelimitreached and only says "monthly" in the message text, so the code name argues
for a burst limit that clears in seconds when the truth is a wall that lasts until the plan
renews. The pack branches on the message, not the code. Fleet #577.
## Data source
http://api.aviationstack.com/v1/ — accesskey query param. /flightsFuture spec:
https://api.swaggerhub.com/apis/apilayer-863/AviationstackAPI/1.0.0/swagger.json
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
json
"mcpServers": {
"aviationstack": {
"url": "https://gateway.pipeworx.io/aviationstack/mcp"
Part of Pipeworx — an MCP gateway connecting AI agents to 1863+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
flights(flightiata?, flighticao?, depiata?, arriata?, airlineiata?, flightstatus?, limit?, offset?) — real-time + scheduled flights
airports(search?, iatacode?, icaocode?, limit?, offset?) — airport database (~10k airports)
airlines(search?, iatacode?, icaocode?, limit?, offset?) — airline database
cities(search?, iatacode?, countryiso2?, limit?) — city → primary airport mapping
countries(search?, countryiso2?, limit?) — country reference
routes(depiata?, arriata?, airlineiata?, flightnumber?, limit?) — scheduled routes
aviationstackfutureflights(iataCode, type, date, airlineiata?, airlineicao?, flightnumber?, limit?, offset?) — scheduled future flights at one airport for a specific date (type: departure or arrival). Backed by Aviationstack's /flightsFuture endpoint, which apilayer's 2026-10-06 notice opened only for the next 7 days — date must be tomorrow..today+7 (UTC); the pack refuses out-of-window dates itself before calling upstream (fleet #2700).
## Auth
Platform key: gateway env PLATFORMAVIATIONSTACKKEY
BYO: ?apiKey= after registering at https://aviationstack.com/signup/free
### Plan tier
As of 2026-10-06 the shared platform key is on a plan that reaches flights, airports,
airlines, cities, countries and routes live (verified: airports/JFK and
routes/JFK→LAX both returned non-empty data — neither is free-tier-only any more; an
earlier version of this README, written 2026-08-28, said otherwise and was stale).
aviationstackfutureflights was added the same day the vendor emailed that they opened
/flightsFuture more broadly; whether our specific plan reaches that endpoint was not
independently confirmed before this tool shipped (the platform key's raw value is a
Cloudflare/Supabase secret, not available to a pack-authoring session) — if a live call
answers HTTP 403 functionaccessrestricted, that means the plan doesn't cover this
endpoint yet and is a money/plan decision, not a pack bug.
The free plan (if the platform key ever reverts to it) is capped at 100 requests per
month, and once that is spent every endpoint answers 429 — including ones the tier would
otherwise allow. Free plan is also HTTP-only (no https) — the pack already uses http://.
Reading a 429 here: Aviationstack labels the monthly-allowance refusal with the code
ratelimitreached and only says "monthly" in the message text, so the code name argues
for a burst limit that clears in seconds when the truth is a wall that lasts until the plan
renews. The pack branches on the message, not the code. Fleet #577.
## Data source
http://api.aviationstack.com/v1/ — accesskey query param. /flightsFuture spec:
https://api.swaggerhub.com/apis/apilayer-863/AviationstackAPI/1.0.0/swagger.json
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
json
"mcpServers": {
"aviationstack": {
"url": "https://gateway.pipeworx.io/aviationstack/mcp"
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/pipeworx-io-mcp-aviationstack/)
- 来源
- github · https://github.com/pipeworx-io/mcp-aviationstack
- 按领域浏览
- MCP 服务
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。