F
licenseNot graded
qualityD
maintenanceEnables 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
-
studio5000-mcp-server
by KonnectSuite
Related Servers
Alternatives to studio5000-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceConverts natural language specifications into working ladder logic and complete Studio 5000 projects, enabling AI-powered PLC programming with L5X and .ACD file generation, semantic search, and documentation access.-
- AlicenseAqualityBmaintenanceEnables AI agents to parse Yaskawa MotionWorks IEC 3 project exports and query POUs, variables, data types, tasks, I/O and motion configuration across multiple export formats. It also decompiles the installed firmware library help to expose motion function-block signatures, parameters and documentation.28MIT
- 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.-
- 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
- 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-
TDQS
A3.5/5.0
Scored across 12 tools
Disambiguation4/5
Most tools have clearly distinct purposes: list/get pairs for tags, UDTs, AOIs, and routines are well-differentiated, plus search_logic and list_modules cover unique targets. Minor overlap exists because get_udt with an empty name returns all UDTs, duplicating get_udts (and similarly get_aoi vs get_aois), but the boundaries are still understandable.
Naming Consistency4/5
Nearly all tools follow a predictable verb_noun pattern (get_tags, get_routine, get_aoi, search_logic, load_project). Slight inconsistency in using both get_* and list_* for listing operations (get_udts vs list_modules), and 'ping' is an outlier, but overall it is readable and consistent.
Tool Count5/5
At 12 tools, the surface is well-scoped for a read-only L5X analysis server, with each tool earning its place. No redundant or trivial tools beyond the standard ping health check.
Completeness4/5
The read/query surface is thorough: project summary, tags, UDTs, AOIs, routines, I/O modules, and cross-routine search all have coverage. Minor gaps include no direct program-list tool (programs are only inferred via get_routines) and no export/reporting operation, but core analysis workflows are fully served.
Maintenance
ActivityStale
ResponsivenessNo issues