logic-analyzer-mcp
logic-analyzer-mcp is an MCP server for controlling USB logic analyzers and capturing/decoding digital traces.
Discover, connect, disconnect, and inspect logic analyzer devices and backends.
Configure active channels, sample rate, and simulator patterns.
Set and get digital triggers by channel, pattern, mode, and level.
Capture single traces, previews, last capture, and export CSV/VCD/summary files.
Decode UART, I2C, and SPI signals, plus list/run available decoders.
Provide built-in help, discovery, status, quickstart, FAQ, and hardware guidance.
Run without hardware using the simulator, or with sigrok-supported hardware.
Enables verification of SPI/I2C signals on PCB designs created with KiCad, working in conjunction with a KiCad MCP server.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@logic-analyzer-mcp decode UART from D0 at 9600 baud"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
logic-analyzer-mcp
AI-driven USB logic analyzer control via FastMCP 3.2. Capture digital traces with sigrok or the built-in simulator, decode UART/I2C/SPI, and export VCD for PulseView.
How it runs
Mode | Hardware | When |
Simulator (default) | None | Development, CI, agent dry-runs |
sigrok | Hantek 6022BL (LA mode), DSLogic, FX2 clones | Production bench with sigrok-cli |
The MCP server does not bundle sigrok. Install PulseView or sigrok-cli separately, then connect your USB LA.
Related MCP server: oscilloscope-mcp
Hands-in / Hands-out
Direction | Artifacts | Notes |
Hands-in |
| Via |
Hands-out | Trace preview (downsampled JSON) |
|
Hands-out | CSV, VCD, JSON summary |
|
Hands-out | Protocol decode rows |
|
Fleet pipelines
Partner MCP | Workflow |
Mixed-signal bring-up (analog + digital) | |
Verify SPI/I2C after PCB bring-up | |
Debug FPGA/MCU buses |
Bench family
One bench, nine servers. bench-orchestrator-mcp conducts (mcu_bringup drives
its six wired peers); the rest are instruments:
Server | Role | Wired peer? |
Conductor — | — (it conducts) | |
Halt / inspect / flash the CPU | yes ( | |
Scope traces — signal integrity | yes ( | |
| Digital capture + UART/I2C/SPI decode | yes ( |
DMM — rails, continuity | yes ( | |
Bench PSU — target power | yes ( | |
AWG stimulus — clocks, reset, fault injection | yes ( | |
Bench vision — LEDs, 7-segment | family (not wired) | |
Spectrum — EMI around the target | family (not wired) |
Quick Start
Set-Location D:\Dev\repos\logic-analyzer-mcp
uv sync --extra dev
just webapp
# Open http://127.0.0.1:10989STDIO-only (Cursor MCP):
just serveDry-run without hardware:
la_device(operation="connect", device_id="sim-la-001")
la_capture(operation="single", sample_rate_hz=1000000, sample_count=4096)
la_decode(operation="uart", rx="D0")Cursor MCP config
Add to C:\Users\sandr\.cursor\mcp.json:
"logic-analyzer-mcp": {
"command": "C:/Users/sandr/.local/bin/uv.exe",
"args": [
"--directory",
"D:/Dev/repos/logic-analyzer-mcp",
"run",
"python",
"-m",
"logic_analyzer_mcp",
"--stdio"
],
"env": {
"FASTMCP_BANNER": "0",
"FASTMCP_UPDATE_CHECK": "0",
"PYTHONUNBUFFERED": "1",
"LOGIC_ANALYZER_MCP_BACKEND": "auto"
}
}Restart Cursor after editing mcp.json.
Tools
Tool | Operations |
| list, connect, disconnect, status, capabilities, backends |
| channels, sample_rate, get, simulator_pattern |
| set, get |
| single, preview, export_csv, export_vcd, export_summary, last |
| list, run, last, uart, i2c, spi |
| discover, tool_help, status, quickstart, faq, hardware_guide |
Webapp
Port | Role |
10985 | Backend (FastAPI + MCP |
10989 | Frontend (Vite React — dashboard, device, configure, trigger, trace, decode, logs) |
just webappNative App (Tauri)
A Tauri 2.0 wrapper (native/) packages the backend with PyInstaller into a single NSIS installer — one shortcut, embedded Python, no separate runtime.
pwsh -NoProfile -File native/build.ps1 # webapp → PyInstaller → Rust → NSIS
just cua-nsis-test # install → launch → verify → uninstallDocumentation
INSTALL.md — setup paths
docs/ARCHITECTURE.md — system design
docs/TOOLS.md — portmanteau reference
docs/HARDWARE.md — LA buying guide
docs/BACKENDS.md — sigrok + simulator
llms.txt — agent discovery index
License
MIT — see LICENSE.
Available Tools
6 toolsla_captureB
Acquire digital traces and export capture data.
Examples
la_capture(operation="single", sample_rate_hz=1000000, sample_count=4096)
la_capture(operation="export_vcd")
Inputs: operation (required), channels, filename, sample_count, +1 more.
la_configureB
Configure logic analyzer channels and sample rate.
Examples
la_configure(operation="channels", channels=["D0", "D1", "D2"])
la_configure(operation="sample_rate", sample_rate_hz=24000000)
Inputs: operation (required), pattern, channels, sample_rate_hz.
la_decodeARead-only
Decode captured digital traces with sigrok decoders or simulator stubs.
Examples
la_decode(operation="list")
la_decode(operation="uart", rx="D0")
la_decode(operation="i2c", sda="D0", scl="D1")
Inputs: operation (required), rx, tx, clk, +5 more.
la_deviceB
Discover, connect, and manage USB logic analyzer devices.
Return Format
{"success": bool, "operation": str, "data": {...}}
Examples
la_device(operation="list")
la_device(operation="connect", device_id="sim-la-001")
la_device(operation="status")
Inputs: operation (required), backend, device_id.
la_helpCRead-only
Help, discovery, and hardware guidance for logic-analyzer-mcp.
Inputs: operation (required), topic, tool_name.
la_triggerB
Configure digital trigger source and pattern.
Examples
la_trigger(operation="set", channel="D0", pattern="rising", mode="auto")
la_trigger(operation="get")
Inputs: operation (required), mode, level, channel, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct phase of the logic-analyzer workflow: device management, configuration, triggering, capture, decoding, and help. la_configure (channels/sample rate) and la_trigger (trigger patterns) could superficially overlap as 'configuration', but their descriptions clearly separate the concerns.
All six tools use a uniform la_ prefix followed by a single verb-like noun in snake_case (la_help, la_capture, la_configure, la_decode, la_device, la_trigger). The pattern is predictable with no mixing of conventions.
Six consolidated tools each covering a clear responsibility is well-scoped for a logic-analyzer server. Sub-operations are pushed into the operation parameter rather than expanding the tool count, keeping the surface tight.
The surface covers the full lifecycle: device discovery/connect, channel and rate configuration, trigger setup, capture with export (VCD), and sigrok decoding. Minor gaps exist (e.g., continuous/streaming capture or session save/load), but core workflows are complete with no dead ends.
Maintenance
Related MCP Connectors
Live browser debugging for AI assistants — DOM, console, network via MCP.
Design circuits, simulate and verify embedded firmware, and lay out PCBs with AI agents.
OCR, transcription, file extraction, and image generation for AI agents via MCP.
AI-native mock API server with MCP. Create REST/SOAP mocks from Claude, Cursor, or Windsurf.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to control Saleae Logic analyzers, capture and analyze digital/analog signals, and export data via MCP.MIT
- AlicenseAqualityBmaintenanceAI-driven USB oscilloscope control via FastMCP, enabling waveform capture, CSV export, and frequency measurements on PicoScope, Hantek, or a built-in simulator.68MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to capture digital waveforms from an ALIENTEK USB logic analyzer, run 208 sigrok protocol decoders with stacked chains (like I2C→SSD1306 or UART→Modbus), and analyze or write .atkdl waveform archives offline without the device attached.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to capture, decode, and analyze signals from logic analyzers and measurement devices via sigrok-cli, supporting I2C, SPI, UART, CAN, and 100+ protocols.15MIT