Oeradio MCP Server

Oeradio MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Amateur radio MCP server with band plans, EIRP, cable loss, antenna gains, and more.

What you get

Public MCP (Model Context Protocol) server providing amateur radio tools and calculations for IARU Region 1 operators.

Model Context Protocol (MCP) is an open standard that allows AI assistants to use external tools. Originally developed by Anthropic, MCP is now supported by Claude, ChatGPT, and Gemini. With this server, you can ask your AI assistant questions like "What are the band limits for 20m?" or "How long should my dipol be for 14.2 MHz?" and get instant calculations.

What the assistant can call

Once Oeradio is connected, these are the calls the assistant has available:

• get_band_plan — Get IARU Region 1 band plan for a specific band
• list_all_bands — List all amateur radio bands
• check_frequency — Check if a frequency is within amateur bands
• calculate_eirp — Calculate EIRP/ERP from power, cable loss, and antenna gain
• calculate_cable_loss — Calculate coaxial cable attenuation
• compare_cables — Compare all cable types at a given frequency and length
• calculate_battery_runtime — Calculate battery runtime for portable operation
• get_antenna_gain — Look up typical antenna gain values
• calculate_wavelength — Calculate wavelength and antenna lengths
• calculate_swr_loss — Calculate power loss from SWR mismatch
• convert_power — Convert between Watt, dBm, and dBW
• callsign_lookup — Search Austrian callsigns (fb.gv.at, QRZ.com, HamQTH fallback)

Setting it up

The server ships on npm as npm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

• Node.js 20+ - Docker (optional)

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Oeradio's toolset — get_band_plan, list_all_bands, check_frequency and 11 more — is a fair guide to whether it matches your workflow. It is maintained by achildrenmile; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Oeradio.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the oeradio mcp server does with a few real requests.