
Sigrok MCP Server
Drive sigrok-cli from Claude Code or Cursor to capture traces and decode embedded protocols without manual CLI juggling.
Overview
sigrok MCP Server is a MCP server for the Build phase that wraps sigrok-cli so agents can capture signals, decode protocols, and query instruments.
What is this MCP server?
- Stdio MCP transport with OCI package ghcr.io/kenosinc/sigrok-mcp-server:0.2.0
- Wraps sigrok-cli for capture, protocol decode, and instrument queries
- Configurable via SIGROK_CLI_PATH, SIGROK_TIMEOUT_SECONDS, and SIGROK_WORKING_DIR
- Suited to UART, SPI, I2C, and other sigrok-supported decoders
- Local execution model—no cloud signal data unless you choose to send it
- Server version 0.2.0
- 3 documented environment variables for CLI path, timeout, and working directory
What problem does it solve?
Debugging serial buses and logic traces forces constant context-switching between the agent chat and a separate sigrok-cli terminal.
Who is it for?
Solo builders and tiny teams doing embedded bring-up who already run sigrok-cli locally and want agent-driven trace capture.
Skip if: Pure software SaaS projects with no hardware probes, or teams that cannot install sigrok-cli and device drivers on the MCP host.
What do I get? / Deliverables
After you register the server, your agent can run capture and decode workflows through MCP tools while you stay in one coding session.
- Agent-invokable capture and decode operations via sigrok-cli
- Instrument query results returned into the coding session
- Repeatable local signal-analysis workflow without manual CLI copy-paste
Recommended MCP Servers
Journey fit
How it compares
Hardware signal integration via MCP, not a generic code-review or compliance skill.
Common Questions / FAQ
Who is Sigrok MCP Server for?
It is for developers and indie hardware hackers who use sigrok-compatible capture gear and want their AI agent to run sigrok-cli commands safely through MCP.
When should I use Sigrok MCP Server?
Use it during firmware integration and protocol debugging when you need repeated captures, decoder runs, or instrument queries alongside agent-assisted code changes.
How do I add Sigrok MCP Server to my agent?
Add the stdio MCP entry from the server manifest, set SIGROK_CLI_PATH to your binary, optionally tune timeout and working directory, then restart Claude Code or Cursor so the sigrok tools appear.