Enterprise DNA
M MCP Servers Developer low

bitbonsai/mcp-obsidian

by Various

A lightweight Model Context Protocol (MCP) server for safe Obsidian vault access

B

MCP

bitbonsai/mcp-obsidian

Added 1 June 2026

Overview

A lightweight server implementing the Model Context Protocol (MCP) to provide safe read and write access to Obsidian vaults. It allows large language models and AI agents to interact with notes and files within a vault while preventing accidental corruption. The server runs locally and exposes vault contents through a standardized MCP interface.

Best for

Best for
Developers integrating AI agents with Obsidian notes while maintaining vault integrity

Use cases

  • Let LLMs retrieve Obsidian notes as context for conversations
  • Automate note creation and organization from AI agent workflows
  • Provide sandboxed access to vault files for external tools

Notes

A lightweight server implementing the Model Context Protocol (MCP) to provide safe read and write access to Obsidian vaults. It allows large language models and AI agents to interact with notes and files within a vault while preventing accidental corruption. The server runs locally and exposes vault contents through a standardized MCP interface.

1,336 stars on GitHub. Last updated 2026-05-25.

Use cases

  • Let LLMs retrieve Obsidian notes as context for conversations
  • Automate note creation and organization from AI agent workflows
  • Provide sandboxed access to vault files for external tools

Pros

  • Lightweight and easy to set up
  • Designed for safe access to avoid vault corruption
  • Uses the standard MCP protocol for broad tool compatibility

Cons

  • Requires Obsidian vault and MCP client configuration
  • May not support all Obsidian features like attachments or canvas
  • Limited to local machine deployment by default

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Lightweight and easy to set up
  • Designed for safe access to avoid vault corruption
  • Uses the standard MCP protocol for broad tool compatibility

Cons

  • Requires Obsidian vault and MCP client configuration
  • May not support all Obsidian features like attachments or canvas
  • Limited to local machine deployment by default