Skip to main content
Glama
sandraschi

oscilloscope-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OSCILLOSCOPE_MCP_BACKENDNoSelects the oscilloscope backend: auto, simulator, picoscope, hantek.auto
OSCILLOSCOPE_MCP_CAPTURE_DIRNoDirectory path for exported CSV and JSON capture files. Defaults to current working directory if not set.

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

CapabilityDetails
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

NameDescription
scope_captureB

Acquire waveforms and export capture data.

Return Format

{"success": bool, "operation": str, "data": {...}}

Examples

  • scope_capture(operation="single", sample_rate_hz=100000, sample_count=4000)

  • scope_capture(operation="export_csv")

  • scope_capture(operation="preview")

scope_configureA

Configure oscilloscope channels and simulator signal profiles.

Return Format

{"success": bool, "operation": str, "data": {...}}

Examples

  • scope_configure(operation="channel", channel_id="A", range_v=2.0, coupling="dc")

  • scope_configure(operation="get")

  • scope_configure(operation="simulator_profile", waveform="square", frequency_hz=1000)

scope_deviceA

Discover, connect, and manage USB oscilloscope devices.

Consolidates device enumeration, session connection, backend selection, and health status.

Return Format

{"success": bool, "operation": str, "data": {...}}

Examples

  • scope_device(operation="list")

  • scope_device(operation="connect", device_id="sim-001")

  • scope_device(operation="status")

  • scope_device(operation="backends")

scope_helpB

Help, discovery, and hardware guidance for oscilloscope-mcp.

Return Format

{"success": bool, "operation": str, "data": {...}}

Examples

  • scope_help(operation="discover")

  • scope_help(operation="quickstart")

  • scope_help(operation="hardware_guide")

scope_measureA

Measure voltage and timing parameters from captured waveforms.

Uses the last capture by default. Operation 'fresh' performs a new capture first.

Return Format

{"success": bool, "operation": str, "data": {...}}

Examples

  • scope_measure(operation="all", channel_id="A")

  • scope_measure(operation="frequency", channel_id="A")

  • scope_measure(operation="fresh", sample_rate_hz=200000)

scope_triggerB

Configure and inspect oscilloscope trigger settings.

Return Format

{"success": bool, "operation": str, "data": {...}}

Examples

  • scope_trigger(operation="set", source_channel="A", threshold_v=0.5, mode="auto", edge="rising")

  • scope_trigger(operation="get")

Prompts

Interactive templates invoked by user choice

NameDescription
scope_bringup_guideGuide for oscilloscope bring-up and first capture.

Resources

Contextual data attached and managed by the client

NameDescription
scope_capabilities_resource
scope_quickstart_resource
scope_last_capture_resource
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a distinct purpose: capture, configure, device management, help, measure, and trigger. No overlapping functionality.

Naming Consistency5/5

All tools follow the same 'scope_' prefix with a clear verb, providing a predictable and consistent naming convention.

Tool Count5/5

Six tools cover the essential oscilloscope operations without being excessive or insufficient, fitting well within the expected range.

Completeness4/5

The tool set covers core oscilloscope functions (capture, measure, trigger, configure, device, help). Missing a dedicated waveform save/load feature, but this is a minor gap.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources