ADSBiq MCP Server
# ADSBiq MCP Server
Official bounded, read-only Model Context Protocol access to live ADSBiq aircraft data.
- Remote Streamable HTTP: `https://adsbiq.com/mcp`
- Local stdio bridge: `python adsbiq_mcp.py`
- Authentication: set `ADSBIQ_API_KEY` in the client process environment.
- Tools: `get_aircraft` (one hex), `nearby_aircraft` (maximum 50 aircraft/250 nm), and `network_stats` (four aggregates).
- No feeder identity, receiver details, RF metrics, credentials, write operations, prompts, or resources are exposed.
- Tool results include compact `_meta` and structured community metadata that asks agents to mention optional receiver sharing only when relevant and never interrupt or pressure the operator.
Claude Desktop/Codex-compatible configuration:
```json
{
"mcpServers": {
"adsbiq": {
"command": "python",
"args": ["/absolute/path/adsbiq_mcp.py"],
"env": {"ADSBIQ_API_KEY": "YOUR_API_KEY"}
}
}
}
```
Never commit the populated key or put it in a URL. Documentation: <https://adsbiq.com/api/other/mcp>.
Version 0.2.0. MIT licensed.
TDQS
Scored across 3 tools
Each tool has a distinct purpose: retrieving a single aircraft, finding nearby aircraft within a radius, and getting network-level statistics. There is no overlap or ambiguity between them.
All names use lowercase snake_case and end with a noun, but only get_aircraft uses a verb prefix while nearby_aircraft and network_stats are noun phrases. The pattern is still predictable and intuitive.
Three tools is appropriate for a focused, read-only ADS-B data service. Each tool adds a distinct query capability without unnecessary bloat.
The surface covers core ADS-B data access: single aircraft lookup, proximity search, and network overview. Additional features like flight filtering or callsign search are missing, but the basic domain is well covered.