@codesys/mcp-toolkit 1.1.14 → 1.1.16

package/.claude/settings.local.json

@@ -0,0 +1,24 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(npm install:*)",
+      "Bash(npm run build:*)",
+      "Bash(npm publish:*)",
+      "Bash(npm pack:*)",
+      "Bash(mkdir:*)",
+      "Bash(tar:*)",
+      "Bash(ls:*)",
+      "Bash(find:*)",
+      "Bash(grep:*)",
+      "Bash(git clone:*)",
+      "Bash(pushd:*)",
+      "Bash(popd:*)",
+      "Bash(git checkout:*)",
+      "Bash(git ls-tree:*)",
+      "Bash(git reset:*)",
+      "Bash(git push:*)",
+      "Bash(npm whoami:*)"
+    ],
+    "deny": []
+  }
+}

package/CHANGELOG.md

@@ -5,71 +5,12 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [1.1.14] - 2025-05-06
+## [1.1.16] - 2025-05-06
 
 ### Fixed
-- Fixed path handling for CODESYS objects to correctly handle dot and slash separators
-- Added automatic detection of common CODESYS structure paths like "PLCWinNT/Plc Logic/Application" 
-- Improved object path traversal in find_object_by_path function
-
-## [1.1.13] - 2025-05-06
-
-### Fixed
-- Fixed remaining f-string formatting in create_pou.py script
-- Restored compatibility with older Python versions in path formatting
-
-## [1.1.12] - 2025-05-06
-
-### Fixed
-- Completely rewrote path handling to avoid excessive backslash escaping
-- Added multiple fallback methods for opening CODESYS projects
-- Removed use of non-existent get_version_info API
-- Made project structure tool more resilient to various CODESYS API patterns
-
-## [1.1.11] - 2025-05-06
-
-### Fixed
-- Fixed syntax errors in Python scripts by replacing f-strings with older-style formatting
-- Ensures compatibility with Python version used in CODESYS scripting environment
-
-## [1.1.10] - 2025-05-06
-
-### Fixed
-- Improved handling of Windows paths in `get_project_structure` and `ensure_project_open` functions
-- Enhanced error handling and debugging for project structure tool
-- Added more detailed logging to help diagnose connection issues with CODESYS
-
-## [1.1.9] - 2025-05-06
-
-### Added
-- Added three new MCP tools that were previously only available as resources:
-  - `check_status`: Tool to check CODESYS environment and open project status
-  - `get_project_structure`: Tool to retrieve the structure of a CODESYS project
-  - `get_pou_code`: Tool to retrieve code from a specific POU
-- These tools allow Claude and other AI assistants to directly access project inspection functionality
-
-## [1.1.8] - 2025-05-06
-
-### Fixed
-- Enhanced create_pou script to automatically find the Application object when only "Application" is specified as the parent path
-- Added better error messages with suggestions when Application isn't found
-
-## [1.1.7] - 2025-05-06
-
-### Fixed
-- Fixed Python scripts not being included in the npm package
-- Enhanced script loading to search for scripts in multiple possible locations
-- Added build step to copy scripts to dist folder
-
-## [1.1.6] - 2025-05-06
-
-### Fixed
-- Added TypeScript as dev dependency to fix build process
-
-## [1.1.4] - 2025-05-01
-
-### Changed
-- Refactored the code for better maintainability
+- Reverted to v1.1.3 code base which has working POU creation functionality
+- Fixed path handling by using simpler approach from v1.1.3
+- Restored original Application object finding logic that worked in v1.1.3
 
 ## [1.0.0] - 2025-04-23
 

package/CONTRIBUTING.md

@@ -0,0 +1,72 @@
+# Contributing to @codesys/mcp-toolkit
+
+Thank you for considering contributing to the CODESYS MCP Toolkit! This document provides guidelines and steps for contributing.
+
+## Code of Conduct
+
+Please be respectful and considerate of others when contributing to this project. We aim to foster an inclusive and welcoming community.
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+Bug reports help improve the project! When reporting bugs:
+
+1. Check if the bug has already been reported
+2. Use the bug report template
+3. Include detailed steps to reproduce the issue
+4. Describe the expected vs. actual behavior
+5. Include screenshots if applicable
+6. Provide environment details (OS, Node.js version, etc.)
+
+### Suggesting Features
+
+We welcome feature suggestions! When suggesting features:
+
+1. Describe the problem your feature would solve
+2. Explain how your feature would work
+3. Consider potential alternatives
+4. Provide examples of similar features in other projects (if applicable)
+
+### Pull Requests
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/amazing-feature`)
+3. Make your changes
+4. Run tests and ensure they pass
+5. Commit your changes (`git commit -m 'Add amazing feature'`)
+6. Push to your branch (`git push origin feature/amazing-feature`)
+7. Open a Pull Request
+
+## Development Setup
+
+1. Clone the repository
+   ```bash
+   git clone https://github.com/yourusername/codesys-mcp-toolkit.git
+   cd codesys-mcp-toolkit
+   ```
+
+2. Install dependencies
+   ```bash
+   npm install
+   ```
+
+3. Build the project
+   ```bash
+   npm run build
+   ```
+
+## Style Guidelines
+
+- Follow existing code formatting patterns
+- Use meaningful variable and function names
+- Add comments where necessary to explain complex logic
+- Update documentation when changing functionality
+
+## Testing
+
+- Add tests for new features
+- Ensure all tests pass before submitting a PR
+- Consider edge cases in your tests
+
+Thank you for contributing!