Skip to main content
Glama

Related Servers

Alternatives to BonengDriveMCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to automate CODESYS V3 PLC development, including project editing, builds, library and alarm management, online variable read/write/force operations, and CODESYS documentation search via MCP.
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Exposes ISO 14229 Unified Diagnostic Services as MCP tools, letting any MCP client run session control, DID reads and writes, DTC queries, routine control, security access and raw requests against a real ECU on a CAN bus or against a built-in simulator. A claim/release access model lets multiple clients safely share one device under test, with hardware-free simulation for offline test-plan development.
      11
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Exposes digital twin device data capabilities as MCP tools, allowing MCP clients to query device status, read real-time metrics, fetch time-series data, and check alerts. Includes a simulated PLC driver with a clean interface for connecting real devices via OPC-UA, Modbus, or gateway APIs.
      6
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI clients to scan for and connect to compatible BLE devices, control suction, vibration, linear, and rotary outputs, and safely stop or disconnect through MCP tools.
      22
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables driving any installed CODESYS 3.5 version (SP18–SP22) from a single MCP server, automatically selecting the right install from each project file's saved version. Exposes 127 tools covering project and POU authoring, compile, online/runtime control, devices and tasks, symbol configuration, multi-device projects, and a version plus git release pipeline.
      5
      MIT

    TDQS

    B3.4/5.0

    Scored across 54 tools

    Disambiguation3/5

    The set is broadly divisible into firmware, parameter, network/serial, oscilloscope, and motion clusters, but several clusters contain easily confused neighbors: firmware validation versus firmware upgrade, offline parameter sets versus live device parameter catalogs versus device snapshots, and multiple read-only probe tools. Descriptions help, but an agent must carefully distinguish preview/start/status/verify phases and offline versus online parameter state.

    Naming Consistency5/5

    Tool names consistently use snake_case with a predictable verb_noun or verb_object_qualifier pattern, such as get_parameter_set, create_device_parameter_snapshot, prepare_drive_speed_change, and execute_drive_position_move. The naming style is stable across all clusters even where the tools themselves are complex.

    Tool Count2/5

    With 54 tools, the server is far beyond the typical well-scoped range and exposes many specialized lifecycle stages across firmware, parameters, networking, serial I/O, oscilloscope capture, and motion control. Even if each tool has a legitimate niche, the surface is heavy enough to make discovery and correct selection difficult.

    Completeness4/5

    Coverage is extensive: discovery, selection, read-only probing, parameter catalog/search/read/write planning, snapshots, firmware build/validation/upgrade status, oscilloscope capture, and motion planning/execution/status/stop are all represented. Minor gaps remain, such as no snapshot restore, no batch parameter write execution, and no deletion operations for offline parameter sets or snapshots, but these are mostly stated limitations rather than fatal omissions.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data