Fr24api MCP vs Moxie Docs MCP
A side-by-side look at the Fr24api MCP and Moxie Docs MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Fr24api MCP for travel & transportation work as a local process; choose Moxie Docs MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Fr24api MCP when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
FR24_API_KEY. - You want tools like
get_live_flights_positions_light, get_live_flights_positions_full, get_live_flights_count.
Choose Moxie Docs MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Travel & Transportation | Knowledge & Memory |
| Quality signal | 56/100 · Good | 80/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | Freemium |
| Required env vars | FR24_API_KEY | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 30 | 2 |
| Directory activity | 2 views 0 installs 0 upvotes | 36 views 25 installs 4 upvotes |
| Tools | 13 | 12 |
| Full listing | View Fr24api MCP | View Moxie Docs MCP |
Tools & capabilities
Fr24api MCP tools 13
get_live_flights_positions_lightGet real-time aircraft positions with basic information.get_live_flights_positions_fullGet real-time aircraft positions with comprehensive flight details.get_live_flights_countGet count of live flights matching criteria.get_historic_flights_positions_fullGet historical flight positions with full details.get_historic_flights_positions_lightGet historical flight positions with basic information.get_historic_flights_countGet count of historical flights.get_flight_summary_fullGet comprehensive flight takeoff/landing information.get_flight_summary_lightGet essential flight takeoff/landing information.get_flight_summary_countGet count of flights in summary query.get_flight_tracksGet detailed positional tracks for a specific flight.get_airline_infoGet airline information by ICAO code.get_airport_info_lightGet basic airport information.- +1 more on the listing page
Moxie Docs MCP tools 12
moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.moxie.get_doc_impactGiven the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.moxie.get_api_contextGiven paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.moxie.review_changeSelf-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.moxie.get_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).moxie.list_docsPaginated, section-grouped table of contents of every generated doc.moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.moxie.propose_doc_removalRemove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branch.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Fr24api MCP
{
"mcpServers": {
"fr24api-mcp": {
"command": "npx",
"args": [
"-y",
"@flightradar24/fr24api-mcp"
],
"env": {
"FR24_API_KEY": "YOUR_FR24_API_KEY_HERE"
}
}
}
}
Moxie Docs MCP
{
"mcpServers": {
"moxie-docs-mcp": {
"command": "npx",
"args": [
"-y",
"moxie-docs"
]
}
}
}
Frequently asked questions
Fr24api MCP is categorized under Travel & Transportation and uses a local stdio subprocess. Moxie Docs MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Fr24api MCP for travel & transportation work and Moxie Docs MCP for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Fr24api MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add fr24api-mcp and moxie-docs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fr24api MCP has a quality signal of 56/100 (Good) with 2 views, 0 installs and 30 GitHub stars. Moxie Docs MCP has 80/100 (Excellent) with 36 views, 25 installs and 2 GitHub stars.
