About yoelbassin/gnuradioMCP
yoelbassin/gnuradioMCP is an MCP server published by yoelbassin in the Developer Tools category: mCP server for GNU Radio.
The repository has 55 stars and 13 forks, with the last commit 2 months ago. Recent commit activity is the strongest signal that reported issues will get attention.
Install
git clone https://github.com/yoelbassin/gr-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about yoelbassin/gnuradioMCP
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 5 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- ✓License declaredUsable under a stated license.
- ✓Tests presentA test suite exists in the repository.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
Releases
README
Marconi 🤖
o)))
|
.-------.
| o o |
| v |
'-------'
Hi! I'm Marco.
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.
Early development — v1.0 is simulation-only (no hardware yet). See
ROADMAP.md.
Proviously known as GNURadio/GR-MCP.
Requirements
uvand 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.
Install
In Claude Code:
/plugin marketplace add yoelbassin/gr-mcp
/plugin install marconi
That's it — uv starts the MCP server on first use and loads the skills. Nothing
else to configure.
Use it
Ask in plain language:
"Simulate an FM station at 100.3 MHz and build me a receiver."
"Here's a capture,
mystery.wav— survey what's on the air, then decode the strongest carrier."
I pick the right skill and drive the workflow end to end:
- 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
Artifacts land under artifacts/ in the server's working directory; set
MARCONI_WORKSPACE to put them elsewhere.
License
README fetched from the repository 5 days ago. The original is authoritative.