npm install -g @codesys/mcp-toolkit

{
  "mcpServers": {
    // ... other servers ...
    "codesys_local": {
      "command": "codesys-mcp-tool", // `: Full path to `CODESYS.exe`. (Required, overrides `CODESYS_PATH` env var, has a default but relying on it is not recommended).
*   `-f, --codesys-profile `: Name of the CODESYS profile. (Required, overrides `CODESYS_PROFILE` env var, has a default but relying on it is not recommended).
*   `-w, --workspace `: Workspace directory for resolving relative project paths passed to tools. Defaults to the directory where the command was launched (which might be unpredictable when run by another application). Setting this explicitly might be needed if using relative paths.
*   `-h, --help`: Show help message.
*   `--version`: Show package version.

## 🔍 Troubleshooting

*   **`'C:\Program' is not recognized...` error immediately after connection:**
    *   **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 running Python) to fail.
    *   **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.

*   **Tool Fails / Errors in Output:**
    *   Check the logs from your MCP Client application (e.g., Claude Desktop logs). Look for `INTEROP:` messages or Python `DEBUG:` / `ERROR:` messages printed to stderr from the CODESYS script execution.
    *   Ensure the `--codesys-path` and `--codesys-profile` arguments passed to the command are correct and point to a valid CODESYS installation with scripting enabled.
    *   Verify the project paths and object paths you are passing to tools are correct (use forward slashes `/`).
    *   Make sure no other CODESYS instances are running in conflicting ways (e.g., holding a lock on the profile).

*   **`command not found: codesys-mcp-tool`:**
    *   Ensure the package was installed globally (`npm install -g @codesys/mcp-toolkit`).
    *   Ensure the npm global bin directory is in your system's `PATH` environment variable. Find it with `npm config get prefix` and add the `bin` subdirectory (or the main directory itself on Windows) to your PATH.

*   **Check Logs:**
    *   Claude Desktop logs: `C:\Users\\AppData\Roaming\Claude\logs\` (Windows)

## 🤝 Contributing
Contributions, issues, and feature requests are welcome! Feel free to check the issues page. (Optionally add a CONTRIBUTING.md file with more details).

## 📝 License
This project is licensed under the MIT License - see the LICENSE file for details.

## 🙏 Acknowledgements
- The CODESYS GmbH team for the powerful CODESYS platform and its scripting engine.
- The Model Context Protocol project for defining the interaction standard.
- All contributors and users who help improve this toolkit.