codesysultra 1.0.0

package/dist/templates/set_pou_code.py

@@ -0,0 +1,90 @@
+import sys, scriptengine as script_engine, os, traceback
+{{ENSURE_PROJECT_OPEN_PYTHON_SNIPPET}}
+{{FIND_OBJECT_BY_PATH_PYTHON_SNIPPET}}
+POU_FULL_PATH = "{POU_FULL_PATH}" # Expecting format like "Application/MyPOU" or "Folder/SubFolder/MyPOU"
+DECLARATION_CONTENT = """{DECLARATION_CONTENT}"""
+IMPLEMENTATION_CONTENT = """{IMPLEMENTATION_CONTENT}"""
+
+try:
+    print("DEBUG: set_pou_code script: POU_FULL_PATH='%s', Project='%s'" % (POU_FULL_PATH, PROJECT_FILE_PATH))
+    primary_project = ensure_project_open(PROJECT_FILE_PATH)
+    if not POU_FULL_PATH: raise ValueError("POU full path empty.")
+
+    # Find the target POU/Method/Property object
+    target_object = find_object_by_path_robust(primary_project, POU_FULL_PATH, "target object")
+    if not target_object: raise ValueError("Target object not found using path: %s" % POU_FULL_PATH)
+
+    target_name = getattr(target_object, 'get_name', lambda: POU_FULL_PATH)()
+    print("DEBUG: Found target object: %s" % target_name)
+
+    # --- Set Declaration Part ---
+    declaration_updated = False
+    # Check if the content is actually provided (might be None/empty if only impl is set)
+    has_declaration_content = 'DECLARATION_CONTENT' in locals() or 'DECLARATION_CONTENT' in globals()
+    if has_declaration_content and DECLARATION_CONTENT is not None: # Check not None
+        if hasattr(target_object, 'textual_declaration'):
+            decl_obj = target_object.textual_declaration
+            if decl_obj and hasattr(decl_obj, 'replace'):
+                try:
+                    print("DEBUG: Accessing textual_declaration...")
+                    decl_obj.replace(DECLARATION_CONTENT)
+                    print("DEBUG: Set declaration text using replace().")
+                    declaration_updated = True
+                except Exception as decl_err:
+                    print("ERROR: Failed to set declaration text: %s" % decl_err)
+                    traceback.print_exc() # Print stack trace for detailed error
+            else:
+                 print("WARN: Target '%s' textual_declaration attribute is None or does not have replace(). Skipping declaration update." % target_name)
+        else:
+            print("WARN: Target '%s' does not have textual_declaration attribute. Skipping declaration update." % target_name)
+    else:
+         print("DEBUG: Declaration content not provided or is None. Skipping declaration update.")
+
+
+    # --- Set Implementation Part ---
+    implementation_updated = False
+    has_implementation_content = 'IMPLEMENTATION_CONTENT' in locals() or 'IMPLEMENTATION_CONTENT' in globals()
+    if has_implementation_content and IMPLEMENTATION_CONTENT is not None: # Check not None
+        if hasattr(target_object, 'textual_implementation'):
+            impl_obj = target_object.textual_implementation
+            if impl_obj and hasattr(impl_obj, 'replace'):
+                try:
+                    print("DEBUG: Accessing textual_implementation...")
+                    impl_obj.replace(IMPLEMENTATION_CONTENT)
+                    print("DEBUG: Set implementation text using replace().")
+                    implementation_updated = True
+                except Exception as impl_err:
+                     print("ERROR: Failed to set implementation text: %s" % impl_err)
+                     traceback.print_exc() # Print stack trace for detailed error
+            else:
+                 print("WARN: Target '%s' textual_implementation attribute is None or does not have replace(). Skipping implementation update." % target_name)
+        else:
+            print("WARN: Target '%s' does not have textual_implementation attribute. Skipping implementation update." % target_name)
+    else:
+        print("DEBUG: Implementation content not provided or is None. Skipping implementation update.")
+
+
+    # --- SAVE THE PROJECT TO PERSIST THE CODE CHANGE ---
+    # Only save if something was actually updated to avoid unnecessary saves
+    if declaration_updated or implementation_updated:
+        try:
+            print("DEBUG: Saving Project (after code change)...")
+            primary_project.save() # Save the overall project file
+            print("DEBUG: Project saved successfully after code change.")
+        except Exception as save_err:
+            print("ERROR: Failed to save Project after setting code: %s" % save_err)
+            detailed_error = traceback.format_exc()
+            error_message = "Error saving Project after code change for '%s': %s\\n%s" % (target_name, save_err, detailed_error)
+            print(error_message); print("SCRIPT_ERROR: %s" % error_message); sys.exit(1)
+    else:
+         print("DEBUG: No code parts were updated, skipping project save.")
+    # --- END SAVING ---
+
+    print("Code Set For: %s" % target_name)
+    print("Path: %s" % POU_FULL_PATH)
+    print("SCRIPT_SUCCESS: Declaration and/or implementation set successfully."); sys.exit(0)
+
+except Exception as e:
+    detailed_error = traceback.format_exc()
+    error_message = "Error setting code for object '%s' in project '%s': %s\\n%s" % (POU_FULL_PATH, PROJECT_FILE_PATH, e, detailed_error)
+    print(error_message); print("SCRIPT_ERROR: %s" % error_message); sys.exit(1)

