Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Live flight tracking and aviation data via FlightAware AeroAPI (flights, airports, alerts).
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
AEROAPI_API_KEY, AEROAPI_OUTPUT_DIR, AEROAPI_CACHE_TTL, AEROAPI_STATIC_CACHE_TTL标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"flightaware": {
"command": "npx",
"args": [
"-y",
"@chrischall/flightaware-mcp"
],
"env": {
"AEROAPI_API_KEY": "your-value",
"AEROAPI_OUTPUT_DIR": "your-value",
"AEROAPI_CACHE_TTL": "your-value",
"AEROAPI_STATIC_CACHE_TTL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add flightaware --env AEROAPI_API_KEY=your-value --env AEROAPI_OUTPUT_DIR=your-value --env AEROAPI_CACHE_TTL=your-value --env AEROAPI_STATIC_CACHE_TTL=your-value -- npx -y @chrischall/flightaware-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"flightaware": {
"command": "npx",
"args": [
"-y",
"@chrischall/flightaware-mcp"
],
"env": {
"AEROAPI_API_KEY": "your-value",
"AEROAPI_OUTPUT_DIR": "your-value",
"AEROAPI_CACHE_TTL": "your-value",
"AEROAPI_STATIC_CACHE_TTL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"flightaware": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@chrischall/flightaware-mcp"
],
"env": {
"AEROAPI_API_KEY": "your-value",
"AEROAPI_OUTPUT_DIR": "your-value",
"AEROAPI_CACHE_TTL": "your-value",
"AEROAPI_STATIC_CACHE_TTL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
AEROAPI_OUTPUT_DIR envAEROAPI_CACHE_TTL envAEROAPI_STATIC_CACHE_TTL env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 chrischall 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:AEROAPI_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.4.0)于3天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, First Sale Scout
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Playbooks and a 14-day checklist for founders winning their first paying customers.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
{
"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.
| Area | Tools |
|---|---|
| Flights | fa_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 |
| Airports | fa_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 / aircraft | fa_get_operator, fa_get_operator_flights, fa_list_operators, fa_get_aircraft_owner |
| Schedules / predictive | fa_get_scheduled_flights, fa_foresight_search (premium tier) |
| Alerts | fa_list_alerts, fa_get_alert, fa_create_alert, fa_update_alert, fa_delete_alert, fa_get_alerts_endpoint, fa_set_alerts_endpoint |
| Health | fa_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.
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.
| variable | default | |
|---|---|---|
MCP_CONFIRM_MODE | ask-user | What 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_ELICITATION | on | off 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_SECONDS | 600 | How long a token stays valid. |
MCP_CONFIRM_SECRET | random per process | Signing key; set it only if tokens must survive a server restart. |
| Var | Required | Purpose |
|---|---|---|
AEROAPI_API_KEY | yes | Your AeroAPI key (sent as the x-apikey header). |
AEROAPI_OUTPUT_DIR | no | Default 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_TTL | no | Seconds to cache identical live-data GET responses (default: 15; 0 disables). Cuts AeroAPI per-query billing. |
AEROAPI_STATIC_CACHE_TTL | no | Longer TTL for reference data — airport/operator info, routes, ownership, canonical lookups (default: 3600; 0 disables). |
npm install
npm run build npm test
Every request rides your own AeroAPI key and counts against your subscription quota. See docs/FLIGHTAWARE-API.md for the pinned endpoint surface.
MIT