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
16 lines
596 B
Markdown
16 lines
596 B
Markdown
---
|
|
trigger: always_on
|
|
description: Obsidian plugin project structure and requirements
|
|
---
|
|
|
|
# Project Overview
|
|
|
|
- **Target**: Obsidian Community Plugin (TypeScript → bundled JavaScript)
|
|
- **Entry point**: `main.ts` compiled to `main.js` and loaded by Obsidian
|
|
- **Required release artifacts**: `main.js`, `manifest.json`, and optional `styles.css`
|
|
|
|
## Key Requirements
|
|
|
|
- All TypeScript code must be bundled into a single `main.js` file
|
|
- Release artifacts must be placed at the top level of the plugin folder
|
|
- Never commit build artifacts (`node_modules/`, `main.js`, etc.) to version control |