package/dist/templates.js

@@ -0,0 +1,42 @@
+"use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.GET_POU_CODE_SCRIPT_TEMPLATE = exports.CREATE_METHOD_SCRIPT_TEMPLATE = exports.CREATE_PROPERTY_SCRIPT_TEMPLATE = exports.SET_POU_CODE_SCRIPT_TEMPLATE = exports.CREATE_POU_SCRIPT_TEMPLATE = exports.GET_PROJECT_STRUCTURE_SCRIPT_TEMPLATE = exports.COMPILE_PROJECT_SCRIPT_TEMPLATE = exports.SAVE_PROJECT_SCRIPT_TEMPLATE = exports.OPEN_PROJECT_SCRIPT_TEMPLATE = exports.CREATE_PROJECT_SCRIPT_TEMPLATE = exports.CHECK_STATUS_SCRIPT = exports.FIND_OBJECT_BY_PATH_PYTHON_SNIPPET = exports.ENSURE_PROJECT_OPEN_PYTHON_SNIPPET = void 0;
+const fs_1 = __importDefault(require("fs"));
+const path_1 = __importDefault(require("path"));
+const templatesDir = path_1.default.join(__dirname, 'templates');
+function readTemplate(filename) {
+    const filePath = path_1.default.join(templatesDir, filename);
+    try {
+        return fs_1.default.readFileSync(filePath, 'utf-8');
+    }
+    catch (error) {
+        console.error(`Error reading template file: ${filePath}`, error);
+        throw error;
+    }
+}
+// --- Base Snippets ---
+exports.ENSURE_PROJECT_OPEN_PYTHON_SNIPPET = readTemplate('ensure_project_open.py');
+exports.FIND_OBJECT_BY_PATH_PYTHON_SNIPPET = readTemplate('find_object_by_path.py');
+// --- Independent Scripts ---
+exports.CHECK_STATUS_SCRIPT = readTemplate('check_status.py');
+exports.CREATE_PROJECT_SCRIPT_TEMPLATE = readTemplate('create_project.py');
+// --- Dependent Scripts ---
+// Helper to inject dependencies safely
+function injectDependencies(content) {
+    // Use split/join to replace all occurrences and avoid special character issues in replacement string
+    let result = content.split('{{ENSURE_PROJECT_OPEN_PYTHON_SNIPPET}}').join(exports.ENSURE_PROJECT_OPEN_PYTHON_SNIPPET);
+    result = result.split('{{FIND_OBJECT_BY_PATH_PYTHON_SNIPPET}}').join(exports.FIND_OBJECT_BY_PATH_PYTHON_SNIPPET);
+    return result;
+}
+exports.OPEN_PROJECT_SCRIPT_TEMPLATE = injectDependencies(readTemplate('open_project.py'));
+exports.SAVE_PROJECT_SCRIPT_TEMPLATE = injectDependencies(readTemplate('save_project.py'));
+exports.COMPILE_PROJECT_SCRIPT_TEMPLATE = injectDependencies(readTemplate('compile_project.py'));
+exports.GET_PROJECT_STRUCTURE_SCRIPT_TEMPLATE = injectDependencies(readTemplate('get_project_structure.py'));
+exports.CREATE_POU_SCRIPT_TEMPLATE = injectDependencies(readTemplate('create_pou.py'));
+exports.SET_POU_CODE_SCRIPT_TEMPLATE = injectDependencies(readTemplate('set_pou_code.py'));
+exports.CREATE_PROPERTY_SCRIPT_TEMPLATE = injectDependencies(readTemplate('create_property.py'));
+exports.CREATE_METHOD_SCRIPT_TEMPLATE = injectDependencies(readTemplate('create_method.py'));
+exports.GET_POU_CODE_SCRIPT_TEMPLATE = injectDependencies(readTemplate('get_pou_code.py'));

