Log inSubmit server
MCP Sigrok logo

MCP Sigrok

Expose sigrok-cli hardware discovery, capture, file processing, and protocol decoding through MCP tools.

InstallRepository
Full README Compare alternatives Embed widget Claim this listing

Install MCP Sigrok

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-sigrok": {
      "command": "uvx",
      "args": [
        "mcp-sigrok"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The mcp-sigrok MCP server exposes sigrok-cli operations for logic analyzer hardware, captured files, and protocol decoders. It runs as a stdio MCP process and delegates hardware discovery, acquisition, configuration, decoding, and format handling to the locally installed sigrok-cli command. Use it when an MCP client needs to inspect compatible devices, capture samples, process session files, or decode protocols such as I2C.

Use cases

  • Scan for connected logic analyzers
  • Capture samples from supported hardware
  • Decode I2C data from a session file
  • Inspect available sigrok drivers and formats
  • Configure a hardware driver before acquisition

Key features

  • Logic analyzer device discovery
  • Sample capture by count or duration
  • Protocol decoder listing and documentation
  • Input and output format inspection
  • Capture file loading and processing
  • Driver configuration

Tools13

What MCP Sigrok lets your agent do. Expand a tool for its parameters.

Self-reported~141 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/5 checks healthy over the last 41d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · mcp-sigrok (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
Last commit6mo agoMost recent push to the default branch.
Tools exposed13Callable tools this server registers over MCP.

How MCP Sigrok works

What mcp-sigrok does

The mcp-sigrok MCP server makes sigrok-cli functionality available through MCP tool calls. It is intended for workflows involving logic analyzers and other hardware supported by the sigrok software suite. The server can report sigrok-cli version information, enumerate supported features and formats, inspect drivers, find connected devices, acquire samples, process existing capture files, and expose protocol-decoder documentation.

The available operations cover both hardware-backed and file-based workflows. A client can scan for detectable devices before selecting a driver, request information about that driver, configure it, and capture samples. Alternatively, it can load an existing input file and request protocol decoding or another supported output format.

How it works

The mcp-sigrok MCP server runs as a stdio process. MCP clients start the mcp-sigrok executable, then call its tools over the client connection. The underlying sigrok-cli installation supplies the actual hardware support, input and output formats, acquisition behavior, and protocol-decoder availability.

A typical hardware workflow is to check the version, list drivers, scan for devices, inspect a driver, set configuration, and capture either a sample count or a fixed duration. File-based processing uses the load operation with an input path and optional protocol-decoder or output settings. The result depends on the locally installed sigrok-cli version and its available drivers.

Setup and configuration

Install the Python package with:

Terminal
pip install mcp-sigrok

sigrok-cli must also be installed on the same system. On Debian or Ubuntu, the README provides sudo apt install sigrok-cli; on macOS, it provides brew install sigrok-cli. Building sigrok-cli from source is another documented option.

Run the server with:

bash
mcp-sigrok

An MCP client configuration needs to use mcp-sigrok as the command for the server. No environment variables are documented as required. Hardware access, device permissions, and the installed sigrok-cli features remain system-level prerequisites.

Tools and capabilities

The mcp-sigrok MCP server exposes tools for:

  • Reporting sigrok-cli version information.
  • Listing supported features, hardware drivers, input formats, output formats, and protocol decoders.
  • Scanning for devices and showing information for a selected driver.
  • Setting driver configuration values.
  • Capturing samples by count or for a specified duration.
  • Loading and processing an input file.
  • Showing documentation for protocol decoders.

These capabilities support tasks such as acquiring logic-analyzer data from selected channels, saving or converting captures, and decoding a protocol from a saved session. The supplied examples show capture with the fx2lafw driver and file processing with the i2c decoder, but the available choices are determined by the local sigrok-cli installation.

Limitations and notes

The server does not provide hardware support independently; sigrok-cli and its drivers must already be installed and able to access the target device. Supported protocols, file formats, and drivers can therefore vary between systems. Device presence is also required for live capture, while file processing requires a readable input file.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Sigrok

mcp-sigrok is an MCP server that connects AI clients to the locally installed sigrok-cli utility and supported logic analyzer hardware. Its main tools report versions, list drivers and protocol decoders, scan devices, configure drivers, capture samples, load files, and process captures with protocol decoding.

Install it with `pip install mcp-sigrok`, then install sigrok-cli separately on the same system. Debian and Ubuntu users can use `sudo apt install sigrok-cli`; macOS users can use `brew install sigrok-cli`.

Set the MCP server command to `mcp-sigrok`.

Yes, use the `load_file` tool to load and process an input file, optionally selecting a protocol decoder and output file. The README demonstrates decoding I2C from a `.sr` capture.

Related MCP servers

All in Embedded System All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Sigrok AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-sigrok?style=directory)](https://allmcps.com/mcp/mcp-sigrok)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-sigrok"><img src="https://allmcps.com/api/badge/mcp-sigrok?style=directory" alt="MCP Sigrok on AllMCPs" /></a>