A Model Context Protocol (MCP) server for CODESYS V3 programming environments.
Codesys mcp server connects Codesys to AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server for CODESYS V3 programming environments.
A Model Context Protocol (MCP) server for CODESYS V3 programming environments. This toolkit enables seamless interaction between MCP clients (like Claude Desktop) and CODESYS, allowing automation of project management, POU creation, code editing, and compilation tasks via the CODESYS Scripting Engine.
Once connected, the assistant can call these 4 tools directly:
codesys — //project/status: Check scripting status and currently open project stateNode.js — Version 18.0.0 or later is recommendedCause — ** This typically happens when the tool is launched via npx within an environment like Claude Desktop. The execution environment (PATH variable) provided toSolution — ** Configure your MCP Client to run the command directly ("command": "codesys-mcp-tool") instead of using "command": "npx". See the **RecommendedThe server is distributed via npm as @codesys/mcp-toolkit, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
The server reads one environment variable: CODESYS_PATH. Keep credentials in your client's env block or a secrets manager rather than committing them.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Codesys sits in that group, and the shape of its toolset — codesys, Node.js, Cause among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| codesys | //project/status: Check scripting status and currently open project state. |
| Node.js | Version 18.0.0 or later is recommended. |
| Cause | ** This typically happens when the tool is launched via npx within an environment like Claude Desktop. The execution environment (PATH variable) provided to the process likely causes an internal CODESYS command (like run |
| Solution | ** Configure your MCP Client to run the command **directly** ("command": "codesys-mcp-tool") instead of using "command": "npx". See the **Recommended Configuration Method** section above. |
{
"mcpServers": {
"codesys-mcp-toolkit": {
"command": "npx",
"args": ["-y", "@codesys/mcp-toolkit"],
"env": {
"CODESYS_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CODESYS_PATH | Filesystem location the server is allowed to use. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.