package/dist/types.js

@@ -0,0 +1,8 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.ImplementationLanguageEnum = exports.PouTypeEnum = void 0;
+const zod_1 = require("zod");
+// --- Zod Schemas ---
+exports.PouTypeEnum = zod_1.z.enum(["Program", "FunctionBlock", "Function"]);
+exports.ImplementationLanguageEnum = zod_1.z.enum(["ST", "LD", "FBD", "SFC", "IL", "CFC", "StructuredText", "LadderDiagram", "FunctionBlockDiagram", "SequentialFunctionChart", "InstructionList", "ContinuousFunctionChart"]);
+// --- End Zod Schemas ---

package/dist/utils.js

@@ -0,0 +1,29 @@
+"use strict";
+var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
+    function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
+    return new (P || (P = Promise))(function (resolve, reject) {
+        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
+        function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
+        function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
+        step((generator = generator.apply(thisArg, _arguments || [])).next());
+    });
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.fileExists = fileExists;
+const promises_1 = require("fs/promises");
+// --- Helper Function (fileExists - async version) ---
+function fileExists(filePath) {
+    return __awaiter(this, void 0, void 0, function* () {
+        try {
+            yield (0, promises_1.stat)(filePath);
+            return true;
+        }
+        catch (error) {
+            if (error.code === 'ENOENT') {
+                return false; // File does not exist
+            }
+            throw error; // Other error
+        }
+    });
+}
+// --- End Helper Function ---

package/docs/configuration.md

