Skip to main content
Glama

Related Servers

Alternatives to stoneai MCP Server

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.
      2
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to discover, inspect, edit, rebuild, and save Schneider Electric RemoteConnect and SCADAPack x70 IEC logic projects, including program sections, hardware, variables, and Modbus configuration.
      63
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      This server enables AI agents to fully control STM32CubeIDE and STMicroelectronics hardware, including GUI automation, headless builds, flashing, GDB debugging, option bytes, serial telemetry, and CubeMX .ioc engineering.
      34
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents and compatible clients to query real-time editor language-server diagnostics, type/symbol information, and code navigation without waiting for slow tsc/eslint checks, plus workspace-aware operations such as finding references, renaming symbols, opening files, and executing editor commands.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents and AI IDEs to pull real-time LSP diagnostics, type/hover/signature information, and code navigation from a running editor, replacing slow tsc and eslint runs. Also supports workspace-wide symbol renaming, reference lookup with usage context, opening files, and listing open editor windows.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to access real-time language-server diagnostics, type/hover/signature information, code references, workspace-wide symbol renaming, and file opening through an editor bridge.
      MIT

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools target distinct resources/actions (doctor, create, state, build, symbols, connect, read). There is mild overlap: stone_files_add both writes a file and compiles while stone_build compiles, and stone_pou_generate also produces ST source; similarly stone_api_search vs stone_snippet are both reference lookups. Descriptions clarify the boundaries adequately.

    Naming Consistency4/5

    All tools share a 'stone_' snake_case prefix, making them clearly cohesive. However, the suffix pattern mixes noun-only labels (stone_doctor, stone_build, stone_symbols, stone_snippet) with verb_noun forms (stone_solution_create, stone_target_connect, stone_watch_read), a minor deviation.

    Tool Count5/5

    Eleven tools is well within the ideal 3-15 range. Each tool maps to a distinct step in the STone workflow (setup, create, build, inspect, generate, connect, monitor) and none feel redundant.

    Completeness3/5

    Core lifecycle is present (create solution, add files, build, inspect symbols, connect, read). But notable gaps exist: only stone_watch_read with no variable write, no target disconnect, and no file/project delete or update operations, which limits full PLC round-trip workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues