Requires Go 1.25+ and `sigrok-cli` installed on your system.
Requires Go 1.25+ and sigrok-cli installed on your system. The sigrok mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
list_supported_hardware — List all supported hardware driverslist_supported_decoders — List all supported protocol decoderslist_input_formats — List all supported input file formatslist_output_formats — List all supported output file formatsshow_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 informationscan_devices — Scan for connected hardware devicescapture_data — Capture communication data from a device and save to filedecode_protocol — Decode protocol data from a captured file using protocol decoderscheck_firmware_status — Check firmware file availability in sigrok firmware directoriesYou will need one environment variable: SIGROK_CLI_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
The server ships on a container image as ghcr.io/kenosinc/sigrok-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Sigrok's toolset — list_supported_hardware, list_supported_decoders, list_input_formats and 8 more — is a fair guide to whether it matches your workflow. It is maintained by kenosinc; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Sigrok's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| 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 |
{
"mcpServers": {
"sigrok": {
"command": "docker",
"args": ["run", "-i", "--rm", "ghcr.io/kenosinc/sigrok-mcp-server"],
"env": {
"SIGROK_CLI_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SIGROK_CLI_PATH | Filesystem location the server is allowed to use. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.