logic-analyzer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGIC_ANALYZER_MCP_BACKEND | No | Backend mode: 'auto', 'simulator', or 'sigrok'. | auto |
| LOGIC_ANALYZER_MCP_CAPTURE_DIR | No | Directory where capture exports (VCD, CSV) are saved. | . |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| la_captureB | Acquire digital traces and export capture data. Examples
|
| la_configureB | Configure logic analyzer channels and sample rate. Examples
|
| la_decodeA | Decode captured digital traces with sigrok decoders or simulator stubs. Examples
|
| la_deviceB | Discover, connect, and manage USB logic analyzer devices. Return Format{"success": bool, "operation": str, "data": {...}} Examples
|
| la_helpC | Help, discovery, and hardware guidance for logic-analyzer-mcp. |
| la_triggerB | Configure digital trigger source and pattern. Examples
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| la_bringup_guide | Guide for logic analyzer bring-up and protocol decode. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| la_capabilities_resource | |
| la_quickstart_resource | |
| la_last_capture_resource |
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.