# mcp-sigrok [Health: Active]

**Category:** 📟 Embedded System  
**Repository:** https://github.com/daedalus/mcp-sigrok  
**GitHub Stars:** 2  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-sigrok

## Description
MCP server exposing sigrok-cli functionality for logic analyzer hardware and protocol decoding

## Tools
Capabilities this server exposes over MCP:

- **version** — Get sigrok-cli version info
- **list_supported** — List all supported features
- **list_hardware_drivers** — List available hardware drivers
- **list_input_file_formats** — List supported input formats
- **list_output_file_formats** — List supported output formats
- **list_protocol_decoders** — List available protocol decoders
- **scan_for_devices** — Scan for detectable devices
- **show_device_info** — Show device info for a driver
- **capture** — Capture samples from hardware
- **capture_for_time** — Capture data for duration
- **load_file** — Load and process input file
- **show_decoder_docs** — Show protocol decoder docs
- **set_config** — Set driver configuration

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "mcp-sigrok": {
    "command": "uvx",
    "args": ["mcp-sigrok"]
  }
}
```

## Documentation

## 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:

```bash
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.

_Full upstream README: https://allmcps.com/mcp/mcp-sigrok/readme_