Festo Codesys Mcp

io.github.efranceschettiPublished by GitHub account efranceschettiv1.0.1Updated Oct 24, 2026

MCP server for Festo/CODESYS PLCs: IEC 61131-3 ST + validated PLCopen XML generation.

Overview

AI-generated overview

Generates validated IEC 61131-3 Structured Text and PLCopen XML for Festo/CODESYS PLC projects, with optional tools to drive a live CODESYS IDE.

What you can do
This local MCP server helps an assistant produce IEC 61131-3 Structured Text and PLCopen XML for Festo/CODESYS PLCs, with validation of the generated XML. It also exposes optional ide_* tools that drive a live CODESYS V3.5 instance on Windows, plus cpx_*/edcon_* hardware commissioning tools that are described as bench use only. File-writing tools operate inside a workspace directory by default.
When to use it
Useful when an assistant needs to draft or validate PLCopen XML and Structured Text for Festo/CODESYS controllers, or to script a running CODESYS V3.5 IDE. The hardware commissioning tools are intended for bench work rather than production lines.
Requirements
Runs locally over stdio, installed with npx from the npm package festo-codesys-mcp; desktop only, no web execution. The ide_* tools need FESTO_MCP_CODESYS_PATH pointing at CODESYS.exe (Windows) and FESTO_MCP_CODESYS_PROFILE naming the CODESYS profile. FESTO_MCP_PYTHON can point to a Python interpreter with lxml for the XSD/semantic validators and hardware tools. No authentication is declared.
Before you install
File-writing tools can write outside the workspace only if FESTO_MCP_ALLOW_OUTSIDE_WORKSPACE is set to 1, so leave it unset unless you intend that. The cpx_*/edcon_* hardware commissioning tools are enabled by FESTO_MCP_ENABLE_HARDWARE=1 and are flagged as bench use only, meaning they can act on connected hardware. The ide_* tools drive a live CODESYS instance and may change project state.

Installation

In SourceWeft

  1. Open Festo Codesys Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.