Skip to main content
Glama
BrianDavidCouch

daqmx-mcp

Related Servers

Alternatives to daqmx-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for interacting with NI DAQ hardware, supporting analog/digital I/O and waveform acquisition, with safety features and simulation mode.
      8
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that gives Claude (or any MCP-compatible AI host) read access to industrial sensor data and safety-gated control over motors and actuators.
      6
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for operating, recording, and analyzing serial-connected measurement instruments and circuits via AI agents. Includes a built-in mock device so all features can be tested without physical hardware.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for seamless integration with peripheral devices connected to your computer. Control, monitor, and manage hardware devices through a unified API.
      5
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A local-first, read-only MCP server for vehicle diagnostics that exposes structured OBD-II tools for reading PIDs, DTCs, and ECU snapshots without raw protocol access.
      7
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for reading and controlling an OWON SPE6103 programmable DC power supply over USB serial, with safety checks and verified SCPI commands.
      MIT

    TDQS

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool targets a distinct resource or action: device discovery, server status, channel listing, self-test, analog input, digital input, recording, and error explanation. The two analog voltage tools are differentiated by output (in-memory statistics vs. file creation), so no agent confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_devices, get_device_details, read_digital_inputs). Even compound verbs like self_test_device and record_analog_voltage adhere to the same pattern, making the API predictable.

    Tool Count5/5

    With 9 tools, the server is well-scoped for a DAQmx interface, covering device management, input operations, recording, and diagnostics. The count is neither sparse nor bloated, and each tool earns its place.

    Completeness4/5

    Core workflows are covered: device discovery, channel enumeration, analog/digital input, recording to file, self-test, and error handling. However, analog/digital output and continuous acquisition are absent, which may be intentional for safety but represents a notable gap for a DAQmx server.

    Maintenance

    ActivityStale
    ResponsivenessNo issues