> ## Documentation Index
> Fetch the complete documentation index at: https://enhancedradar.com/docs/api/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect an AI assistant with the Enhanced Radar MCP server

> Connect Claude, Cursor, or another MCP client to the Enhanced Radar MCP server, sign in with OAuth, and use its tools for ATC transcripts, events, and statuses.

The Enhanced Radar MCP server gives AI assistants and agents the same data as the REST API through Model Context Protocol tools. Your client signs in with your Enhanced Radar account over OAuth, so you don't paste an API key into it.

## Server URL

```text theme={null}
https://api.enhancedradar.com/api/mcp
```

The server uses the streamable HTTP transport.

## Connect

> [tab] Claude Code
>
> ```bash theme={null}
> claude mcp add --transport http enhanced-radar https://api.enhancedradar.com/api/mcp
> ```
>
> Then run `/mcp` in Claude Code, choose `enhanced-radar`, and sign in.

> [tab] Other clients
>
> Add a remote MCP server with the URL above. Clients that read an `mcpServers` JSON file usually take this shape:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "enhanced-radar": {
>       "url": "https://api.enhancedradar.com/api/mcp"
>     }
>   }
> }
> ```

When the client connects, it opens a browser window. Sign in to your Enhanced Radar account and approve the connection.

> [!TIP]
>
> The **MCP** page of the [dashboard](https://api.enhancedradar.com) has a prompt you can copy into your assistant. It asks the assistant to set up the connection, walk you through signing in, and show you an example with real data.

## Tools

| Tool | What it does | Price |
| - | - | - |
| `search_facilities` | Turns an airport, TRACON, or center code or name into a `facility_id`. | Free |
| `get_facility` | Lists a facility's channels and their `atc_channel_id`s. | Free |
| `search_airlines` | Turns an airline code or name into an `airline_id`. | Free |
| `get_pricing` | What each charged item costs in US dollars, scheduled price changes, and account tiers, the same as [`GET /api/v0/pricing`](https://enhancedradar.com/docs/api/docs/api/api-reference/pricing). | Free |
| `get_airport_status` | Runways in use, flight rules, flow, traffic programs, METAR and TAF, and what was heard on frequency at one airport. | \$1.50 |
| `get_transcripts` | Transmissions in a window of up to 48 hours, newest first, or the best matches for a text search. `q` cannot be combined with `callsign`, `airline_id`, or `cursor`. | \$0.03 per transcript returned |
| `get_transcript` | One transmission by `audio_sample_id`. | \$0.03 |
| `get_transcript_audio` | A link to one transmission's audio. The link expires 3 minutes after it is created. | \$0.02 to \$40.00 per link, by monthly volume. See [Audio clips](https://enhancedradar.com/docs/api/docs/api/pricing.md#audio-clips). |
| `search_events` | Notable things that happened on frequency, described in plain words. | \$1.00 per search plus \$1.00 per event returned |
| `get_event` | One event with all its updates. | \$1.00 |
| `get_flight_status` | The latest status of one flight as of a given time. | \$0.12, free when there is no status |
| `search_pireps` | Pilot weather reports within a radius of a point, in a window of up to 6 hours. | \$0.15 per PIREP returned |
| `answer_question` | Answers a question that needs several lookups combined, such as whether a flight diverted and why, with the evidence behind it. | \$0.01 per record reviewed, at least 300 and at most `record_limit` (default 1,000) |

Tools are charged to your organization the same way as the matching REST routes: an empty transcript or PIREP result is free, as is `get_flight_status` when `status` is `null`, and `search_events` charges for the search even when no event matches. See [Pricing](https://enhancedradar.com/docs/api/docs/api/pricing.md) and [Billing](https://enhancedradar.com/docs/api/docs/api/concepts/billing.md).

Transcript results from `get_transcripts` and `get_transcript` leave out word timings: `word_timestamps` is `null`. The REST API returns them when they are available.

## Charges

Every tool result reports what the call cost, in `_meta.billing` and in an additional JSON text content block after the tool's data:

```json theme={null}
{"charged_usd": "0.030", "balance_usd": "987.650"}
```

* `charged_usd` is what the call cost, in US dollars with three decimal places.
* `balance_usd` is your organization's balance after the charge, in the same format. It is included when the call was billed.
* Free tools and failed tool calls report `charged_usd` `"0.000"` without a balance.

The tool's own data stays in `structuredContent` and its JSON text content block.

## Access

`search_facilities` works as soon as you sign in. The other tools need an account that has finished onboarding in the [dashboard](https://api.enhancedradar.com). When a tool reports that your account has not finished setup or that its balance does not cover a request, follow the link in its message.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.