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 automate a headless browser — 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, browser automation. For everything else (reading/editing .st, .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: B&R Automation Studio MCP Server

Features

• Build & Deploy: Compile CLASS 2 projects, download to PLC, full deploy pipelines.

• PLC Control: Start/stop PLC runtime, read/write live channel values, query state.

• CLASS 2 Batch Engine: Create/delete networks, add/remove objects, manage connections, configure tasks — operations that require the CLASS 2 scripting engine.

• VISUDesigner Engine: Sync datapoints, manage text lists/schemes/media, publish, download to HMI.

• HMI Simulation: Local web runtime via LasalVISUDataService with headless Edge browser automation for visual verification.

• PLC Diagnostics: Tracing, file transfer, static code analysis.

• Project Guide: Built-in resource (lasal://guide) documenting all LASAL file formats so the agent can edit project files directly.

Prerequisites

• Windows OS (Sigmatek LASAL suite runs exclusively on Windows).

• Node.js v18 or higher.

• Sigmatek LASAL Suite:

  • LASAL CLASS 2 (PLC engineering).

  • VISUDesigner (HMI design).

Installation & Setup

git clone <repository-url>
cd Lasal-MCP
npm install
npm run build

Configuration

Environment Variables

Connecting to MCP Clients

Claude Desktop

Add to %APPDATA%\Claude\claude_desktop_config.json:

{
  "mcpServers": {
    "lasal-mcp": {
      "command": "node",
      "args": ["C:/path/to/Lasal-MCP/dist/server.js"],
      "env": {
        "LASAL_CLASS2_EXE": "C:\\Program Files (x86)\\Sigmatek\\Lasal\\Class2\\Bin\\Lasal2.exe",
        "LASAL_VISUDESIGNER_EXE": "C:\\Program Files\\Sigmatek\\Lasal\\VISUDesigner\\VISUDesigner.exe"
      }
    }
  }
}

Claude Code

Add to .claude/settings.json or run claude mcp add:

{
  "mcpServers": {
    "lasal-mcp": {
      "command": "node",
      "args": ["C:/path/to/Lasal-MCP/dist/server.js"]
    }
  }
}

Available Tools

Engine & Hardware Tools (MCP)

Direct File Editing (no MCP needed)

The agent edits these files directly with its native file tools:

See the built-in lasal://guide resource for detailed file format documentation.

Development

npm run dev          # Watch mode
npm test             # Run tests (Vitest)
npm run test:watch   # Tests in watch mode
npm run lint         # ESLint
npm run format       # Prettier
npm run inspector    # MCP Inspector for interactive debugging