@@ -0,0 +1,141 @@
+# Configuration Guide
+
+This guide explains how to configure the CODESYS MCP Toolkit for use with MCP clients, specifically focusing on Claude Desktop.
+
+## Claude Desktop Configuration
+
+Claude Desktop is a popular MCP client that can use the CODESYS MCP Toolkit.
+
+### Finding the Configuration File
+
+The configuration file is typically located at:
+*   **Windows:** `C:\Users\<YourUsername>\AppData\Roaming\Claude\settings.json` (or `claude_desktop_config.json` in older versions)
+*   **macOS:** `~/Library/Application Support/Claude/settings.json` (or `claude_desktop_config.json`)
+*   **Linux:** `~/.config/Claude/settings.json` (or `claude_desktop_config.json`)
+
+*(If you can't find `settings.json`, look for `claude_desktop_config.json`)*
+
+### Recommended Configuration: Direct Command
+
+Due to potential environment variable issues (especially with `PATH`) when launching Node.js tools via wrappers like `npx` within certain host applications (e.g., Claude Desktop), it is **strongly recommended** to configure Claude Desktop to run the installed command `codesys-mcp-tool` **directly**.
+
+Edit the configuration file and add the CODESYS MCP server to the `mcpServers` object:
+
+```json
+{
+  "mcpServers": {
+    // ... other servers ...
+    "codesys_local": {
+      "command": "codesys-mcp-tool", // <<< Use the direct command name
+      "args": [
+        // Pass arguments directly to the tool using flags
+        "--codesys-path", "C:\\Program Files\\Path\\To\\Your\\CODESYS\\Common\\CODESYS.exe", // Customize this path!
+        "--codesys-profile", "Your CODESYS Profile Name" // Customize this profile name!
+        // Optional: Add --workspace "/path/to/your/projects" if needed
+      ]
+    }
+    // ... other servers ...
+  }
+}
+```
+
+### Why Direct Command is Recommended
+
+Launching with `npx` (`"command": "npx"`) has been observed to cause errors (`'C:\Program' is not recognized...` or profile errors) when run from within applications like Claude Desktop. This is likely due to `npx` altering the execution environment (like the `PATH` variable) in a way that interferes with how CODESYS finds its own components or parses arguments when run non-interactively. Using the globally installed `codesys-mcp-tool` command directly avoids this interference.
+
+### Customizing for Your Environment
+
+You **must** customize:
+1.  `--codesys-path`: Set this value to the **full and correct path** of your specific `CODESYS.exe` executable file.
+2.  `--codesys-profile`: Set this value to the **exact name** of the CODESYS profile you want to use (this name is visible in the CODESYS UI or start menu).
+
+**Important Notes:**
+*   Use double backslashes (`\\`) for paths in the JSON file if you are on Windows.
+*   The profile name must match *exactly*, including capitalization and spacing.
+*   Ensure `codesys-mcp-tool` is accessible in the system PATH where Claude Desktop runs. Global installation via `npm install -g` usually handles this.
+
+### Applying Changes
+
+After modifying the configuration:
+1.  Save the `settings.json` file.
+2.  **Restart Claude Desktop completely** (ensure it's fully closed and reopened).
+3.  Claude should now attempt to connect to the CODESYS MCP server using the direct command.
+
+### Alternative (Not Recommended): Using `npx`
+
+If you cannot use the direct command method for some reason, you can try `npx`, but be aware of the potential issues mentioned above.
+
+```json
+// Example using npx (POTENTIALLY PROBLEMATIC - USE WITH CAUTION):
+{
+  "mcpServers": {
+    "codesys_local": {
+      "command": "npx",
+      "args": [
+        "-y", // Tells npx to install temporarily if not found globally
+        "@codesys/mcp-toolkit",
+        // Arguments for the tool MUST come AFTER the package name
+        "--codesys-path", "C:\\Program Files\\Path\\To\\Your\\CODESYS\\Common\\CODESYS.exe",
+        "--codesys-profile", "Your CODESYS Profile Name"
+        // Optional: "--workspace", "/path/to/your/projects"
+      ]
+    }
+  }
+}
+```
+*If you encounter errors with `npx`, switch to the recommended Direct Command method.*
+
+## Command-Line Options (for `codesys-mcp-tool`)
+
+When running `codesys-mcp-tool` directly or configuring it in your MCP client, you can use these arguments:
+
+*   `-p, --codesys-path <path>`: Full path to `CODESYS.exe`. (Required, overrides `CODESYS_PATH` env var, has a default but relying on it is not recommended).
+*   `-f, --codesys-profile <profile>`: Name of the CODESYS profile. (Required, overrides `CODESYS_PROFILE` env var, has a default but relying on it is not recommended).
+*   `-w, --workspace <dir>`: 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.
+*   `-V, --version`: Output the version number.
+*   `-h, --help`: Display help for command.
+
+## Verifying Configuration
+
+To verify your configuration within Claude Desktop:
+
+1.  After restarting Claude with the correct configuration, wait for the server to connect (check logs if needed).
+2.  Ask Claude:
+    ```
+    Can you please check the status of the CODESYS Local server?
+    ```
+    (Replace `CODESYS Local` if you used a different key in `mcpServers`).
+
+3.  Claude should use the `codesys://project/status` resource. A successful response will show information like `Scripting OK: true`, `Project Open: ...`, etc. An error indicates a problem with the connection, CODESYS setup, or the script execution itself (check logs).
+
+## Multiple CODESYS Installations
+
+If you have multiple CODESYS installations, you can create multiple server entries in `mcpServers` with different keys (names) and point each to the specific installation:
+
+```json
+{
+  "mcpServers": {
+    "codesys_sp21": { // Unique key for this server
+      "command": "codesys-mcp-tool", // Direct command
+      "args": [
+        "--codesys-path", "C:\\Program Files\\CODESYS 3.5.21.0\\CODESYS\\Common\\CODESYS.exe",
+        "--codesys-profile", "CODESYS V3.5 SP21"
+      ]
+    },
+    "codesys_sp19": { // Unique key for this server
+      "command": "codesys-mcp-tool", // Direct command
+      "args": [
+        "--codesys-path", "C:\\Program Files\\CODESYS 3.5.19.0\\CODESYS\\Common\\CODESYS.exe",
+        "--codesys-profile", "CODESYS V3.5 SP19"
+      ]
+    }
+    // ... other servers ...
+  }
+}
+```
+
+## Next Steps
+
+*   Try some [basic examples](examples.md)
+*   Learn about the [available tools and resources](api.md)
+*   Check the [troubleshooting guide](troubleshooting.md) if you encounter issues

package/docs/index.md

@@ -0,0 +1,26 @@
+# CODESYS MCP Toolkit Documentation
+
+Welcome to the documentation for the CODESYS MCP Toolkit!
+
+## Overview
+
+The CODESYS MCP Toolkit provides a bridge between Model Context Protocol (MCP) clients and CODESYS V3 programming environments. This toolkit enables seamless interaction for automating project management, POU creation, code editing, and compilation tasks.
+
+## Components
+
+- **MCP Server**: Core component that handles MCP protocol communication
+- **CODESYS Script Integration**: Interface with CODESYS scripting engine
+- **Command-Line Interface**: For direct usage and configuration
+
+## Getting Started
+
+- [Installation](installation.md)
+- [Configuration](configuration.md)
+- [Usage Examples](examples.md)
+- [API Reference](api.md)
+
+## Advanced Topics
+
+- [Contributing Guidelines](../CONTRIBUTING.md)
+- [Troubleshooting](troubleshooting.md)
+- [Custom Extensions](extensions.md)

package/docs/installation.md

@@ -0,0 +1,84 @@
+# Installation Guide
+
+This guide covers how to install the CODESYS MCP Toolkit on your system.
+
+## Prerequisites
+
+Before installing, ensure you have:
+
+1. **Node.js**: Version 18 or later
+   - Download from [nodejs.org](https://nodejs.org/)
+   - Verify installation with `node --version`
+
+2. **CODESYS V3**: A working CODESYS V3 installation
+   - Tested with version 3.5 SP21
+   - Must have the **Scripting Engine** component enabled
+   - Verify by opening CODESYS and checking if scripting commands are available
+
+3. **MCP Client**: An MCP-enabled application (e.g., Claude Desktop)
+
+## Installation Methods
+
+### Method 1: Install from npm (Recommended)
+
+The simplest way to install is directly from npm:
+
+```bash
+npm install -g @codesys/mcp-toolkit
+```
+
+This installs the package globally on your system, making the `codesys-mcp-toolkit` command available in your terminal.
+
+Verify the installation by running:
+
+```bash
+codesys-mcp-toolkit --version
+```
+
+### Method 2: Install from Source
+
+For development or to get the latest unreleased changes:
+
+```bash
+# Clone the repository
+git clone https://github.com/yourusername/codesys-mcp-toolkit.git
+cd codesys-mcp-toolkit
+
+# Install dependencies
+npm install
+
+# Build the project
+npm run build
+
+# Install globally
+npm install -g .
+```
+
+Verify the installation using the same command as above.
+
+## Next Steps
+
+After installation:
+
+1. [Configure your MCP client](configuration.md) to use the CODESYS MCP Toolkit
+2. Try some [basic examples](examples.md)
+3. Learn about the [available tools and resources](api.md)
+
+## Troubleshooting Installation Issues
+
+### Common Issues
+
+- **Permission errors**: You may need to run npm with administrative privileges
+  ```bash
+  sudo npm install -g @codesys/mcp-toolkit  # On Linux/macOS
+  # or use PowerShell as Administrator on Windows
+  ```
+
+- **Path issues**: Ensure the npm global bin directory is in your PATH
+
+- **Node.js version**: Verify you have Node.js 18 or later
+  ```bash
+  node --version
+  ```
+
+If you encounter other issues, please check the [troubleshooting guide](troubleshooting.md) or [open an issue](https://github.com/yourusername/codesys-mcp-toolkit/issues) on GitHub.

package/examples/README.md

@@ -0,0 +1,78 @@
+# CODESYS MCP Toolkit Examples
+
+This directory contains examples of how to use the CODESYS MCP toolkit effectively.
+
+## Example Configuration Files
+
+### Basic MCP Configuration
+
+`claude_desktop_config.json` - Example configuration for Claude Desktop:
+
+```json
+{
+  "mcpServers": {
+    "codesys_local": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@codesys/mcp-toolkit",
+        "--codesys-path", "C:\\Program Files\\CODESYS 3.5.21.0\\CODESYS\\Common\\CODESYS.exe",
+        "--codesys-profile", "CODESYS V3.5 SP21"
+      ]
+    }
+  }
+}
+```
+
+## Example Prompts
+
+Here are some example prompts you can use with Claude Desktop:
+
+### Create a Motor Controller Function Block
+
+```
+Using the CODESYS Local server, please create a MotorController function block with the following:
+
+1. Properties:
+   - SpeedSetpoint (INT)
+   - ActualSpeed (INT)
+   - IsRunning (BOOL)
+
+2. Methods:
+   - Start() - Sets IsRunning to TRUE
+   - Stop() - Sets IsRunning to FALSE
+   - SetSpeed(speed: INT) - Sets SpeedSetpoint to the given value
+
+Create this in a new project at C:/MyProjects/MotorControl.project
+```
+
+### Open and Analyze an Existing Project
+
+```
+Using the CODESYS Local server, please open the project at C:/MyProjects/ExistingProject.project and show me its structure. Then, show me the code for the main POU.
+```
+
+### Compile a Project
+
+```
+Using the CODESYS Local server, please open the project at C:/MyProjects/MyProject.project and compile it. Let me know if there are any errors.
+```
+
+## Programmatic Usage Examples
+
+If you're integrating directly with the server code, here are some examples:
+
+### CLI Usage
+
+Run the server directly:
+
+```bash
+codesys-mcp-toolkit --codesys-path "C:\Program Files\CODESYS 3.5.21.0\CODESYS\Common\CODESYS.exe" --codesys-profile "CODESYS V3.5 SP21"
+```
+
+## Use Cases
+
+* Automated PLC project creation
+* Standardized Function Block library management
+* Continuous integration for CODESYS projects
+* Documentation generation from CODESYS projects

package/examples/sample_config.json

@@ -0,0 +1,32 @@
+{
+  "mcpServers": {
+    "codesys_local": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@codesys/mcp-toolkit",
+        "--codesys-path", "C:\\Program Files\\CODESYS 3.5.21.0\\CODESYS\\Common\\CODESYS.exe",
+        "--codesys-profile", "CODESYS V3.5 SP21"
+      ]
+    },
+    "filesystem": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@modelcontextprotocol/server-filesystem",
+        "C:/MyProjects"
+      ]
+    },
+    "memory": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@modelcontextprotocol/server-memory"
+      ]
+    },
+    "puppeteer": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-puppeteer"]
+    }
+  }
+}

