Sigrok Mcp Server

Created By
KenosInc3 months ago
A Model Context Protocol (MCP) server for sigrok — enables AI agents like Claude Code, Codex, and Cursor to capture, decode, and analyze signals from logic analyzers and measurement devices. Supports I2C, SPI, UART, CAN, and 100+ protocols via sigrok-cli.
Overview

sigrok-mcp-server

CI Go Version License: MIT GitHub Release

A Model Context Protocol (MCP) server for sigrok — enables AI agents like Claude Code, Codex, and Cursor to capture, decode, and analyze signals from logic analyzers and measurement devices. Supports I2C, SPI, UART, CAN, and 100+ protocols via sigrok-cli.

Documentation | Getting Started

Tools

ToolDescription
list_supported_hardwareList all supported hardware drivers
list_supported_decodersList all supported protocol decoders
list_input_formatsList all supported input file formats
list_output_formatsList all supported output file formats
show_decoder_detailsShow detailed info about a protocol decoder (options, channels, documentation)
show_driver_detailsShow detailed info about a hardware driver (functions, scan options, devices)
show_versionShow sigrok-cli and library version information
scan_devicesScan for connected hardware devices
capture_dataCapture communication data from a device and save to file
decode_protocolDecode protocol data from a captured file using protocol decoders
check_firmware_statusCheck firmware file availability in sigrok firmware directories

Quickstart

Docker

docker pull ghcr.io/kenosinc/sigrok-mcp-server
docker run -i ghcr.io/kenosinc/sigrok-mcp-server

From source

Requires Go 1.25+ and sigrok-cli installed on your system.

go build -o sigrok-mcp-server ./cmd/sigrok-mcp-server
./sigrok-mcp-server

The server communicates over stdio (stdin/stdout JSON-RPC).

Configuration

Configuration is via environment variables:

VariableDefaultDescription
SIGROK_CLI_PATHsigrok-cliPath to the sigrok-cli binary
SIGROK_TIMEOUT_SECONDS30Command execution timeout in seconds
SIGROK_WORKING_DIR(empty)Working directory for sigrok-cli execution

MCP Client Configuration

Claude Desktop

Add to your claude_desktop_config.json:

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

To access USB devices from the container:

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

To also provide firmware files for devices that require them (e.g. Kingst LA2016):

{
  "mcpServers": {
    "sigrok": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm", "--privileged",
        "-v", "/path/to/sigrok-firmware:/usr/local/share/sigrok-firmware:ro",
        "ghcr.io/kenosinc/sigrok-mcp-server"
      ]
    }
  }
}

Claude Code

claude mcp add sigrok -- docker run -i --rm ghcr.io/kenosinc/sigrok-mcp-server

With USB access and firmware:

claude mcp add sigrok -- docker run -i --rm --privileged -v /path/to/sigrok-firmware:/usr/local/share/sigrok-firmware:ro ghcr.io/kenosinc/sigrok-mcp-server

Firmware

Some hardware drivers require firmware files that cannot be bundled with this server due to licensing restrictions. The server works without firmware for devices that don't need it (e.g. demo, protocol-only analysis). For devices that require firmware (e.g. Kingst LA2016, Saleae Logic16), mount your firmware directory into the container at /usr/local/share/sigrok-firmware.

Use the check_firmware_status tool to verify firmware availability and diagnose device detection issues.

See the sigrok wiki for firmware extraction instructions for your device.

Architecture

MCP Client (LLM)
    |  stdio (JSON-RPC)
    v
sigrok-mcp-server (Go)
    |  exec.Command
    v
sigrok-cli
    |
    v
libsigrok / libsigrokdecode
  • Transport: stdio (stdin/stdout JSON-RPC)
  • No C bindings: sigrok-cli is the sole interface to sigrok
  • Capture & decode: capture_data acquires data from devices; all other tools are read-only queries
  • Structured output: Raw sigrok-cli text output is parsed into JSON

Workflow Example

A typical signal analysis workflow using Claude:

  1. scan_devices — Discover connected hardware
  2. show_driver_details — Check driver capabilities
  3. capture_data — Capture communication data to file
  4. decode_protocol — Decode captured data with protocol decoders
  5. Claude analyzes the decoded output and explains the communication

Development

# Build
go build ./...

# Test
go test ./... -race

# Lint
golangci-lint run ./...

Project Structure

cmd/sigrok-mcp-server/     Entry point
internal/
  config/                  Environment-based configuration
  sigrok/
    executor.go            sigrok-cli command execution with timeout
    parser.go              Output parsing (list, decoder, driver, version, scan)
    testdata/              Real sigrok-cli output fixtures
  tools/
    tools.go               MCP tool definitions and registration
    handlers.go            Tool handler implementations

License

MIT (Kenos, Inc.)

Server Config

{
  "mcpServers": {
    "sigrok": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--privileged",
        "ghcr.io/kenosinc/sigrok-mcp-server"
      ]
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
KenosInc
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Ghl Command
@Elite DCs LLC

GoHighLevel MCP server for Claude. 212 tools across 43 modules, including the only programmatic GHL workflow builder (private API, reverse-engineered), funnel + page editor, form builder, pipeline builder, pre-deploy validator, multi-sub-account switching, bulk operations, and full account export. $97 one-time, lifetime updates. GHL Command gives Claude full programmatic control of GoHighLevel through 212 tools across 43 modules. Built for GoHighLevel agency operators who manage many client sub-accounts and want to onboard new clients in minutes instead of days. Exclusive capabilities (none of the free GHL MCPs have these): - Programmatic workflow builder. Create, edit, clone, publish, and validate complete GHL workflows from a single prompt. GHL's public API has no workflow write endpoints; this uses their internal API (the same one their UI calls). - Funnel + page editor and form builder (also private API). - Pipeline builder, goal event builder, full 57-native-trigger registry. - Pre-deploy validator that catches GHL's silent invalid-ID failure (a common workflow-breaking bug GHL never warns you about). - Multi-sub-account token registry. Switch between any client account mid-conversation; API keys swap automatically. - Bulk operations: tag, update, enroll, delete hundreds of contacts in one command. - Full account export and side-by-side location diff for audit or migration. Works with Claude Desktop App, Claude Code (terminal), and headless on a Linux server or droplet. $97 one-time, 3 machines, no subscription, lifetime updates. 30-day time-back guarantee: save 5+ hours on one real client build or full refund.

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Fixmypdf

15 hours ago