Codesys-MCP-Master

One MCP server for every installed CODESYS 3.5 version (SP18, SP19, SP21, SP22; every offline tool live-tested on all four, online tools against a local soft PLC on SP18, SP19 and SP21). Each tool call picks the install from the project file's saved version. It launches CODESYS with its UI visible, keeps it running, and drives it through 132 tools: project and POU authoring, compile, online/runtime, devices and tasks, symbol configuration, multi-device projects, and a version + git release pipeline. The CODESYS menus stay usable while it is connected, and on SP22 the CODESYS-shipped MCP server's tools are available alongside (ide_ prefix).

Started as a fork of luke-harriman/Codesys-MCP, which stopped working on SP21+. About 13% of the code here is still from that project (measured 2026-10-06: roughly one line in eight of the TypeScript, Python scripts and tests); the rest was written for this one. Why and what changed: docs/whats-new.md.

Quick start

npm install -g codesys-mcp-master
codesys-mcp-master --print-config      # one MCP config entry for all installed CODESYS versions

Paste the entry into .mcp.json (or claude mcp add ...) and restart Claude Code. Details, install from source and config options: docs/installation.md.

Related MCP server: T-IA Connect (Siemens TIA Portal)

Working in natural language

You do not call the tools yourself. You tell Claude (or another MCP client) what you want in plain words, and it picks the tools, fills in the arguments and reports back. For example:

• "Open the pump project and add a function block FB_PumpControl with a start and a stop input."

• "Compile it and fix whatever errors come up."

• "Where is nSpeed used? Rename it to nMotorSpeed everywhere."

• "Switch the PLC to simulation, start the application and watch PLC_PRG.nCycles and GVL.bAlarm for ten seconds."

• "Download the project to the PLC at 192.0.2.10 and tell me which version is running."

• "Release the next minor version with a changelog entry."

Each request becomes one or more tool calls: create_pou, compile_project and get_compile_messages, find_references and rename_symbol, set_simulation_mode and monitor_variables, download_to_device and read_running_version_online, release_project_version. The client shows each call, so you can see what was done, and whether a call that changes something (a download, a write to a PLC) needs your approval first is up to the client and its permission settings. The server itself stops and asks in a few cases: before it closes another CODESYS, discards unsaved projects or starts a second CODESYS next to yours.

Name things the way you would to a colleague: project file names, object paths such as Application/PLC_PRG, variable expressions, PLC addresses. If something is ambiguous (several installs, a PLC that is in use, a project open in another CODESYS), the answer says so instead of guessing.

Documentation

Credits and license

Upstream architecture and the original tool set: luke-harriman/Codesys-MCP. This fork: phobicdotno/Codesys-MCP-Master, Karstein Kvistad. MIT.