Mcp Sigrok
Drive sigrok-cli and logic analyzer captures from your agent when debugging embedded firmware or serial protocols.
Overview
io.github.daedalus/mcp-sigrok is an MCP server for the Build phase that exposes sigrok-cli logic analyzer and protocol decoding to coding agents via stdio.
What is this MCP server?
- Stdio MCP transport with PyPI package mcp-sigrok (v0.1.0)
- Exposes sigrok-cli for logic analyzer capture and protocol decode
- Targets firmware and hardware builders using supported LA hardware
- Reduces manual sigrok terminal juggling during bring-up debug
- Depends on sigrok-cli and compatible logic analyzer hardware installed locally
- Published server version 0.1.0 on PyPI identifier mcp-sigrok
- Stdio transport in MCP server schema
- Repository GitHub daedalus/mcp-sigrok
Community signal: 1 GitHub stars.
What problem does it solve?
Debugging buses with sigrok means switching between terminal, capture files, and the agent instead of one integrated hardware debug loop.
Who is it for?
Indie hardware or firmware builders who already use sigrok and want agent-assisted capture and protocol analysis during integration.
Skip if: Pure web or mobile app builders with no logic analyzer, or teams unwilling to install sigrok-cli and hardware dependencies.
What do I get? / Deliverables
After setup, your agent can invoke sigrok-cli-backed MCP tools so captures and decode steps stay coordinated with your firmware work.
- sigrok-cli operations exposed as MCP tools
- Agent-guided capture and decode workflows during hardware bring-up
- Less context switching between terminal sigrok and coding sessions
Recommended MCP Servers
Journey fit
Hardware protocol work happens while you build and integrate devices or firmware tooling, not during distribution or analytics. sigrok-cli bridge is a specialized local integration between lab hardware and the agent, matching build integrations.
How it compares
sigrok-cli MCP bridge for lab hardware, not a cloud monitoring or application log aggregator.
Common Questions / FAQ
Who is io.github.daedalus/mcp-sigrok for?
Developers working on embedded systems, IoT prototypes, or protocol debugging who rely on sigrok-cli and compatible logic analyzer hardware.
When should I use io.github.daedalus/mcp-sigrok?
Use it during build integrations when bringing up firmware, validating serial protocols, or iterating on hardware debug with sigrok captures.
How do I add io.github.daedalus/mcp-sigrok to my agent?
Install sigrok-cli and hardware drivers, install mcp-sigrok from PyPI, register the stdio MCP server in your agent config, and verify tools against a connected analyzer.