Delta PLC Agent
Related Servers
Alternatives to Delta PLC Agent
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to connect to Allen-Bradley, Siemens, and CODESYS PLC projects for discovering, asking questions about, analyzing, and proposing code changes, with access to live tag values and version exports under permission-scoped controls.-
- AlicenseBqualityBmaintenanceEnables 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.631MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI to operate STEP 7-Micro/WIN SMART via MCP, supporting offline STL/AWL analysis, project inspection, online PLC monitoring (snap7), and engine-injected operations like compile, download, upload, and symbol management through natural language.8-
- AlicenseNot gradedqualityBmaintenanceEnables 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.2MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI-powered PLC programming with natural language to ladder logic conversion, L5X and .ACD project generation, and semantic search through L5X files and documentation.36-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to generate and statically verify IEC 61131-3 Structured Text logic, mutate .csp/.cpj OLE2 project containers, trigger in-GUI Error Check compilation, manage HMI screens, and run deterministic OCS scan-cycle simulations and Modbus telemetry scaling against Cscape 10.2. All physical hardware and firmware-download paths are intercepted fail-closed, so commissioning must be performed manually by authorized field personnel.MIT
TDQS
Scored across 11 tools
Tools map to distinct lifecycle phases (probe, capabilities, target, workspace, adapter, evidence, workflow) and descriptions carefully delimit boundaries, e.g. workspace.create vs workspace.import and workflow.start vs workflow.run. Minor potential confusion remains between the create/import and start/run pairs, but the descriptions resolve it.
All 11 tools follow a strict namespace.verb pattern (environment.probe, workspace.create, workflow.run, adapter.invoke, etc.). The convention is applied uniformly with no style deviations.
11 tools is well within the ideal range and each earns its place, covering the full lifecycle from environment discovery through workflow execution. No redundant or filler tools are present.
The surface covers discovery, target resolution, workspace lifecycle, capability invocation, evidence reading, and workflow orchestration. Minor gaps exist: no workspace teardown/delete, no workflow cancel/abort, and no evidence listing, but these are workaroundable.