te1000-mcp

MCP server for Beckhoff TwinCAT XAE / TE1000 Automation Interface.

This server uses the locally verified TwinCAT XAE Shell COM ProgID and calls it through 32-bit PowerShell, which matches Beckhoff's TE1000 requirements.

What It Can Do

• attach to a running XAE Shell instance

• open a solution in XAE Shell

• list and execute XAE/DTE commands

• inspect the active document and selected items

• read the current Error List when available

• clear the visible Error List

• inspect TwinCAT tree items

• list tree children

• export and import tree item XML with ProduceXml / ConsumeXml

• create, import, export, and delete TwinCAT child items

• link and unlink TwinCAT variables

• get and set the target NetId

• trigger PLC rescans and I/O box scans

• inspect NC tasks and axes

• save the active solution

• clean, build, and rebuild the active solution configuration

• PLC login, download, and logout through XAE commands

• activate configuration

• start or restart the TwinCAT runtime

Related MCP server: TwinCAT Validator MCP Server

v2 Tool Surface (2026-06-11)

The MCP surface was consolidated for agent-context efficiency: 36 tools -> 10, grouped by noun with action enums, compact outputs (raw XML, pruned compact JSON). The PowerShell bridge is unchanged and still answers the original fine-grained action names; index.js maps onto them (the original v1 tool surface is preserved in this repo's git history). Old tool names appearing later in this README map as: twincat_*_tree_item*/twincat_*_child -> tc_tree, twincat_link/unlink/ resolve_variable* -> tc_link, netid/errors/rescan/scan tools -> tc_system, nc_* -> nc, xae_solution_build -> xae_build, xae_execute_command -> xae_command, remaining xae_* -> xae.

• xae — status / open_solution / save_all / active_document / selected_items / error_list / clear_error_list / list_commands

• xae_build — clean / build / rebuild

• xae_command — raw DTE command (guarded)

• tc_tree — get / children / exists / get_xml / set_xml / create / delete / import / export / focus

• tc_link — link / unlink / resolve

• tc_system — get_netid / set_netid / errors / rescan_plc / scan_io_boxes

• nc — tasks / axes / axis

• plc_download — bootproject (default, headless ITcPlcProject deploy) or legacy command route

• twincat_activate_configuration, twincat_restart_runtime

plc_login/plc_logout were dropped from the surface (the 64-bit shell's DTE exposes no window automation, so they never worked here); use xae_command with OtherContextMenus.PlcProject.Login/.Logout on shells where it does. progId is no longer a tool parameter — set env TE1000_PROGID to override the default TcXaeShell.DTE.17.0.

High-impact tools are guarded:

• twincat_activate_configuration requires confirm="ALLOW_TWINCAT_ACTIVATE"

• twincat_restart_runtime requires confirm="ALLOW_TWINCAT_RESTART"

• xae_command requires confirm="ALLOW_XAE_COMMAND_EXEC"

Requirements

• Windows

• Beckhoff TwinCAT XAE Shell / XAE installed

• TE1000 Automation Interface available through TcXaeShell.DTE.15.0

• 32-bit Windows PowerShell present at: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe

• Node.js 20+

Install

git clone https://github.com/Edge-JB/tc1000-MCP-TC-4026.git
cd tc1000-MCP-TC-4026
npm install

Run

node index.js

The server speaks MCP over stdio, so it is normally launched by an MCP client (see below) rather than run by hand. Running it directly just prints te1000-mcp server running on stdio and waits for a client on stdin.

MCP Client Config Example

Point your MCP client at the absolute path of index.js in your clone:

{
  "mcpServers": {
    "te1000": {
      "command": "node",
      "args": [
        "C:\\path\\to\\tc1000-MCP-TC-4026\\index.js"
      ]
    }
  }
}

Tool Notes

twincat_set_tree_item_xml is the main path for IO edits. Typical workflow:

1. call twincat_get_tree_item_xml

2. edit the returned XML

3. call twincat_set_tree_item_xml

4. call xae_save_all

5. optionally call twincat_activate_configuration

Example TwinCAT tree path:

TIID^Device 1 (EtherCAT)^Term 1 (EK1100)

The exact path depends on the project tree in the active XAE session.

Useful discovery helpers:

• xae_list_commands

• xae_get_selected_items

• xae_get_error_list

• xae_clear_error_list

• twincat_test_item_path

• twincat_resolve_variable_path

• nc_list_tasks

• nc_list_axes

PLC Variable Paths

PLC struct variables are not always exposed to ITcSysManager::LinkVariables with IEC dot syntax all the way down. The top-level PLC variable can use dot syntax after the POU name, but child fields under a mapped struct may be XAE tree subitems and require ^.

Example:

TIPC^MyPlc^MyPlc Instance^PlcTask Inputs^MAIN.stSlot02_DI^In00

not:

TIPC^MyPlc^MyPlc Instance^PlcTask Inputs^MAIN.stSlot02_DI.In00

Use twincat_resolve_variable_path to test a candidate path and see the valid alternatives. twincat_link_variables also resolves these alternatives by default before linking.

Modal-dialog watchdog

A bridge call drives XAE through a synchronous DTE/COM call. If that call makes XAE raise a modal dialog (save-changes, "file changed externally", activate confirm, a license prompt, etc.), the COM call blocks inside XAE's modal message loop until a human clicks the dialog — so the MCP call, and the calling agent, hang indefinitely with no idea why.

powershell/dialog-watch.ps1 closes that gap. It runs as a short-lived process alongside every bridge call and, each poll, looks for an application-modal dialog owned by the XAE process (precise signal: a visible/enabled window whose owner window is disabled — docked tool windows and non-modal popups don't qualify). On finding one it either:

• auto-dismisses it — if the dialog matches a rule in powershell/dialog-allowlist.json, the watcher clicks that rule's button, releasing the blocked COM call so the operation completes normally; or

• reports it — for any dialog with no matching rule, index.js waits a short grace period (TE1000_DIALOG_GRACE_MS, default 4000 ms), then abandons the bridge call and returns an error containing the dialog's title, body text, and buttons, so the agent knows exactly what is blocking it. The dialog is left open on the machine for a human to clear; the operation result is indeterminate.

Detection is dialog-driven, not a wall-clock timeout, so long legitimate operations (a multi-minute build) are never killed just for taking a while.

Allowlist (powershell/dialog-allowlist.json)

Ships with rules: [] (report-only). Each rule: match (regex on the title, required), optional textMatch (regex on the body), and button (exact label to click). First matching rule wins; unmatched dialogs are reported, never clicked.

Live cell. Only add dialogs that are safe to auto-answer unattended. Never allowlist Activate Configuration / Run-mode / restart / download / safety prompts — those must stay human-confirmed. Prefer the non-destructive button.

Env toggles

Run dialog-watch.ps1 -Mode probe at any time to see the current dialog (if any) as JSON — useful for discovering the exact title/button strings for a new allowlist rule.

Build Support

Use xae_solution_build with:

• action: "clean"

• action: "build"

• action: "rebuild"

This runs through the Visual Studio SolutionBuild automation layer, which is the same side Beckhoff points to when PLC compilation is needed through automation.

PLC Session Commands

The server exposes these non-ADS PLC actions through XAE command execution:

• plc_login

• plc_download

• plc_logout

Current command mappings found in the live XAE shell on this machine:

• login: OtherContextMenus.PlcProject.Login

• download: PLC.Downloadnone

• logout: OtherContextMenus.PlcProject.Logout

These depend on XAE context. If a command is unavailable because the wrong node/editor is active, pass a different commandName override or change the active selection in XAE.

Tree Manipulation

The server exposes TwinCAT tree operations through ITcSmTreeItem:

• twincat_create_child

• twincat_delete_child

• twincat_import_child

• twincat_export_child

These are powerful but parent-type-specific. subType and import compatibility must match what the parent node accepts.

Targeting And Rescan

• twincat_get_target_netid

• twincat_set_target_netid

• twincat_rescan_plc_project

• twincat_scan_io_boxes

twincat_rescan_plc_project defaults to TIPC.

twincat_scan_io_boxes should target a device node such as:

TIID^Device 1 (EtherCAT)

NC Helpers

The server includes NC convenience tools:

• nc_list_tasks

• nc_list_axes

• nc_get_axis_info

A typical NC root pattern is:

TINC^NC-Task 1 SAF^Axes^Axis 1

TwinCAT quirk:

• some container/root nodes such as TIID and major EtherCAT boxes may return descendant collections rather than a single scalar item payload through COM

• leaf nodes and specific IO terminals are the safer targets for ProduceXml / ConsumeXml

• if a broad path returns too much data, step down one level and target the exact terminal, box, or variable node

• xae_focus_tree_item is best effort only; this environment exposes expand/focus behavior through the backing VS project item, but not a reliable true selection API

• xae_get_error_list uses typed EnvDTE80 interop loaded from the XAE PublicAssemblies folder because late-bound ToolWindows.ErrorList was returning null in this shell

• xae_clear_error_list clears the visible Visual Studio/XAE Error List through OtherContextMenus.ErrorList.Clear, which is different from TwinCAT.ClearErrorList

Safety

This server intentionally does not auto-activate or auto-restart TwinCAT.

If you expose it to an agent, keep the confirmation guards in place unless you are willing to accept live target changes.

The modal-dialog watchdog (above) is held to the same standard: its allowlist ships empty, and you should never add rules for Activate Configuration, Run-mode, restart, download, or safety prompts — those stay human-confirmed.

License

MIT.