Wraps sigrok-cli for signal analysis: capture data, decode protocols, and query instruments.
{
"mcpServers": {
"io-github-kenosinc-sigrok-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 3 days ago. 1 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
Context cost
11 tools. ~500 tokens (0.3% of 200K).
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
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
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for io.github.KenosInc/sigrok-mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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
| Tool | Description |
|---|---|
| list_supported_hardware | List all supported hardware drivers |
| list_supported_decoders | List all supported protocol decoders |
| list_input_formats | List all supported input file formats |
| list_output_formats | List all supported output file formats |
| show_decoder_details | Show detailed info about a protocol decoder (options, channels, documentation) |
| show_driver_details | Show detailed info about a hardware driver (functions, scan options, devices) |
| show_version | Show sigrok-cli and library version information |
| scan_devices | Scan for connected hardware devices |
| capture_data | Capture communication data from a device and save to file |
| decode_protocol | Decode protocol data from a captured file using protocol decoders |
| check_firmware_status | Check firmware file availability in sigrok firmware directories |
docker pull ghcr.io/kenosinc/sigrok-mcp-server
docker run -i ghcr.io/kenosinc/sigrok-mcp-server
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 is via environment variables:
| Variable | Default | Description |
|---|---|---|
| SIGROK_CLI_PATH | sigrok-cli | Path to the sigrok-cli binary |
| SIGROK_TIMEOUT_SECONDS | 30 | Command execution timeout in seconds |
| SIGROK_WORKING_DIR | (empty) | Working directory for sigrok-cli execution |
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 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
Some hardware drivers require firmware files th