Bill
08cc6e9ea6
🎉 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
30 lines
887 B
Markdown
30 lines
887 B
Markdown
---
|
|
trigger: always_on
|
|
description: Manifest.json requirements and conventions
|
|
---
|
|
|
|
# Manifest Rules
|
|
|
|
## Required Fields
|
|
|
|
The `manifest.json` must include:
|
|
|
|
- `id` - Plugin ID; for local dev it should match the folder name
|
|
- `name` - Display name
|
|
- `version` - Semantic Versioning `x.y.z`
|
|
- `minAppVersion` - Minimum Obsidian version required
|
|
- `description` - Brief description
|
|
- `isDesktopOnly` - Boolean indicating mobile compatibility
|
|
|
|
## Optional Fields
|
|
|
|
- `author` - Plugin author name
|
|
- `authorUrl` - Author's URL
|
|
- `fundingUrl` - Funding/donation URL (string or map)
|
|
|
|
## Critical Rules
|
|
|
|
- **Never change `id` after release** - Treat it as stable API
|
|
- Keep `minAppVersion` accurate when using newer APIs
|
|
- Use Semantic Versioning for `version` field
|
|
- Canonical requirements: https://github.com/obsidianmd/obsidian-releases/blob/master/.github/workflows/validate-plugin-entry.yml |