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 分