Skip to main content
Glama
Sign In
Hachimeder

maxplus2-mcp

by Hachimeder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to maxplus2-mcp

No user-submitted related servers found.

    Related Servers

    • inoproshop

      x2124824695-stack
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local stdio-based MCP integration with InoProShop/CODESYS for project structure reading, POU editing with verified writes, compilation, task configuration, and persistent session recovery.
      2
      MIT

    • e-debug-bridge

      997375857
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI to read, reliably edit, compile, and observe a local E5.95 EasyLanguage IDE over MCP, including project snapshots, declarations, native listview preparation, support-library metadata, and fault/variable capture. It works without simulating keyboard or mouse input and without depending on AutoLinker.
      4
      MIT

    • Computer-Controller-Bridg

      Dobona
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients on Windows to control the local mouse, keyboard, and screen understanding via MCP stdio, allowing automated workflows like viewing the screen, locating elements, clicking, typing, and verifying results.
      1
      Apache 2.0

    • cad-studio

      jbrandonp
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients such as Claude Desktop, Cursor, and Copilot to connect over MCP STDIO to CAD/CAE/CAM tooling for natural-language parametric shape synthesis, CSG script generation, solid watertightness validation, error analysis, and autonomous correction.
      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.4/5.0

    Scored across 68 tools

    Disambiguation3/5

    Descriptions are unusually explicit about boundaries and cross-reference sibling tools ('use gdf_geometry for...', 'use netlist_export for...'), which helps. However the surface has large overlapping clusters — e.g. gdf_text_edit vs gdf_text_format_edit (both edit free root DOC text), gdf_graphics_edit vs gdf_edit vs gdf_construct, and scf_edit vs scf_stimulus_edit vs scf_structure_edit — where an agent can easily pick the wrong one.

    Naming Consistency3/5

    Everything is snake_case and grouped by predictable subsystem prefixes (gdf_, scf_, project_, desktop_, acf_, setacf_, maxplus2_, job_). But verb ordering is inconsistent: noun_verb forms (acf_read_pins, project_read_file, gdf_text_edit) coexist with verb_noun forms (list_projects, parse_tbl, simulate_and_verify, probe_executable), and many tools carry no prefix at all.

    Tool Count1/5

    68 tools is an extreme mismatch for a single server. Even a rich legacy-EDA workflow does not justify this many entry points, and the count forces agents to navigate many near-duplicate edit/inspect variants rather than a focused set.

    Completeness5/5

    The surface covers the full lifecycle: project create/clone/files/read/write/search/parse, ACF read/validate/repair, setacf plan/apply, compile/simulate plan/run, result parsing, GDF/SYM/SCF authoring and editing, netlist export, waveform analysis, job control, and desktop GUI automation. Almost no obvious functional gap remains for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources