Skip to main content
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

The server uses the streamable HTTP transport.

Connect

Then run /mcp in Claude Code, choose enhanced-radar, and sign in.
When the client connects, it opens a browser window. Sign in to your Enhanced Radar account and approve the connection.
The MCP page of the dashboard 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

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 and Billing. 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:
  • 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. 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.