Sigrok Mcp Server

Name: Sigrok Mcp Server
Author: KenosInc

@KenosInc

About Sigrok Mcp Server

AI-powered logic analyzer control via Model Context Protocol - connect Claude, Cursor to sigrok-cli for automated signal capture and protocol decoding

#sigrok #logic-analyzer #protocol-decoder #hardware-debugging

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "sigrok": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--privileged",
        "ghcr.io/kenosinc/sigrok-mcp-server"
      ]
    }
  }
}

Tools

List all supported hardware drivers

List all supported protocol decoders

List all supported input file formats

List all supported output file formats

Show detailed info about a protocol decoder (options, channels, documentation)

Show detailed info about a hardware driver (functions, scan options, devices)

Show sigrok-cli and library version information

Scan for connected hardware devices

Capture communication data from a device and save to file

Decode protocol data from a captured file using protocol decoders

Check firmware file availability in sigrok firmware directories

Overview

What is Sigrok Mcp Server?

This is an MCP server that integrates sigrok’s signal capture and protocol decoding with AI agents like Claude Code, Codex, and Cursor. It interfaces with logic analyzers and measurement devices via sigrok-cli, supporting over 100 protocols including I2C, SPI, UART, and CAN.

How to use Sigrok Mcp Server?

Run with Docker (docker pull ghcr.io/kenosinc/sigrok-mcp-server) or build from source with Go 1.25+ and sigrok-cli installed. Configure via environment variables (SIGROK_CLI_PATH, SIGROK_TIMEOUT_SECONDS, SIGROK_WORKING_DIR). On a client like Claude Desktop, add a JSON config pointing to the server command. Use tools such as scan_devices, capture_data, and decode_protocol for signal analysis.

Key features of Sigrok Mcp Server

List supported hardware, decoders, input/output formats.
Show detailed decoder and driver information.
Scan for connected hardware devices.
Capture communication data from a device.
Decode captured data with protocol decoders.
Check firmware availability for devices.

Use cases of Sigrok Mcp Server

Debugging I2C, SPI, or UART communication with an LLM.
Automating signal capture and analysis in CI pipelines.
Providing a natural‑language interface to sigrok for non‑experts.

FAQ from Sigrok Mcp Server

What is the difference between this server and using sigrok‑cli directly?

The server wraps sigrok‑cli in an MCP interface, allowing LLMs to programmatically capture, decode, and analyze signals without manual command‑line use.

Does this server require firmware files?

Some hardware drivers require firmware that cannot be bundled due to licensing. The server works without firmware for devices that don’t need it (e.g., demo, protocol‑only analysis). Use the check_firmware_status tool to verify availability.

What transport does the server use?

It communicates over stdio (stdin/stdout JSON‑RPC).

What are the runtime dependencies?

Go 1.25+ and sigrok‑cli must be installed on the host, or you can run the Docker image. On Docker, access to USB devices may require --privileged and firmware volumes.