🎉 Initial release of Obsidian MCP Server plugin
Core Features:
- MCP server implementation with HTTP transport
- JSON-RPC 2.0 message handling
- Protocol version 2024-11-05 support
MCP Tools:
- read_note, create_note, update_note, delete_note
- search_notes, list_notes, get_vault_info
Server Features:
- Configurable HTTP server (default port: 3000)
- Health check and MCP endpoints
- Auto-start option
Security:
- Origin header validation (DNS rebinding protection)
- Optional Bearer token authentication
- CORS configuration
UI:
- Settings panel with full configuration
- Status bar indicator and ribbon icon
- Start/Stop/Restart commands
Documentation:
- Comprehensive README with examples
- Quick Start Guide and Implementation Summary
- Test client script
938 B
938 B
trigger, description
| trigger | description |
|---|---|
| always_on | Versioning and release process |
Versioning & Releases
Version Management
- Bump
versioninmanifest.jsonusing Semantic Versioning (SemVer) - Update
versions.jsonto map plugin version → minimum app version - Keep version numbers consistent across all release artifacts
Release Process
- Create GitHub release with tag that exactly matches
manifest.json'sversion- Do not use a leading
vin the tag
- Do not use a leading
- Attach required assets to the release:
manifest.jsonmain.jsstyles.css(if present)
- After initial release, follow the process to add/update your plugin in the community catalog
Testing Before Release
Manual install for testing:
- Copy
main.js,manifest.json,styles.css(if any) to:<Vault>/.obsidian/plugins/<plugin-id>/ - Reload Obsidian
- Enable the plugin in Settings → Community plugins