YouTrack MCP Server

## Description Brief description of the changes in this PR. ## Type of Change - [ ] 🐛 Bug fix (non-breaking change which fixes an issue) - [ ] ✨ New feature (non-breaking change which adds functionality) - [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] 📚 Documentation update - [ ] 🔧 Performance improvement - [ ] ♻️ Code refactoring - [ ] 🧪 Test improvements ## Changes Made - [ ] Added/modified tools in `src/tools.ts` - [ ] Updated YouTrack client in `src/youtrack-client.ts` - [ ] Modified main server logic in `src/index.ts` - [ ] Updated configuration or utilities - [ ] Added/updated tests - [ ] Updated documentation ## Tools Added/Modified If you added or modified MCP tools, list them here: - `tool_name` - Description of what it does - `another_tool` - Description of what it does ## Testing - [ ] Tests added for new functionality - [ ] All existing tests pass - [ ] Manual testing completed - [ ] Build succeeds (`npm run build`) - [ ] Type checking passes (`npx tsc --noEmit`) ### Test Results ```bash # Paste test output here if relevant ``` ## YouTrack API Changes - [ ] Uses existing YouTrack API endpoints - [ ] Introduces new API endpoint usage - [ ] Changes API authentication/authorization - [ ] Affects API rate limiting ## Breaking Changes If this is a breaking change, describe what breaks and how to migrate: ``` Description of breaking changes and migration steps ``` ## Documentation - [ ] README.md updated - [ ] Workflow documentation updated - [ ] API documentation updated - [ ] Code comments added/updated - [ ] No documentation changes needed ## Backwards Compatibility - [ ] Fully backwards compatible - [ ] Backwards compatible with deprecation warnings - [ ] Breaking changes (documented above) ## Performance Impact - [ ] No performance impact - [ ] Improves performance - [ ] May impact performance (explain below) ## Security Considerations - [ ] No security implications - [ ] Reviewed for security implications - [ ] Security review needed ## Checklist - [ ] My code follows the project's style guidelines - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes ## Related Issues Closes #(issue number) Related to #(issue number) ## Screenshots (if applicable) Add screenshots to help explain your changes. ## Additional Notes Add any other notes about the PR here.