Obsidi MCP
Provides tools for interacting with an Obsidian vault, enabling reading, writing, searching, tagging, linking, and managing notes, as well as CLI bridge for Sync history and file recovery.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Obsidi MCPlist all notes in my daily folder"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Obsidi MCP
Expose Obsidian vault tools via Model Context Protocol (MCP) server.
Features
MCP Server - Serve vault tools over stdio, HTTP (StreamableHTTP), or SSE transports
28+ Built-in Tools - Read, write, search, tag, link, and manage vault notes
CLI Bridge - Obsidian Sync history, file recovery, and diff tools (v1.12+)
Tool Provider Registry - Other plugins register additional tools at runtime
Vault Resources - MCP resource subscriptions with live vault change notifications
Session Persistence - Hot-reload recovery for connected MCP clients
Related MCP server: obsidian-local-mcp
Requirements
Obsidian Desktop (not mobile - uses Node.js features)
Node.js 18+
For CLI bridge: Obsidian CLI v1.12+
Installation
BRAT (Recommended)
Install via BRAT:
Install BRAT from Community Plugins
Add
cameronsjo/obsidi-mcpas a beta pluginEnable Obsidi MCP in Community Plugins
Development
git clone https://github.com/cameronsjo/obsidi-mcp.git
cd obsidi-mcp
npm install
npm run build
# For development with auto-rebuild
npm run devLinking to Obsidian
Create a symlink from your Obsidian vault's plugins folder:
ln -sfn /path/to/obsidi-mcp /path/to/vault/.obsidian/plugins/obsidi-mcpUsage
Enable the plugin in Obsidian Settings > Community Plugins
Configure transport (stdio, HTTP, or SSE) in plugin settings
Connect your MCP client to the server
Connecting Claude Code
For stdio transport, add to your Claude Code MCP config:
{
"mcpServers": {
"obsidian": {
"command": "obsidian",
"args": ["--vault", "Your Vault Name", "--mcp"]
}
}
}For HTTP transport:
{
"mcpServers": {
"obsidian": {
"url": "http://localhost:3000/mcp",
"transport": "streamable-http"
}
}
}Configuration
Open Settings > Obsidi MCP to configure:
Transport: stdio, HTTP (StreamableHTTP), SSE, or stdio + HTTP
HTTP Port: Port for HTTP/SSE server (default: 3000)
Server Name: Name exposed to MCP clients
CLI Bridge: Enable Obsidian CLI tools for Sync history and file recovery
Tools Available
Vault Tools (28)
Category | Tools |
Read |
|
Write |
|
Search |
|
Navigation |
|
Tags |
|
Links |
|
Metadata |
|
Semantic |
|
CLI Bridge Tools (7)
Tool | Description |
| Check Obsidian Sync connection status |
| Get version history for a file |
| Read a specific version of a file |
| Restore a file to a previous version |
| Diff between two versions of a file |
| Get file modification history |
| Read a file at a specific history point |
Plugin Integration
Other plugins can register tools with Obsidi MCP:
// In your plugin's onload()
const mcp = this.app.plugins?.plugins?.['obsidi-mcp'];
if (mcp?.registerToolProvider) {
mcp.registerToolProvider({
id: 'my-plugin',
name: 'My Plugin',
tools: myToolDefinitions,
});
}
// In your plugin's onunload()
const mcp = this.app.plugins?.plugins?.['obsidi-mcp'];
mcp?.unregisterToolProvider?.('my-plugin');Tool providers registered later override built-in tools with the same name, enabling plugins to provide enhanced versions (e.g., RAG-powered search).
Architecture
obsidi-mcp
├── MCPServer (stdio/HTTP/SSE transports)
│ ├── Tool dispatch (dynamic from registry)
│ ├── Vault resources (live subscriptions)
│ ├── Completions (path autocomplete)
│ ├── Elicitation (confirmation dialogs)
│ └── Log forwarding
├── ObsidianTools (28 built-in vault tools)
├── CLI Bridge (7 Obsidian CLI tools)
├── VaultResources (direct app.vault access)
└── Tool Provider Registry
├── Built-in tools (layer 1)
├── CLI bridge tools (layer 2)
└── External providers (layer 3, last wins)Security
The HTTP/SSE server binds to localhost with no authentication, no TLS, and no access control. It is designed for local-only use by MCP clients running on the same machine.
Do not expose the server to a network without a secured reverse proxy. Anyone who can reach the HTTP port has full read/write access to your vault.
If you need remote access, place the server behind a reverse proxy that provides authentication, TLS, rate limiting, and role-based access control (e.g., Caddy, nginx, Cloudflare Tunnel).
Troubleshooting
Server not starting
Check Obsidian's developer console (Cmd+Option+I) for errors. The server status is visible in plugin settings.
CLI bridge not available
Ensure Obsidian CLI is installed (v1.12+):
obsidian --versionPort already in use
Change the HTTP port in plugin settings if port 3000 is occupied.
License
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cameronsjo/obsidi-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server