Developer · Local MCP server

sigrok MCP Server

Wraps sigrok-cli for signal analysis: capture data, decode protocols, and query instruments.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.KenosInc/sigrok-mcp-server
Version
0.2.0
Status
Active
Category
developer
Transport
stdio (local process)
Package
OCI image (Docker)
Published
2026-02-25
Updated
2026-02-25
Publisher
KenosInc (GitHub) · 2 servers with pages here
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/KenosInc) · how
Repository
github.com/KenosInc/sigrok-mcp-server
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
OCI image (Docker)ghcr.io/kenosinc/sigrok-mcp-server:0.2.0-stdioSIGROK_CLI_PATH, SIGROK_TIMEOUT_SECONDS, SIGROK_WORKING_DIR

How to connect sigrok MCP Server

sigrok MCP Server runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/kenosinc/sigrok-mcp-server:0.2.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e SIGROK_CLI_PATH -e SIGROK_TIMEOUT_SECONDS -e SIGROK_WORKING_DIR ghcr.io/kenosinc/sigrok-mcp-server:0.2.0. It reads these environment variables: SIGROK_CLI_PATH, SIGROK_TIMEOUT_SECONDS and SIGROK_WORKING_DIR; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "sigrok-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SIGROK_CLI_PATH",
        "-e",
        "SIGROK_TIMEOUT_SECONDS",
        "-e",
        "SIGROK_WORKING_DIR",
        "ghcr.io/kenosinc/sigrok-mcp-server:0.2.0"
      ],
      "env": {
        "SIGROK_CLI_PATH": "<value>",
        "SIGROK_TIMEOUT_SECONDS": "<value>",
        "SIGROK_WORKING_DIR": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More from KenosInc (GitHub)

All 2 →
ServerRunsEndpoint or package
Digilent WaveForms MCP ServerMCP server for Digilent WaveForms instruments (oscilloscope, AWG, logic analyzer).Local · stdioOCI image (Docker): ghcr.io/kenosinc/dwf-mcp-server:0.2.1

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Signadot MCP ServerConnect to Signadot to manage ephemeral environments and route traffic to local services.Local · stdioMCP Bundle (.mcpb): signadot/cli/releases/download/v1.9.0/signadot-c
Signal OraclePay-per-call change-intelligence feeds for AI agents over x402 (deps, security, regs, tariffs)Remote · HTTPLive check: ✓ handshakeoracles-production.up.railway.app
SignalintLocal stdio MCP server for cached, loop-aware JS/TypeScript diagnostics (Oxlint, tsc, Biome).Local · stdionpm: signalint-mcp
SigNoz MCP ServerSigNoz MCP server: access metrics, traces, logs, alerts, and dashboards via AI assistants.Local · stdioOCI image (Docker): docker.io/signoz/signoz-mcp-server:v0.15.0
Sigstore RekorSigstore Rekor - the public transparency log for software signatures.Remote · HTTPLive check: ✓ handshakegateway.pipeworx.io
sigtap Agent Tools13 paid x402 tools, USDC/Base. Free check: GET /preview<path>=200 sample. Copy-paste pay: /llms.txt.Remote · HTTPLive check: ✓ handshakesigtap-mcp.sigtap.workers.dev
Silentwatch MCPMCP server for cron silent-failure detection across crontab, systemd, and OpenClaw schedulers.Local · stdioPyPI: silentwatch-mcp
SilexLocal-first MCP server that reconstructs architecture, workflows and business rules from your code.Local · stdioPyPI: silex-archaeology