
edge-jb/twincat-xae-mcp
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
MCP server for Beckhoff TwinCAT 3 (TE1000 / XAE Automation Interface) — drive the System Manager tree, PLC authoring, IO/EtherCAT, linking, builds, and deployment from an AI agent.
개요
A Model Context Protocol server for engineering automation — drive the from an AI agent or any MCP client. te1000-mcp exposes the TwinCAT XAE engineering surface — the System Manager tree, PLC project authoring, IO/EtherCAT configuration, variable linking, builds, and runtime deployment — as a compact set of MCP tools. It talks to a through the TE1000 Automation Interface (COM/DTE), so an agent can configure and build a TwinCAT project the same way an engineer would in the GUI. A Node MCP front (index.js) owns the MCP protocol, tool schemas, and confirmation guards; the COM/DTE work runs in a (Te1000Daemon.exe) that the front talks to over a Windows named pipe. The daemon is the sole backend. See How it works. This server drives a and can activate or download to a . Every action that touches the target runtime (activate, restart, download, deletes, licensing) is and off by default. See Safety & guards.
README
원문 README의 일부입니다. 원문 보기.
te1000-mcp
A Model Context Protocol server for Beckhoff TwinCAT 3 engineering automation — drive the TE1000 / XAE Automation Interface from an AI agent or any MCP client.
te1000-mcp exposes the TwinCAT XAE engineering surface — the System Manager tree,
PLC project authoring, IO/EtherCAT configuration, variable linking, builds, and
runtime deployment — as a compact set of MCP tools. It talks to a running XAE Shell
through the TE1000 Automation Interface (COM/DTE), so an agent can configure and build
a TwinCAT project the same way an engineer would in the GUI.
A Node MCP front (index.js) owns the MCP protocol, tool schemas, and confirmation
guards; the COM/DTE work runs in a persistent native C#/.NET daemon
(Te1000Daemon.exe) that the front talks to over a Windows named pipe. The daemon is
the sole backend. See How it works.
[!IMPORTANT] This server drives a real engineering tool and can activate or download to a TwinCAT runtime. Every action that touches the target runtime (activate, restart, download, deletes, licensing) is confirmation-gated and off by default. See Safety & guards.
Contents
- Highlights
- How it works
- Requirements
- Install
- Build the daemon
- Configure your MCP client
- Environment variables
- Quickstart
- Tool reference
- Safety & guards
- Reliability: dialog watchdog & PLC session control
- Troubleshooting
- Examples
- Documentation
- Contributing
- License
Highlights
- 25 noun-grouped tools covering the automatable TE1000 surface — tree, IO/EtherCAT, linking, PLC project & POU authoring, libraries, tasks, mapping, routes, fieldbuses, TcCOM, C++, measurement/scope, licensing, and variants.
- Batch-first — every multi-item operation has a
*_batchform that runs N operations
설치
This server does not publish a one-line install command.
Open the repository installation guide MCP 초보자라면? mcpskill.org 가이드부터 시작하세요 →설정
{
"mcpServers": {
"te1000": {
"command": "node",
"args": ["C:\\path\\to\\TwinCAT-XAE-MCP\\index.js"]
}
}
}