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
基本情報
AI-powered logic analyzer control via Model Context Protocol - connect Claude, Cursor to sigrok-cli for automated signal capture and protocol decoding
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"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.
Console, Backend and CLI to manage Capgo Instant update and Native build for Capacitor apps Build and upload to app store your mobile app
Codebase health as MCP tools: dead code, circular dependencies, coupling, architectural drift.

MilliGate is a developer-first remote MCP server that functions as a secure crypto paywall. By leveraging the HTTP 402 (Payment Required) protocol, it allows developers to monetize AI agents, APIs, and digital infrastruc
Remote MCP server from OSIR, an ICANN-accredited registrar: 105 tools and 11 prompts to search, register, renew, transfer, and manage domains, DNS, VPS, email, and websites from Claude, ChatGPT, Cursor, or any MCP client

OpenMark is a remote MCP server available at https://openmark.ai. Benchmark your own prompt on 100+ models with real API calls.
コメント