Flightaware Mcp

io.github.chrischall由 GitHub 账号 chrischall 发布v1.4.1更新于 Nov 7, 2026

Live flight tracking and aviation data via FlightAware AeroAPI (flights, airports, alerts).

已验证STDIO仅桌面位置与生活数据与分析

概览

AI 生成的概览

通过 FlightAware AeroAPI 为助手提供实时航班追踪与航空数据的 MCP 服务器，涵盖航班、机场、运营商、时刻表与提醒。

可以做什么
  • 查询与搜索航班、航迹、位置、航线、历史记录并生成航班地图
  • 读取机场信息、航班看板、航班量、航线、附近机场、延误与天气
  • 查询运营商、其航班及飞机所有权信息
  • 获取计划航班与预测性搜索
  • 创建、更新、列出和删除航班提醒，并配置提醒回调端点
  • 运行健康检查，报告 API 密钥是否解析成功并被接受
适用场景
适合让助手回答某个航班的状态或位置、查看机场的到达情况与延误，或设置航班事件提醒。
运行要求
通过 npx 以 stdio 在本地运行（需要 Node.js）。需要 FlightAware AeroAPI 密钥，放在 AEROAPI_API_KEY 中，以 x-apikey 请求头发送。可选配置：AEROAPI_CACHE_TTL、AEROAPI_STATIC_CACHE_TTL、AEROAPI_OUTPUT_DIR，以及 MCP_CONFIRM_MODE、MCP_CONFIRM_ELICITATION、MCP_CONFIRM_TTL_SECONDS、MCP_CONFIRM_SECRET。需要访问 AeroAPI 的网络连接。
安装前请注意
AeroAPI 按查询计费，每次请求都会消耗订阅额度，缓存设置可减少重复计费。提醒的创建、更新、删除和端点设置会写入你的 AeroAPI 账户，需要确认；在无法弹出确认框的客户端上，会先返回预览和一次性令牌。航班地图 PNG 会写入配置的输出目录。README 说明该项目由 AI 开发，使用需自行斟酌。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Flightaware Mcp，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

flightaware-mcp

[npm]

MCP server for FlightAware AeroAPI (v4) — live flight tracking and aviation data for Claude. Track flights, read airport boards, look up operators and aircraft, fetch scheduled flights, and manage flight alerts, all over stdio.

Developed and maintained by AI (Claude Code). Use at your own discretion.

Quick start

json
{  "mcpServers": {    "flightaware": {      "command": "npx",      "args": ["-y", "@chrischall/flightaware-mcp"],      "env": { "AEROAPI_API_KEY": "your-aeroapi-key-here" }    }  }}

Get a key at flightaware.com/aeroapi/portal. The free Personal tier (500 calls/month) is enough to start; AeroAPI bills per query.

Tools

AreaTools
Flightsfa_get_flights, fa_search_flights, fa_search_flights_advanced, fa_search_flight_positions, fa_count_flights, fa_get_flight_track, fa_get_flight_position, fa_get_flight_route, fa_get_flight_map, fa_get_flight_history, fa_resolve_flight
Airportsfa_get_airport, fa_get_airport_flights, fa_get_airport_flight_counts, fa_get_airport_routes, fa_list_airports, fa_get_nearby_airports, fa_get_airport_delays, fa_get_airport_weather, fa_resolve_airport
Operators / aircraftfa_get_operator, fa_get_operator_flights, fa_list_operators, fa_get_aircraft_owner
Schedules / predictivefa_get_scheduled_flights, fa_foresight_search (premium tier)
Alertsfa_list_alerts, fa_get_alert, fa_create_alert, fa_update_alert, fa_delete_alert, fa_get_alerts_endpoint, fa_set_alerts_endpoint
Healthfa_healthcheck — is this connector working? Reports whether AEROAPI_API_KEY resolved, whether AeroAPI accepted it, and what to fix. Uses a static-cached lookup, so repeat checks are not re-billed.

Alert mutations (fa_create_alert, fa_update_alert, fa_delete_alert, fa_set_alerts_endpoint) ask you to confirm before they write — see Confirmations.

Confirmations

Every alert mutation asks for your confirmation before it touches your AeroAPI account. A client that can show a confirmation prompt (Claude Code) shows one. On a client that cannot (claude.ai, Claude Desktop), the first call makes no network call and returns a preview of the exact request (method, path, body) plus a confirmToken; only a repeat call with that token sends it. A token acts once, expires, and is refused if the request changed since the preview.

variabledefault
MCP_CONFIRM_MODEask-userWhat a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). ask-user: two steps — the first call does nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. auto: the same two steps, but the model may use the token after reviewing the preview itself. refuse: writes are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt, unless MCP_CONFIRM_ELICITATION=off. An unrecognised value is treated as refuse.
MCP_CONFIRM_ELICITATIONonoff never sends a confirmation prompt, so every client gets the MCP_CONFIRM_MODE path. Set it for a client that declares it can show prompts but never does (the gated call hangs — opencode 2.0.x). Any other value stays on, with a stderr warning.
MCP_CONFIRM_TTL_SECONDS600How long a token stays valid.
MCP_CONFIRM_SECRETrandom per processSigning key; set it only if tokens must survive a server restart.

Configuration

VarRequiredPurpose
AEROAPI_API_KEYyesYour AeroAPI key (sent as the x-apikey header).
AEROAPI_OUTPUT_DIRnoDefault directory for flight-map PNGs (default: ~/Downloads/flightaware-mcp). A per-call output_dir must be inside this directory (or inside ~/Downloads/flightaware-mcp when it is unset).
AEROAPI_CACHE_TTLnoSeconds to cache identical live-data GET responses (default: 15; 0 disables). Cuts AeroAPI per-query billing.
AEROAPI_STATIC_CACHE_TTLnoLonger TTL for reference data — airport/operator info, routes, ownership, canonical lookups (default: 3600; 0 disables).

Upgrading

next release

  • fa_get_flight_map on a hosted server (mcp-host, i.e. MCP_DATA_DIR or MCP_BLOB_BASE_URL set) no longer writes the PNG to the server's disk, where the caller could never open it. It returns the map as an inline image when it fits (10 MiB), otherwise a signed, expiring download link: { "via": "link", "url": "…", "expiresAt": "…", "note"?: "…" } in place of { "map": "<path>" }. inline:false or an output_dir there also yields a link (with a note). A hosted server with no blob store refuses an over-cap map with a too_large error.
  • Local installs: the default is unchanged ({ "map": "<path>" }). inline:true is now capped at 10 MiB; a bigger map is saved to disk and returned as { "map": "<path>", "note": "…" } instead of an oversized inline image.

Development

bash
npm installnpm run buildnpm test

Every request rides your own AeroAPI key and counts against your subscription quota. See docs/FLIGHTAWARE-API.md for the pinned endpoint surface.

License

MIT

来源：README.md，提交 6a6c92a

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

15
  1. v1.4.1最新Nov 7, 2026
  2. v1.4.0Nov 4, 2026
  3. v1.3.2Oct 16, 2026
  4. v1.3.1Oct 10, 2026
  5. v1.3.0Oct 7, 2026
  6. v1.2.4Oct 5, 2026
  7. v1.2.3Oct 3, 2026
  8. v1.2.2Sep 30, 2026
  9. v1.2.1Sep 25, 2026
  10. v1.2.0Sep 24, 2026
  11. v1.1.2Sep 23, 2026
  12. v1.1.1Sep 23, 2026
  13. v1.1.0Sep 20, 2026
  14. v1.0.0Sep 18, 2026
  15. v0.5.3Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分