sigrok MCP Server
An MCP server that wraps sigrok-cli to allow AI agents to control logic analyzers and measurement devices. It supports listing hardware drivers, protocol decoders, and input/output formats, as well as scanning for connected devices, capturing communication data, and decoding protocols like I2C, SPI, UART, and CAN.
Package and access
Local package with source-attributed installation metadata. Koskamo does not execute packages during review.
What you can do with it
- List all supported hardware drivers and protocol decoders
- Scan for connected logic analyzer hardware devices
- Capture communication data from a device and save to file
- Decode protocol data from a captured file using protocol decoders
Source and maintenance
- Maintenance checked
Packages and installation
Source-provided package data. Koskamo has not executed or live-probed this package.
ghcr.io/kenosinc/sigrok-mcp-server:0.2.0
{
"transport": "stdio",
"identifier": "ghcr.io/kenosinc/sigrok-mcp-server:0.2.0",
"registryType": "oci",
"environmentVariables": [
{
"name": "SIGROK_CLI_PATH",
"description": "Path to sigrok-cli binary"
},
{
"name": "SIGROK_TIMEOUT_SECONDS",
"description": "Command execution timeout in seconds"
},
{
"name": "SIGROK_WORKING_DIR",
"description": "Working directory for sigrok-cli execution"
}
]
}Tools
Reported by the attributed source; not independently observed by Koskamo.
Connect from your client
Each snippet configures the same source-provided package; replace placeholders before use.
Cursor
{
"mcpServers": {
"sigrok-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SIGROK_CLI_PATH=<YOUR_SIGROK_CLI_PATH>",
"-e",
"SIGROK_TIMEOUT_SECONDS=<YOUR_SIGROK_TIMEOUT_SECONDS>",
"-e",
"SIGROK_WORKING_DIR=<YOUR_SIGROK_WORKING_DIR>",
"ghcr.io/kenosinc/sigrok-mcp-server:0.2.0"
],
"env": {
"SIGROK_CLI_PATH": "<YOUR_SIGROK_CLI_PATH>",
"SIGROK_TIMEOUT_SECONDS": "<YOUR_SIGROK_TIMEOUT_SECONDS>",
"SIGROK_WORKING_DIR": "<YOUR_SIGROK_WORKING_DIR>"
}
}
}
}Cline
{
"mcpServers": {
"sigrok-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SIGROK_CLI_PATH=<YOUR_SIGROK_CLI_PATH>",
"-e",
"SIGROK_TIMEOUT_SECONDS=<YOUR_SIGROK_TIMEOUT_SECONDS>",
"-e",
"SIGROK_WORKING_DIR=<YOUR_SIGROK_WORKING_DIR>",
"ghcr.io/kenosinc/sigrok-mcp-server:0.2.0"
],
"env": {
"SIGROK_CLI_PATH": "<YOUR_SIGROK_CLI_PATH>",
"SIGROK_TIMEOUT_SECONDS": "<YOUR_SIGROK_TIMEOUT_SECONDS>",
"SIGROK_WORKING_DIR": "<YOUR_SIGROK_WORKING_DIR>"
}
}
}
}VS Code
{
"servers": {
"sigrok-mcp-server": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SIGROK_CLI_PATH=<YOUR_SIGROK_CLI_PATH>",
"-e",
"SIGROK_TIMEOUT_SECONDS=<YOUR_SIGROK_TIMEOUT_SECONDS>",
"-e",
"SIGROK_WORKING_DIR=<YOUR_SIGROK_WORKING_DIR>",
"ghcr.io/kenosinc/sigrok-mcp-server:0.2.0"
],
"env": {
"SIGROK_CLI_PATH": "<YOUR_SIGROK_CLI_PATH>",
"SIGROK_TIMEOUT_SECONDS": "<YOUR_SIGROK_TIMEOUT_SECONDS>",
"SIGROK_WORKING_DIR": "<YOUR_SIGROK_WORKING_DIR>"
}
}
}
}Claude Desktop
{
"mcpServers": {
"sigrok-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SIGROK_CLI_PATH=<YOUR_SIGROK_CLI_PATH>",
"-e",
"SIGROK_TIMEOUT_SECONDS=<YOUR_SIGROK_TIMEOUT_SECONDS>",
"-e",
"SIGROK_WORKING_DIR=<YOUR_SIGROK_WORKING_DIR>",
"ghcr.io/kenosinc/sigrok-mcp-server:0.2.0"
],
"env": {
"SIGROK_CLI_PATH": "<YOUR_SIGROK_CLI_PATH>",
"SIGROK_TIMEOUT_SECONDS": "<YOUR_SIGROK_TIMEOUT_SECONDS>",
"SIGROK_WORKING_DIR": "<YOUR_SIGROK_WORKING_DIR>"
}
}
}
}Let your agent find its tools
Find servers like sigrok MCP Server from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.