GNURadio MCP Server

MCP server for GNU Radio. Exposed over MCP by the gnuradio mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

LLM-driven RF for Claude Code. Describe what you want on the air and I survey the spectrum, build and run the receiver, look at the signal, and leave a reproducible RF project behind — SigMF captures, YAML pipelines, and .grc flowgraphs you own.

Its toolset

Everything the assistant can do here goes through one of these:

• survey-spectrum — what's present (PSD, signal detection, spectrogram)
• simulate-scene — register a simulated device from a description
• build-receiver — channelize, demodulate, validate, run, verify, save
• debug-no-signal — locate the fault when a receiver outputs nothing
• tx-experiment — closed-loop transmit-then-receive in simulation
• escape-hatch — drop to the Python library when no tool fits

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

• uv and Python ≥ 3.13 - GNU Radio 3.10+ installed system-wide (conda-forge, your distro's package manager, or Homebrew) — needed to run pipelines and simulate. Analyzing existing IQ files doesn't require it.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. GNURadio's toolset — survey-spectrum, simulate-scene, build-receiver and 3 more — is a fair guide to whether it matches your workflow. It is maintained by yoelbassin; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against GNURadio's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• 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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the gnuradio mcp server does with a few real requests.