Related Servers

Each tool targets a distinct TwinCAT subsystem or lifecycle stage: PLC authoring (plc_pou) vs project lifecycle (plc_project) vs deployment (plc_download) vs online session (plc_session); EtherCAT (tc_ethercat) vs non-EtherCAT fieldbus (tc_fieldbus) vs generic tree ops (tc_tree); individual links (tc_link) vs project-wide mapping (tc_mapping). Overlapping boundaries are explicitly negotiated in the descriptions themselves — tc_tree directs EtherCAT creation to tc_ethercat, tc_fieldbus excludes EtherCAT, and the twincat_activate/restart/plc_download trio is clearly separated as a pipeline. Even the potentially confusable pairs (xae vs xae_command, tc_task vs tc_module) are sharply differentiated by scope.

Snake_case is used throughout with recognizable subsystem prefixes: tc_* for System Manager domains, plc_* for PLC engineering, twincat_* for lifecycle actions, xae_* for IDE shell. Internal action names follow a consistent verb_noun pattern (create_batch, set_xml, get_decl, link, unlink). Deviations exist: bare 'nc' breaks the prefix convention, 'xae' sits alongside 'xae_build' and 'xae_command' at uneven granularity, and tool suffixes mix nouns (tc_system, tc_ethercat) with verbs (plc_download, xae_build).

At exactly 25 tools, the server sits at the top of the heavy range. However, the domain is genuinely enormous — full TwinCAT XAE engineering covering IDE shell, PLC authoring/lifecycle, fieldbus, runtime tasks, TcCOM modules, linking, licensing, C++, measurement, and variants — and each tool maps to a major subsystem rather than a single operation. Some tools are thin (nc exposes only three read actions; tc_license is minimal) and could arguably have been folded into tc_task or tc_tree, but the overall decomposition is defensible given the breadth.

The surface covers the full engineering workflow: build, activate configuration, download boot project, restart runtime, online session control, PLC object CRUD with batch and surgical operations, EtherCAT and non-EtherCAT fieldbus creation, variable linking and bulk mapping, tasks, TcCOM modules, C++ projects, libraries, routes, variants, and licensing. The gaps are mostly deliberate and documented: graphical POU bodies are read-only (diagnostic only), solution creation from scratch is absent (only open_solution exists), measurement data export is explicitly omitted as unverified, and safety (TISC) is intentionally out of scope. Agents can work around these, but a fresh-solution workflow and graphical PLC editing would require external tooling.