MCP Tools for Obsidian

<!-- 🚨 READ FIRST: https://github.com/jacksteamdev/obsidian-mcp-tools/blob/main/CONTRIBUTING.md This is a FREE project maintained by volunteers. Be respectful and patient. Rude, demanding, or entitled behavior results in immediate bans. Join Discord for discussions: https://discord.gg/q59pTrN9AA --> ## Pull Request Description **Clear description of what this PR changes and why** ## Type of Change - [ ] 🐛 Bug fix (non-breaking change that fixes an issue) - [ ] ✨ New feature (non-breaking change that adds functionality) - [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] 📚 Documentation update - [ ] 🔧 Internal/tooling change ## Testing **How has this been tested?** - [ ] Local Obsidian vault testing - [ ] MCP server functionality verified - [ ] Claude Desktop integration tested - [ ] Cross-platform testing (if applicable) ## Architecture Compliance - [ ] Follows feature-based architecture patterns (see `/docs/project-architecture.md`) - [ ] Uses ArkType for runtime validation where applicable - [ ] Implements proper error handling - [ ] Includes setup function for new features - [ ] Follows coding standards in `.clinerules` ## Checklist - [ ] My code follows the project's coding standards - [ ] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to documentation (if applicable) - [ ] 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 ## Security Considerations - [ ] No hardcoded secrets or API keys - [ ] Input validation implemented where needed - [ ] No new security vulnerabilities introduced - [ ] Follows minimum permission principles ## Additional Context <!-- - Screenshots (if UI changes) - Performance considerations - Backward compatibility notes - Related issues or PRs --> ## For Maintainers **Review checklist:** - [ ] Code quality and architecture compliance - [ ] Security review completed - [ ] Tests adequate and passing - [ ] Documentation updated as needed - [ ] Ready for release --- **Remember**: This is volunteer work. Be patient during the review process.