Your ETS project now understands plain language.
Tell your AI assistant what you need – MCP-Connector carries it out in your open ETS
project. It links ETS to AI assistants such as Claude through the open Model Context
Protocol (MCP). Instead of clicking through dialogs and lists, you describe the result
in your own words:
• "Create group addresses for switching and dimming the light in every ground-floor
room."
• "Assign every device on line 1.1 to its room."
• "Set the behaviour after bus voltage recovery to Off on all switch actuators
upstairs."
• "Which communication objects are not linked to any group address yet?"
• "Export the group addresses as CSV."
The AI reads and edits topology, buildings, trades, functions, group addresses,
devices, parameters and communication objects – and adds devices from the catalog.
You stay in control:
• Preview first: every change can be checked before it takes effect – if you like,
with the real verdict of ETS, while the project stays unchanged.
• One step back is enough: every change is a named entry in the ETS undo history and
can be undone there as a whole.
• Nothing half-written: the connector reads every change back and keeps it only if it
arrived exactly as requested.
• Reasons, not guesswork: when ETS refuses something, you learn why – and what to do
next.
• The AI knows the valid values of a parameter instead of guessing them.
Your project stays with you: the connector runs inside ETS and opens no network
connection of its own. You decide which AI sees your project data by choosing your
assistant.
Questions? We’re here to help.
Whether it’s setup, connecting your AI assistant, or a question in an ongoing project –
write to us at support@die-bildungsmanufaktur.de. We can help you with:
• installing the connector in ETS and connecting it to your AI assistant,
• questions about working with the connector in your project,
• error messages and unexpected behaviour,
• requests and ideas for future versions.
To help us respond quickly, please include your ETS version, the connector version and
the AI assistant you use. If something goes wrong, your assistant can also create a
diagnostic report: it is saved only locally on your computer and is never sent
automatically. You review it and decide for yourself whether to send it to us.
Your ETS project now answers questions.
Ask your AI assistant what is in your open ETS project – MCP-Connector Lite gets the
answer from ETS. It links ETS to AI assistants such as Claude through the open Model
Context Protocol (MCP). Instead of searching lists and opening dialogs, you ask in your
own words:
• "Which communication objects are not linked to any group address yet?"
• "Show every device on line 1.1 with its room."
• "What is the behaviour after bus voltage recovery on the switch actuators upstairs?"
• "Which values does this parameter accept at all?"
• "Export the group addresses as CSV."
The AI reads topology, buildings, trades, functions, group addresses, devices,
parameters, communication objects and the product data in the project.
This edition reads, and nothing else:
• Lite offers the reading tools only. Nothing in the project changes – no entry in the
undo history, no confirmation prompt, no interference with work in progress.
• The answers come from ETS itself, not from a copy kept beside it.
• The AI learns at the parameter itself which values it accepts – instead of guessing.
• When ETS refuses a query, you learn why – and what to do next.
• This is how you survey a project, check it before handover, document it and track
down faults.
Your project stays with you: the connector runs inside ETS and opens no network
connection of its own. You decide which AI sees your project data by choosing your
assistant.
Creating, changing and deleting inside the project – with preview, a named entry in the
ETS undo history and a read-back of every change – is offered by MCP-Connector
Professional.