Skip to main content
Glama
Disectron

twincat-mcp

by Disectron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to twincat-mcp

No user-submitted related servers found.

    Related Servers

    • Beckhoff PLC MCP Server

      malcolm-mill
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables read-only access to Beckhoff TwinCAT PLCs via ADS, allowing queries of device info, symbols, variables, and EtherCAT diagnostics through natural language.
      8
      MIT

    • te1000-mcp

      Edge-JB
      A
      license
      B
      quality
      A
      maintenance
      MCP server for Beckhoff TwinCAT XAE / TE1000 Automation Interface, enabling control of XAE Shell, TwinCAT tree manipulation, PLC operations, and build actions via natural language.
      25
      15
      MIT

    • TwinCAT Validator MCP Server

      agenticcontrolio
      A
      license
      B
      quality
      F
      maintenance
      An MCP server for validating, auto-fixing, and scaffolding TwinCAT 3 XML files using deterministic code quality tools and IEC 61131-3 OOP checks. It enables AI assistants to perform structural validation, apply safe fixes, and generate canonical code skeletons for industrial automation projects.
      16
      37
      MIT

    • codesys-mcp-server

      NPavii
      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

    • tiacommander-mcp

      a4webdev
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that connects AI assistants to Siemens TIA Portal via the Openness API. AI-assisted PLC programming, project management, hardware configuration, cross-reference analysis, and deployment. 19 tools, 230 actions.
      46
      -
    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

    C2.9/5.0

    Scored across 139 tools

    Disambiguation3/5

    Tools are grouped into coherent families (ads_*, rec_*, proj_*, xae_*) and descriptions are unusually detailed, but multiple overlapping variants exist — ads_read vs ads_read_many vs ads_dump vs ads_leaves, several write paths, several recording/test entry points — so an agent must carefully read descriptions to avoid misselection.

    Naming Consistency4/5

    Names consistently use snake_case with subsystem prefixes (ads_, proj_, xae_, rec_, exp_, infosys_), and most operations include a verb. Minor deviations are noun-only/stateful names (ads_status, proj_interface, xae_plc) and the workflow-layer wf_ prefix mixed with subsystem naming, but the pattern remains readable and predictable.

    Tool Count1/5

    139 tools is far beyond the 3–15 well-scoped range and well past the 25+ 'too many' threshold. Even for the broad TwinCAT domain, the set is a kitchen sink with layered and overlapping capabilities, imposing severe selection overhead on an agent.

    Completeness4/5

    Coverage is extensive across the TwinCAT lifecycle: project indexing, code get/set, build/deploy/activate, runtime ADS read/write, recording, experiments, HMI, Infosys docs, IPC, safety and audit. Some minor lifecycle gaps remain (e.g. explicit experiment deletion, HMI editing), but there are few obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources