Skip to main content
Glama
sealablab

Moku MCP Server

by sealablab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Moku MCP Server

No user-submitted related servers found.

    Related Servers

    • Instrument MCP Server

      zeng-andrew
      A
      license
      C
      quality
      B
      maintenance
      Enables natural language control of test instruments like spectrum analyzers and power supplies via SCPI commands, with auto-discovery and multi-instrument session support.
      100
      1
      MIT

    • pico-mcp

      Schimmilab
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to control a PicoScope 5000A USB oscilloscope for signal generation, block capture, measurements, and frequency response sweeps.
      1
      MIT

    • InstrMCP

      caidish
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for quantum device physics laboratory instrumentation control, enabling LLMs to interact with physics instruments and measurement systems through QCodes and JupyterLab.
      38
      MIT

    • pickering-lxi-mcp

      testinsightconsulting
      A
      license
      B
      quality
      B
      maintenance
      Enables LLM agents to safely route signals through Pickering PXI/LXI switching by logical endpoint names, with connectivity-graph interlock enforcement and a built-in chassis simulator.
      18
      MIT

    • keyscope-mcp

      AnterCreeper
      A
      license
      Not graded
      quality
      D
      maintenance
      AI-native oscilloscope control. A pure-Python MCP service that lets LLM agents control Keysight EDUX1052G oscilloscopes via a compact DSL.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: discovery, connection, device info, configuration retrieval, slot listing, configuration deployment, disconnection, and routing setup. The descriptions make it easy to distinguish between tools like get_config (retrieve config) and push_config (deploy config), avoiding any ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, such as attach_moku, discover_mokus, get_config, and release_moku. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.

    Tool Count5/5

    With 8 tools, the server is well-scoped for managing Moku devices, covering essential operations like discovery, connection, configuration, and release. Each tool earns its place without feeling excessive or insufficient, aligning perfectly with the domain's needs.

    Completeness5/5

    The tool set provides complete lifecycle coverage for Moku device management, from discovery and attachment to configuration, monitoring, and release. There are no obvious gaps; all core operations are included, ensuring agents can handle typical workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources