MODEL CONTEXT PROTOCOL

Connect AI to AeroScope

AeroScope runs a public, read-only MCP server so any MCP-capable assistant — Claude, Cursor, Cline and others — can query its documentation and the live aircraft over any point on Earth, with the same verified, no-overstatement answers as the rest of the platform.

Connect it ↗REST API docs

The endpoint

One URL, spoken in JSON-RPC

POST https://aeroscope.live/api/mcp

Transport: Streamable HTTP (JSON-RPC 2.0). No authentication, read-only, rate-limited. This is an API endpoint for AI clients — not a web page; opening it in a browser returns a 405 by design (browsers send GET; MCP uses POST).

Tools

What an AI can call

Tool	Arguments	Returns
`search_aeroscope_docs`	query, limit?	The most relevant documentation excerpts with source URLs
`about_aeroscope`	—	A verified summary of capabilities, honest limits and the open dataset
`aircraft_over_location`	lat, lon, radius_nm?	Live aircraft over a point — identity, type, altitude, distance/bearing, military & emergency flags

Read-only & passive. The server only exposes what the live site already shows. It sees only aircraft that broadcast ADS-B, never claims capabilities AeroScope lacks, and can't transmit, jam or interfere with anything.

Connect

Add it to your assistant

Native Streamable-HTTP clients (Cursor, Cline, …)

{
  "mcpServers": {
    "aeroscope": { "url": "https://aeroscope.live/api/mcp" }
  }
}

Claude Desktop (via the mcp-remote bridge)

{
  "mcpServers": {
    "aeroscope": {
      "command": "npx",
      "args": ["mcp-remote", "https://aeroscope.live/api/mcp"]
    }
  }
}

Test it from a terminal

# list the available tools
curl -s -X POST https://aeroscope.live/api/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Try asking

Once connected, ask things like

"What's flying over 51.5, -0.1 right now, and is anything military?"

"How does AeroScope detect a spoofed aircraft?"

"What is AeroScope, and what can it not do?"

"Are there any emergency squawks over my coordinates?"

Compatibility. Works today with MCP clients that support remote Streamable HTTP (Cursor, Cline, dev tooling) and with Claude Desktop via mcp-remote. A listed ChatGPT connector additionally requires OAuth — a planned follow-up.

FAQ

Frequently asked questions

What is the AeroScope MCP endpoint?

https://aeroscope.live/api/mcp — a public, read-only Model Context Protocol server over Streamable HTTP (JSON-RPC 2.0). It lets AI assistants call three tools: search_aeroscope_docs, about_aeroscope, and aircraft_over_location (live aircraft over any point).

Do I need an API key?

No. The MCP server is public and read-only — it only exposes data the live site already shows. It is rate-limited to prevent abuse.

Why does opening the MCP URL in my browser show an error?

Because it is an API endpoint, not a web page. Browsers send a GET request; the MCP protocol uses POST with JSON-RPC, so a GET returns a 405 by design. Connect an MCP client (or use curl with POST) instead.

Does it work with ChatGPT?

It works today with MCP clients that support remote Streamable HTTP (e.g. Cursor, Cline) and with Claude Desktop via the mcp-remote bridge. A listed ChatGPT connector additionally requires OAuth, which is a planned follow-up.