package/package.json

@@ -0,0 +1,48 @@
+{
+  "name": "codesysultra",
+  "version": "1.0.0",
+  "description": "Model Context Protocol (MCP) server for CODESYS automation platform",
+  "main": "dist/server.js",
+  "bin": {
+    "codesys-mcp-tool": "./dist/bin.js"
+  },
+  "scripts": {
+    "test": "echo \"Error: no test specified\" && exit 1",
+    "build": "tsc && node scripts/copy-templates.js",
+    "start": "node ./dist/bin.js"
+  },
+  "keywords": [
+    "codesys",
+    "mcp",
+    "modelcontextprotocol",
+    "plc",
+    "automation",
+    "programming"
+  ],
+  "author": "Nirithy",
+  "license": "Apache-2.0",
+  "type": "commonjs",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/johannesPettersson80/codesys-mcp-toolkit.git"
+  },
+  "homepage": "https://github.com/johannesPettersson80/codesys-mcp-toolkit#readme",
+  "bugs": {
+    "url": "https://github.com/johannesPettersson80/codesys-mcp-toolkit/issues"
+  },
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.10.2",
+    "axios": "^1.6.8",
+    "commander": "^11.1.0",
+    "yargs": "^17.7.2",
+    "zod": "^3.24.3"
+  },
+  "devDependencies": {
+    "@types/node": "^20.14.1",
+    "@types/yargs": "^17.0.33",
+    "typescript": "^5.5.3"
+  }
+}

package/scripts/copy-templates.js

@@ -0,0 +1,31 @@
+const fs = require('fs');
+const path = require('path');
+
+const srcDir = path.join(__dirname, '../src/templates');
+const distDir = path.join(__dirname, '../dist/templates');
+
+console.log(`Copying templates from ${srcDir} to ${distDir}...`);
+
+if (!fs.existsSync(srcDir)) {
+    console.error(`Source directory ${srcDir} does not exist.`);
+    process.exit(1);
+}
+
+if (!fs.existsSync(distDir)) {
+    fs.mkdirSync(distDir, { recursive: true });
+}
+
+const files = fs.readdirSync(srcDir);
+let copiedCount = 0;
+
+files.forEach(file => {
+    if (file.endsWith('.py')) {
+        const srcFile = path.join(srcDir, file);
+        const distFile = path.join(distDir, file);
+        fs.copyFileSync(srcFile, distFile);
+        console.log(`Copied ${file}`);
+        copiedCount++;
+    }
+});
+
+console.log(`Successfully copied ${copiedCount} template files.`);