Sigmatek LASAL MCP Server
An MCP server that lets AI agents automate the Sigmatek LASAL suite — compile, deploy to PLC/HMI hardware or a local LARS simulation, control live PLC values, and drive CLASS 2, VISUDesigner and LASAL SCREEN engines.
Project setup & status: select a project per agent session (
select_project), inspect classes/networks/objects (inspect_project), check engines/processes/stations/HMI health (lasal_status).Build & deploy: compile or download CLASS 2 projects (
build_project), full pipeline (deploy_all), multi-station MachineManager deploy via.lutc(deploy_solution), bootdisk/update-stick creation (create_class2_bootdisk).PLC control: start/stop/query runtime (
control_plc), read/write live channel values (plc_values), tracing, file transfer, code analysis, OS download, backups (plc_diagnostics).Local simulation (no hardware): per-station LARS workspaces, one-call
simulateloop, port probing, screen screenshots, target switching/restore (lars_runtime).CLASS 2 automation: ordered batch operations for networks, objects, connections, tasks, compiler version, copy/replace/import, plus file-level class creation/registration/cleanup (
apply_project_changes), and an arbitrary Python 2.7 batch escape hatch (run_class2_script).Class source & GUID handling: latin1-safe read/write of
.st/.hby class name (read_class_source), duplicate GUID resolution and CRC-32@CT_hash generation (validate_guids).VISUDesigner: text lists, schemes, media, code modules, alarms, languages, datapoint properties, publish and HMI download (
visu_project).LASAL SCREEN (LSE): inventory, create, compile, download, merge/fuse, XML text round-trips, variable import, translations, bulk theming, settings (
lse_project).HMI simulation: start/stop local DataService web runtime and get a testable URL (
hmi_runtime).IDE & connection management: open/close CLASS 2, VISUDesigner and LSE editors; update station IP/port/SSL in
.lss(set_target_ip).Long-running work & resources: background jobs with
jobId+check_job_status; MCP resources for the file-format guide, project status, stations and class sources.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Sigmatek LASAL MCP Server Compile and download the PLC project to the target hardware."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Sigmatek LASAL MCP Server
A Model Context Protocol (MCP) server for automating the Sigmatek LASAL software suite. It gives AI coding assistants (Claude, Gemini, Cursor, etc.) the ability to compile, deploy to hardware, control PLCs, read/write live values, run HMI simulations, and validate project GUIDs — while the agent edits project files directly.
Warning: This is NOT an official Sigmatek product. This project is in active development — bugs and unpredictable behavior are likely. Do not use on production projects without backups or version control.
Design Philosophy
The MCP only exposes tools for operations that require an external engine or hardware — compiling, deploying, PLC control, LARS soft-runtime simulations — plus the class/manifest operations whose generated formats and caches make raw file edits error-prone (creating a class, registering project files, latin1-safe class source access, resolving GUID collisions). For everything else (reading/editing .lcp, .lcn, .lss, .lvp, dashboard JSON), the AI agent works with the files directly using its native file tools. This keeps the tool set small, reliable, and focused.
Related MCP server: smart200-mcp
Features
Build & Deploy: Compile CLASS 2 projects, download to PLC, full deploy pipelines (
build_project,deploy_all), bootdisk/update-stick creation (plain or Update-Tool flavor with Autoexec, LasalOS image, VISU publish folder;create_class2_bootdisk).Multi-Station Deploy: MachineManager
.lutcorchestration — CLASS 2, LASAL SCREEN and VISUDesigner downloads, OS updates, file transfer, run/boot, channel writes, CLI commands (deploy_solution), with the per-run MachineManager log returned for diagnosis.Background Jobs:
build_project,deploy_all,deploy_solutionandlse_projectacceptasync: trueand return ajobId— poll withcheck_job_status(useful for clients with request timeouts).Headless Hardening: modal engine dialogs (error boxes, crash reporters, WerFault) are auto-dismissed while script runs execute — their text is captured into the tool result instead of hanging the run until someone clicks OK (
LASAL_MCP_DIALOG_WATCHER=0disables).PLC Control: Start/stop PLC runtime, read/write live channel values, query state (
control_plc,plc_values).Local Simulation (LARS): Run one LASAL program per LARS instance — one workspace per station (PLC + HMI) so both run simultaneously on separate ports (the MCP probes the port each instance actually serves). Point stations at the local runtime with a single call, compile/download/start/read values exactly like a real PLC, and browse the HMI via DataService. LARS also renders LASAL SCREEN projects locally, with window screenshots for visual verification. No hardware needed (
lars_runtime).CLASS 2 Batch Engine: Create/delete networks, add/remove objects, manage connections, configure tasks — operations that require the CLASS 2 scripting engine (
apply_project_changes,run_class2_script).GUID & CRC-32 Validation: Auto-resolve duplicate GUID collisions across classes/MaeExp.txt and compute exact IEEE 802.3 CRC-32 hashes for
@CT_tables (validate_guids).VISUDesigner Engine: Sync datapoints, manage text lists/schemes/media, publish, download to HMI (
visu_project).LASAL SCREEN (LSE) Engine: Drive classic panel HMI
.lprprojects via the LASALScreen COM automation — inventory, compile, download, merge/fuse, text-list translation edits, variable import from CLASS 2, bulk theming, settings (lse_project).HMI Simulation: Local web runtime via LasalVISUDataService returning accessible HTTP URLs for browser inspection or external Playwright MCP testing (
hmi_runtime).PLC Diagnostics: Tracing, file transfer, static code analysis (
plc_diagnostics).MCP Resources: Built-in resources for file documentation (
lasal://guide), live project status (lasal://project/status), active stations (lasal://stations), and class sources (lasal://classes/{className}).Autocompletions: Context-aware MCP completions for class names and station names.
Prerequisites
Windows OS (Sigmatek LASAL suite runs exclusively on Windows).
Node.js v18 or higher.
Sigmatek LASAL Suite:
LASAL CLASS 2 (PLC engineering).
VISUDesigner (web HMI design).
LASAL SCREEN (LSE, classic panel HMI design — required for
lse_project).MachineManager (optional — required for
deploy_solution).
Quick Start (with npx)
No repository clone or build required — configure your favorite MCP client to run directly via npx:
Claude Desktop
Add to %APPDATA%\Claude\claude_desktop_config.json:
{
"mcpServers": {
"lasal-mcp": {
"command": "npx",
"args": ["-y", "lasal-mcp"]
}
}
}Cursor
Add to your project's .cursor/mcp.json (or global Cursor MCP settings):
{
"mcpServers": {
"lasal-mcp": {
"command": "npx",
"args": ["-y", "lasal-mcp"]
}
}
}Claude Code
Run:
claude mcp add lasal-mcp npx -y lasal-mcpLocal Installation & Setup (for Developers)
git clone https://github.com/Svel26/Lasal-MCP.git
cd Lasal-MCP
npm install
npm run buildWhen running from a local clone, point your MCP client to:
{
"mcpServers": {
"lasal-mcp": {
"command": "node",
"args": ["C:/path/to/Lasal-MCP/dist/server.js"]
}
}
}Configuration
Environment Variables
Variable | Default | Purpose |
|
| CLASS 2 IDE path |
|
| VISUDesigner path |
|
| LASAL SCREEN (LSE) editor / COM automation server path |
|
| MachineManager path |
| auto-discovered (latest version) | DataService path |
|
| Compile timeout (ms) |
|
| Download timeout (ms) |
|
| Visu operation timeout (ms) |
|
| Script execution timeout (ms) |
|
| LASAL SCREEN operation timeout (ms) |
|
| MachineManager update timeout (ms) |
|
| Auto-dismiss modal engine dialogs during script runs and report their text. Set to |
|
| LARS runtime path |
|
| LARS workspace config file |
|
| Local HMI runtime directory |
|
| Hours before temp files are cleaned |
|
| Override the MCP state file (unit tests use it to stay off live state) |
| unset | Pin this MCP server process to one project. Overrides |
|
| Set to |
Running several agents at once
Every MCP server process has its own project selection. select_project in
one agent session no longer redirects another session's next tool call — the
shared state file only keeps a "last used" hint, and a fresh process inherits it
only when the process that wrote it has exited.
What is still machine-wide, and therefore coordinated:
Engine lock — compile/download/visu/LSE operations take a cross-process lock, so two agents queue instead of driving
Lasal2.exesimultaneously.CLASS 2 / VISUDesigner ownership — before an engine operation closes an IDE, each running instance is matched to its
.lcp/.lvpfrom the process command line. Instances belonging to another project are left running; engine operations report the conflict instead of destroying another agent's unsaved work.manage_class2/manage_visudesigneracceptforce: trueto override.State writes —
lasal-state.jsonis written under a lock via temp-file + rename, and handlers merge their changes into the current file instead of overwriting a stale snapshot.
lasal_status reports agents (live sessions and their projects) and class2
(instances owned by this project vs. other projects).
Available Tools
Engine & Hardware Tools (MCP)
Tool | Description |
| Set this agent session's project root directory (per-process; other agents keep theirs). |
| Check project, stations, engines, processes, HMI health. |
| Poll background jobs started with |
| Read-only class/network/object inventory (channels, tasks) from the manifest + class sources. |
| Scan a station project for duplicate GUID collisions and uninitialized |
| Read or write a class |
| Update a station's target IP/port/SSL in its |
| Open or close the CLASS 2 IDE. |
| Open or close VISUDesigner. |
| Open or close the LASAL SCREEN (LSE) editor. |
| Compile or download to PLC (supports |
| Create a CLASS 2 bootdisk / update stick (plain or Update-Tool flavor with Autoexec, OS image, VISU publish folder). |
| Start, stop, or query PLC runtime state. |
| Read/write live channel values on a running PLC. |
| Local LARS simulation: list/setup workspaces per station (wires CLASS 2 + LASAL SCREEN projects), start/stop, simulate (one-call loop: ARM→PC switch, compile, start, download), screenshot of the rendered screen, point stations at the probed effective port ( |
| Batch engine operations (networks, objects, connections, tasks, compiler version, compile/download) and file-level class operations: |
| Escape hatch: run arbitrary Python 2.7 |
| VISUDesigner engine operations (text lists, schemes, media, publish, download). |
| LASAL SCREEN engine operations via COM automation: info, compile, download, merge/fuse, XML text export/import, CLASS 2 variable import, text-list translations, bulk button/softkey theming, settings, images. |
| Start/stop local HMI web simulation (DataService) and return accessible URL. |
| Tracing (DataAnalyzer), file transfer on the control, code analysis (project or single file), OS download, RAM-image clear, project-on-PLC backup, connection-file download. |
| Full pipeline: compile → download → start PLC → compile LASAL SCREEN → optional SCREEN download → sync visu → start HMI. |
| Multi-station MachineManager deploy via generated |
MCP Resources
URI | Description |
| Comprehensive guide on LASAL file formats, ST structure, and runtime JS API. |
| Dynamic JSON resource reporting selected project, discovered stations, HMI runtime status, and LARS instances. |
| Live list of stations in the active solution and their target connections. |
| Direct read access to Structured Text ( |
Direct File Editing (no MCP needed)
The agent edits these files directly with its native file tools:
File | Format | Encoding | What it contains |
| XML | latin1 | Solution — lists all stations |
| XML | latin1 | Station settings — target IP, project references |
| XML | latin1 | CLASS 2 project manifest — class and network file paths |
| Generated declaration + ST | latin1 | Class source — |
| XML | latin1 | Network definitions — objects, connections, init values |
| Mixed | utf-8 | VISUDesigner project manifest |
| Binary | mixed | LASAL SCREEN project — never edit directly; drive via |
| XML | latin1 | LASAL SCREEN online/download target (updated by |
Dashboard JSON | JSON | utf-8 | HMI dashboards, windows, controls, property bindings |
See the built-in lasal://guide resource for detailed file format documentation.
Development
npm run dev # Watch mode
npm test # Run unit tests (Vitest)
npm run test:lab # Integration tests against the local LASAL installation (creates fresh projects)
npm run test:watch # Tests in watch mode
npm run lint # ESLint
npm run format # Prettier
npm run inspector # MCP Inspector for interactive debugging
npm run start:catalog -- --profile visu # Action-catalog preview (see docs/CATALOG_PREVIEW.md)
npm run docs:actions # Regenerate the action reference (docs/ACTIONS.md)Action catalog preview
The action catalog is available as a separate, opt-in entrypoint. It exposes
lasal_find_action / lasal_execute_action over a local catalog of 90 actions
covering CLASS 2, VISUDesigner, LASAL SCREEN, LARS and shared project actions.
It does not replace the existing tool set yet.
npm run build
npm run start:catalog -- --profile auto --project "C:\Projects\MySolution"Dedicated bins are also available:
npm run start:class2
npm run start:visu
npm run start:screen
npm run start:lars
npm run start:solutionGenerate an MCP client config for a project:
npm run init -- --project "C:\Projects\MySolution"
npm run init -- --project "C:\Projects\MySolution" --write .mcp.jsonSee docs/CATALOG_PREVIEW.md for usage,
docs/ACTIONS.md for the generated action reference,
docs/LARS_COMPATIBILITY.md for the LARS build
matrix, and docs/IMPLEMENTATION_PLAN.md for
the delivery plan and current status.
Simulating without hardware (LARS)
LARS (LASAL Runtime System) runs LASAL programs on a normal PC. Since each LARS instance runs one program, the MCP creates one workspace per station:
lars_runtime setup— creates workspaces for every station in the selected solution.lars_runtime start <station>— launches the LARS window for that station and reports the effective online port it probed.lars_runtime set_station_target <station>— adds or switches a dedicatedLARSprofile in the station's.lssand pointsOnlineConnectionat it (refusing a port that is not answering). The machine's own profile is left untouched.Now
build_project,control_plc, andplc_valueswork unchanged against the local runtime.lars_runtime restore <station>— switchesOnlineConnectionback to the machine profile. Nothing is rewritten, so no address can be lost.
Shortcut: lars_runtime simulate does the whole loop in one call — creates the workspace
if needed (CLASS 2 + LASAL SCREEN), switches ARM targets to PC, compiles, starts the LARS
instance (probing its effective online port) and downloads to it.
How the online port is resolved
Workspaces get distinct port blocks in lasalos2.xml (1954, 1964, 1974, …), but
LARS builds differ in which port they actually serve: older builds bind the workspace's
ONLINE port, while the field-tested 01.03.216 build serves the default port 1954 for a
single instance (and a second parallel instance on that build exposes no online port at
all). The MCP therefore probes what actually answers (workspace ONLINE port first, then
1954) and never assigns a port another running instance already owns — PLC and HMI end up
on distinct ports whenever the LARS build provides them, and a workspace that answers
nowhere fails loudly instead of pointing a station at a dead port. lars_runtime list and
lasal_status report the resolved port as effectiveOnlinePort.
LARS 01.03.216 ignores the table entirely: every instance binds 1954 and a second
concurrent instance exposes no online port at all, which makes multi-station simulation
impossible. If you need more than one instance, point LASAL_LARS_EXE at a build that
honours the table (01.03.213 was verified to) — no other change is needed.
Notes:
Projects compiled for
Processor="ARM"(most machine PLCs) needlars_runtime target_pcfirst — LARS is an x86 runtime and rejects ARM images.HMI panel / Local stations are already PC-targeted and work directly.
Downloads to LARS automatically include the PC loader (
addLoaderAnyway).%APPDATA%\lasalos2.xmlis edited losslessly - the MCP updates only the fields it owns and preserves everything else, so the file stays interchangeable with Sigmatek's LARSConfigTool (Descattributes,DATASERVICETCPPORT, comments, extra drive mappings). The catalog also exposes explicit create/clone/validate and lossless XML/JSON export/import, so a workspace set can be backed up and restored without losing unmodeled fields. Seedocs/LARS_COMPATIBILITY.md.Each workspace gets its own emulated
C:data root (%LOCALAPPDATA%\lasal-mcp\lars\<workspace>by default) instead of the hostC:\, so instances never shareLSLWORK/SRAM and never write into the real system drive. Files a program expects at a fixedC:\path are re-seeded from the host before every start, so the host copy stays authoritative.stopcloses LARS gracefully first — the runtime writes its SRAM image on a normal shutdown, and a force kill would silently drop retained variables.hmi_runtimeremaps published stations.json entries to running LARS instances, so the web HMI talks to the local simulation.Stations with a LASAL SCREEN project get their
.lprwired into the LARS workspace (SCREEN_PRJ_PATH), so LARS renders the panel screens locally;lars_runtime screenshotreturns a PNG of the window for visual verification.lars.scenario.runkeeps one PLC connection for all steps and supports named reads, DataAnalyzer trace start/stop, LARS window screenshots and JUnit XML output alongside set/wait/assert/sleep.lars.instance.list,status,restartandlogscover the runtime side;lars.doctorreports detected build version, configured vs effective ports, unknown config elements and data-root/port conflicts.
Contributing
Contributions are welcome! Please check out CONTRIBUTING.md for guidelines on code standards, adding tools, and submitting pull requests.
Releasing & CI/CD
Automated releases and publishing to npm are powered by GitHub Actions. Releases can be triggered manually via workflow dispatch with automated version bumping or by pushing version tags (v*.*.*). Release notes are maintained in CHANGELOG.md.
License
This project is licensed under the MIT License.
Available Tools
23 toolsapply_project_changesADestructive
Run CLASS 2 batch engine operations that cannot be done by editing files directly: create/delete/rename networks, add/remove/rename objects, create/delete connections, set init values, configure tasks, compile, download. Kills CLASS 2 IDE before running.
Inputs: operations (required), dry_run, lcp_path.
build_projectA
Compile the CLASS 2 project or download it to the PLC. Compilation closes this project's CLASS 2 IDE; an IDE opened for another project is reported, not killed. Download pings the PLC first. Supports async: true — the call then returns immediately with a jobId and you MUST poll check_job_status until it reports status completed/failed (the result is delivered there).
Inputs: action (required), async, options, lcp_path, +3 more.
check_job_statusARead-onlyIdempotent
Poll the status of a background job started with async: true (build_project, deploy_all, deploy_solution, lse_project). Omit jobId to list recent jobs.
Inputs: jobId.
control_plcBDestructive
Start, stop, or query PLC runtime state. Pings the target PLC before start/stop.
Inputs: action (required), lcp_path, connection.
create_class2_bootdiskADestructive
Create a CLASS 2 bootdisk (update stick): plain bootdisk or the full Update-Tool flavor with update script, Autoexec.lsl, LasalOS image, VISUDesigner publish folder and MultiMaster Stations.txt. Platform AUTO/ALL/ARM/X86.
Inputs: output_path (required), mode, os_file, lcp_path, +11 more.
deploy_allA
Full deploy pipeline: compile → download PLC → start PLC → verify state → compile LASAL SCREEN (.lpr, when present) → optional SCREEN download → update Visu stations → download Visu → start HMI runtime. Each step is optional via flags. Supports async: true — the call then returns immediately with a jobId and you MUST poll check_job_status until it reports status completed/failed (the result is delivered there).
Inputs: async, compile, lse_run, lcp_path, +17 more.
deploy_solutionADestructive
Multi-station deploy via MachineManager: generates a .lutc update file from the solution (class2/screen/visu downloads, OS updates, file transfers, run/boot, channel writes, CLI commands) and executes it with MachineManager.exe /update. This is the official flow for pushing LASAL SCREEN projects together with CLASS 2 to the same panel. Use dry_run to review the generated .lutc first. The newest MachineManager per-run log is returned with the result. Supports async: true — the call then returns immediately with a jobId and you MUST poll check_job_status until it reports status completed/failed (the result is delivered there).
Inputs: stations (required), async, dry_run, lsm_path, +3 more.
hmi_runtimeA
Start, stop, or check the local HMI web simulation (LasalVISUDataService). Publishes the project, copies webroot, and spawns the DataService. Returns the accessible HTTP URL (e.g. for testing via Playwright MCP or opening in a browser).
Inputs: action (required), lvp_path, debugPublish, publishFirst.
inspect_projectARead-onlyIdempotent
Read-only inventory of the CLASS 2 project: classes (name, channels, tasks), networks and objects, from the .lcp manifest and class sources. Use it to plan changes before apply_project_changes.
Inputs: lcp_path, class_names, include_networks, include_connections.
lars_runtimeA
Manage local LARS (LASAL Runtime System) simulation instances. LARS runs one program per instance — use one workspace per station (PLC + HMI) so both run simultaneously on separate ports. Actions: list (auto-cleans stale workspaces), setup (create workspaces for all stations), start (auto-creates the workspace if the station is known but unconfigured), stop, remove, gc (lazy cleanup of unreferenced workspaces), set_station_target (point a station's .lss at its LARS instance), restore (revert .lss to the real target. After set_station_target, build_project/control_plc/plc_values/deploy_all operate on the LARS instance automatically.
Inputs: action (required), name, dry_run, station, +6 more.
lasal_statusARead-onlyIdempotent
Check project selection, station discovery, PLC/HMI reachability, engine paths, running processes, HMI runtime health, live agent sessions and CLASS 2 ownership. Call to orient or diagnose connection issues.
Inputs: no named parameters.
lse_projectADestructive
Run LASAL SCREEN (LSE) engine operations on a .lpr screen project via the LASALScreen COM automation: info (screens/windows/servers/text lists/languages/settings inventory), create (fresh project), compile (Runtime output folder), download to a panel (Download & Run), and apply_changes with granular operations: merge/fuse projects, export_xml/import_xml text round-trips, import_variables (CLASS 2 references), textlist_* translations, server_get_property/server_set_property (limits, unit, menu, state schema, hostname, …), bulk update_buttons/update_softkeys theming, settings_set (resolution/compiler/online), image_insert. The .lpr itself is binary — never edit it directly; use this tool or the editor. Supports async: true — the call then returns immediately with a jobId and you MUST poll check_job_status until it reports status completed/failed (the result is delivered there).
Inputs: action (required), run, save, async, +4 more.
manage_class2ADestructive
Open or close the LASAL CLASS 2 IDE GUI. Close before running batch operations. close only terminates instances opened for this agent's project unless force: true is passed.
Inputs: action (required), force, lcp_path.
manage_lasalscreenADestructive
Open or close the LASAL SCREEN (LSE) editor for .lpr screen projects. Close before running lse_project automation (releases .lpr file locks).
Inputs: action (required), lpr_path.
manage_visudesignerADestructive
Open or close the VISUDesigner GUI. Close before running automated visu operations. close only terminates instances opened for this agent's project unless force: true is passed.
Inputs: action (required), force, lvp_path.
plc_diagnosticsC
Run PLC diagnostics: trace recording, file upload/download/delete on PLC, or static code analysis.
Inputs: action (required), os_path, lcp_path, plc_path, +8 more.
plc_valuesB
Read or write live channel values on a running PLC. Channels use 'ObjectName.ChannelName' format. Auto-coerces types based on ST declarations.
Inputs: action (required), values, channels, lcp_path, +1 more.
read_class_sourceA
Read or write a CLASS 2 class source (.st) by class name, with optional .h access. Writes are latin1-validated and require the CLASS 2 IDE to be closed.
Inputs: action (required), class_name (required), source, lcp_path, +2 more.
run_class2_scriptADestructive
Escape hatch: run arbitrary Python 2.7 batch statements through Lasal2.exe (module batch, project prj in scope). Use for batch API calls not covered by apply_project_changes; the project is NOT saved automatically.
Inputs: script_body (required), args, lcp_path.
select_projectAIdempotent
Set the active LASAL project for THIS agent session by directory path. Call first — all other tools default to this project. Selections are per MCP server process, so parallel agents do not redirect each other.
Inputs: path (required).
set_target_ipAIdempotent
Update the target IP/port/SSL of a station in its .lss (surgical edit, other settings preserved). Use when a station moved networks; connection strings can also be passed per call.
Inputs: ip, port, ssltls, station.
validate_guidsBDestructive
Scan a LASAL station project for duplicate GUID collisions and uninitialized TO_UDINT(0) placeholders in classes. Auto-resolves duplicate GUID collisions (generating fresh GUIDs and updating MaeExp.txt/xml) and populates exact LASAL CRC32 @CT_ hashes. Also cleans dangling network metadata.
Inputs: auto_fix, lcp_path.
visu_projectBDestructive
Run VISUDesigner engine operations: update stations, publish, manage text lists/schemes/media/code modules, set datapoint properties, or download to HMI. These need the VISUDesigner engine — for direct dashboard JSON editing, edit the files in the project directly.
Inputs: action (required), flags, lvp_path, connection, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 23 tools
Most tools target a distinct resource+action and the verbose descriptions clearly separate GUI management (manage_class2/lasalscreen/visudesigner) from engine operations (apply_project_changes, lse_project, visu_project). There is genuine overlap in the deployment cluster — build_project vs deploy_all vs deploy_solution, and lse_project vs deploy_solution both push SCREEN projects to panels — but the descriptions spell out the boundaries.
Snake_case is used throughout, but conventions mix: verb-first tools (check_job_status, inspect_project, apply_project_changes, deploy_all) coexist with noun-first/domain tools (lasal_status, lse_project, visu_project, lars_runtime, plc_values, hmi_runtime). The manage_* group is internally consistent, but the overall set blends verb-led and noun-led patterns without a single rule.
23 tools is on the heavy side, but the server spans several distinct subsystems (CLASS 2, LASAL SCREEN, VISUDesigner, PLC runtime, LARS simulation, deployment, job polling) and nearly every tool maps to a concrete capability. A few tools (deploy_all/deploy_solution/build_project) could plausibly be consolidated, but nothing feels purely redundant.
Coverage is broad: project selection/status, class inspection and read/write, GUID validation, batch apply, compile/download, multi-station deploy, PLC control/values/diagnostics, LARS simulation, SCREEN and VISU automation, HMI runtime, bootdisk creation, and async job polling. Minor gaps exist (no explicit project creation/deletion or job cancellation), but agents have workarounds via the batch/script escape hatches.
Maintenance
Related MCP Connectors
Create, run and debug Leapwork Play tests and runlists, build knowledge bases, and use AI workflows.
Cloud PLC simulator: validate and step-run LAD/SCL programs, run scenarios, return PASS/FAIL.
Control Unreal Engine to browse assets, import content, and manage levels and sequences. Automate…
AI-native programming language and toolchain for accountable, verifiable agent-driven development.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with B\&R Automation Studio projects by building code, running ARsim simulators, and reading or writing OPC UA variables. It facilitates industrial automation development and real-time variable integration through natural language commands.17MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI to operate STEP 7-Micro/WIN SMART via MCP, supporting offline STL/AWL analysis, project inspection, online PLC monitoring (snap7), and engine-injected operations like compile, download, upload, and symbol management through natural language.12-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to automate CODESYS V3 PLC development, including project editing, builds, library and alarm management, online variable read/write/force operations, and CODESYS documentation search via MCP.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM/AI editors to drive e!COCKPIT PLC automation projects through typed, schema-discoverable tools — building, importing, compiling, reading and writing online variables, snapshotting projects, and downloading to or managing files on a live PLC. Destructive operations such as download, write, stop, and PLC file put/rm are confirm-gated and carry destructiveHint annotations.Apache 2.0