obsidian-companion-mcp

A hybrid Model Context Protocol (MCP) ecosystem for Obsidian, providing vault-wide semantic intelligence and real-time editor context awareness.

• Multilingual Semantic Search: Powered by intfloat/multilingual-e5-small, allowing high-precision search across Japanese, English, and 100+ other languages.
• Real-time Editor Context: AI awareness of the active file, cursor position, and text selection.
• Smart Note Management: Precise CRUD operations for Markdown files and Frontmatter.
• Local-First Architecture: All embeddings and indexing are performed locally on your machine for maximum privacy.

The public MCP surface is organized around the actual agent workflow:

1. Discover candidate notes

• list_notes
• search_notes
• semantic_search_notes
• get_semantic_index_status
• refresh_semantic_index

1. Read persisted notes or the active editor

• read_note
• read_active_context

1. Apply one structured edit tool

• edit_note

1. Use lifecycle / metadata tools when needed

• create_note
• patch_note_metadata
• move_note
• delete_note

read_note and read_active_context both return machine-readable edit handoff payloads so agents can move from read to edit without reconstructing anchors manually.

For long persisted notes, prefer read_note with anchor.type = "line" and follow readMoreHint to walk the document in stable line windows. For active editor buffers, rerun read_active_context with the same or a larger maxChars instead of relying on continuation hints, because the unsaved buffer can change between reads.

To use Obsidian Companion MCP, you need to set up both the Obsidian plugin and the MCP server.

1. Manual Install: Copy the contents of dist/plugin-release (after running just build) to your vault's .obsidian/plugins/companion-mcp/ directory.
2. Enable: Go