openplc-engineering-mcp
openplc-engineering-mcp
Un pequeño servidor MCP en Python que expone operaciones de ingeniería orientadas a dominio y de solo lectura para OpenPLC.
El proyecto es una implementación experimental temprana. Su propósito actual es establecer un límite de integración mínimo y comprobable entre agentes compatibles con MCP y proyectos de OpenPLC Editor.
Arquitectura
MCP Host / LLM Agent
|
| MCP
v
OpenPLC Engineering MCP
|
v
OpenPLCEl servidor utiliza el SDK oficial de Model Context Protocol para Python y transporte stdio. No modifica OpenPLC ni expone herramientas genéricas de sistema de archivos o shell.
Related MCP server: gx3-mcp-server
Requisitos
Python 3.12+
Node.js/npm solo cuando se usa MCP Inspector (
mcp devusanpx)
Instalación
git clone https://github.com/industrix-com-br/openplc-engineering-mcp.git
cd openplc-engineering-mcp
uv syncEjecución
Inicie el servidor MCP stdio:
uv run openplc-engineering-mcpÁbralo con MCP Inspector:
uv run mcp dev src/openplc_engineering_mcp/server.py --with-editable .Pruebas
uv run pytestLas pruebas usan la interfaz Client(mcp) en memoria del SDK oficial en lugar de llamar directamente a las funciones de herramienta.
Herramientas actuales
get_server_info— informa las capacidades actuales del servidor.get_project_structure— devuelve la estructura relevante de un proyecto de OpenPLC Editor.list_pous— lista programas, bloques de función y funciones usando el diseño actual del proyecto de OpenPLC Editor.
La inspección de proyectos de OpenPLC sigue el diseño actual del Editor: project.json en la raíz del proyecto, POUs debajo de pous/programs, pous/function-blocks y pous/functions, además de las ubicaciones relacionadas de dispositivos y tipos de datos utilizadas por el Editor.
Alcance
Esta versión es intencionalmente de solo lectura y experimental. No incluye modificación de proyectos, compilación, despliegue, control en tiempo de ejecución, forzado de variables, autenticación, transporte HTTP ni acceso sin restricciones a shell/sistema de archivos. Esas capacidades deberían agregarse solo cuando requisitos concretos lo justifiquen.
Available Tools
3 toolsget_project_structureBRead-onlyIdempotent
Return the relevant file structure of an OpenPLC Editor project.
Inputs: project_path (required). Returns: name, path, type, files
get_server_infoARead-onlyIdempotent
Return basic information about this experimental OpenPLC MCP server.
Inputs: no named parameters. Returns: object
list_pousBRead-onlyIdempotent
List the programs, function blocks, and functions in an OpenPLC project.
Inputs: project_path (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
get_server_info is clearly distinct as server metadata. get_project_structure and list_pous overlap somewhat since a file structure could include POUs, but the descriptions separate file layout from logical POU listings.
All tool names follow a verb_noun pattern with get_ and list_ prefixes. The mix of get and list is a minor style inconsistency, but the pattern is still predictable and readable.
Three tools is a small but reasonable surface for an experimental read-only server. Each tool serves a distinct purpose, though the inclusion of a generic server_info tool makes the set feel slightly thin.
The server only provides inspection capabilities: server info, project structure, and POU listing. There are no operations for opening, editing, compiling, validating, or managing POU details, which are significant gaps for an engineering-focused server.
Maintenance
Related MCP Connectors
Search and inspect source-pinned agent skills, plugins and tools through a free public MCP.
Read-only MCP server exposing a user ORANO library to their own AI agent.
Read-only discovery of ChatGXT's integration catalog and public MCP capabilities.
Read-only MCP server for the Durable Agent Directory: search and compare agent-infrastructure tools.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI agents to read and understand local Mendix project structure and logic by connecting directly to the .mpr file via MCP. Allows querying microflows, entities, attributes, and modules in read-only mode without requiring cloud access.41ISC
- FlicenseAqualityBmaintenanceProvides read-only analysis of Mitsubishi GX Works3 PLC projects via MCP, enabling device tracing, cross-referencing, ladder inspection, linting, and report generation without modifying source projects.15101 PyPI10-
- FlicenseNot gradedqualityDmaintenanceEnables MCP agents to inspect deployment knowledge extracted from a repository, covering workflows, services, deployments, and images.-
- FlicenseDqualityBmaintenanceProvides read-only, structured access to Yasin ecosystem information (project registry, documentation, GitHub state, diagnostics) through the MCP protocol, enabling AI agents to query without direct repository access.223-