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.
@KenosInc
Basic information
AI-powered logic analyzer control via Model Context Protocol - connect Claude, Cursor to sigrok-cli for automated signal capture and protocol decoding
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"
]
}
}
}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
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.
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.
The server wraps sigrok‑cli in an MCP interface, allowing LLMs to programmatically capture, decode, and analyze signals without manual command‑line use.
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.
It communicates over stdio (stdin/stdout JSON‑RPC).
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.
It supports all hardware that sigrok‑cli supports. Use `scan_devices` to discover connected devices; some may need firmware or driver configuration.

AI SEO tools for MCP clients — audit whether AI crawlers can read a website, validate JSON-LD and robots.txt, and generate llms.txt, AI-crawler-aware robots.txt, and JSON-LD schema without leaving the conversation.
Console, Backend and CLI to manage Capgo Instant update and Native build for Capacitor apps Build and upload to app store your mobile app

Multi-zone MCP server for GKE/EKS/AKS: Python tools from git, NeMo guardrails, SSO, autoscaling.

Nebelus is an enterprise agentic-AI platform for regulated industries. This MCP server exposes the Nebelus Construction API: ~48 tools that give an MCP client full agent build parity — create/update/probe agents, edit ag
CronWatch records every run of your scheduled jobs in your own database, and speaks up when one is missed, fails, gets stuck, runs slow or costs too much. CronWatch is free and open-source.
Comments