motionworks-iec-mcp-server
Related Servers
Alternatives to motionworks-iec-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to read, understand, and write Yaskawa MotionWorks IEC 3 code by parsing PLCopen XML and Extended IEC 61131-2 exports and extracting the firmware motion library from the installed vendor help.28MIT
- 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
- AlicenseAqualityBmaintenanceEnables AI agents to parse Rockwell/Allen-Bradley L5X project exports and query PLC tags, UDTs, routines, AOIs, and I/O modules, including cross-reference search across logic to trace where a symbol is used. Ladder logic is returned as compact NeutralText with rung comments, keeping context windows small.12MIT
- FlicenseAqualityCmaintenanceLets AI agents and users analyze Mitsubishi MELSEC .gx3 projects directly, tracing coil conditions, checking device references, comparing program changes, and inspecting ladder logic without opening GX Works3.134-
- 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.-
- 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
TDQS
Scored across 28 tools
Descriptions are unusually thorough and cross-reference each other (e.g. get_type pointing to get_fb_signature), which aids selection. However there is real overlap: get_routines/get_pous and get_routine/get_pou are deliberate aliases, and get_types/get_type/get_udts/get_udt/get_fb_signature/list_fb_catalog/list_library_blocks form a dense cluster of type-and-block lookups with subtle boundaries.
Almost everything follows a snake_case verb_noun pattern (get_*, list_*, search_*, render_*, validate_*, open_/load_project). Minor deviation: singular listing tools use get_ for plurals (get_tags, get_types, get_pous, get_udts) while others use list_ (list_library_blocks, list_fb_catalog, list_languages), plus singular/plural alias pairs.
At 28 tools this is heavy, though the PLC-analysis domain genuinely spans projects, sources, POUs, tags, types, FBs, tasks, motion, I/O, search, conventions, validation and rendering. The count is inflated by two redundant alias pairs and overlapping type/block tools that could be consolidated.
The read/analysis surface is comprehensive (projects, POUs, tags, types, FBs, library, tasks, motion, I/O, search, conventions) and adds validation plus code/type rendering, so most workflows have no dead ends. The main gap is that rendering is export-shaped only, with no verified import/write path back into the project.