obsidian-vault-mcp
Reads and writes notes stored in GitHub repositories, using immutable tree snapshots and Git blob SHA-based optimistic concurrency for safe updates.
Provides tools for browsing, searching, reading, and analyzing an Obsidian vault, including notes, links, backlinks, tags, aliases, embeds, and the note graph.
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., "@obsidian-vault-mcpFind the shortest path between 'MCP' and 'Obsidian' in my vault"
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.
Obsidian Vault MCP
A self-hosted Model Context Protocol server for private Obsidian vaults stored in GitHub. It runs on Cloudflare Workers, authenticates the vault owner with OAuth 2.1, and exposes Markdown notes, an Obsidian-compatible link graph, and a durable event stream for vault automations.
The same Worker also serves an optional private web portal with a vault switcher, Markdown reader, content search, an interactive Graph Explorer, an ephemeral read-only AI chat with verified note citations, and callback-driven vault snapshots to Google Drive.
The server does not run Obsidian. It derives links, backlinks, aliases, tags, embeds, unresolved references, and shortest paths from an immutable GitHub tree snapshot.
Security model
The default deployment is deliberately single-owner:
One immutable GitHub user ID may authorize MCP clients.
Only repositories in
GITHUB_REPOSITORIESare addressable.A fine-grained GitHub token must be restricted to exactly those repositories.
Each MCP client requires an explicit consent screen after GitHub login.
Read-only deployments do not register the write tool.
Writable deployments require
vault:write; updates use the current Git blob SHA and reject stale or blind overwrites.Secrets stay in Cloudflare and are never part of this repository.
Do not add unrelated users to a deployment backed by one shared token. See Multi-user architecture for the correct isolation model.
Related MCP server: Obsidian MCP (pgvector + Ollama, self-hosted)
Tools
Tool | Purpose |
| List explicitly configured vault repositories. |
| Browse visible Markdown paths. |
| Search note contents through GitHub. |
| Read one Markdown note with its current SHA. |
| Create or safely replace a note; available only in write mode. |
| Resolve outgoing links, embeds, backlinks, and broken references. |
| Page through nodes, edges, tags, aliases, and orphans. |
| Find a deterministic shortest path between notes. |
| Inspect canonical note-created, updated, and deleted events. |
| Inspect the server's configured internal automations. |
| Inspect automation attempts and outcomes. |
Deploy your own instance
Follow the complete self-hosting guide. The short version is:
Fork this repository.
Create Cloudflare KV, D1, and Queues resources plus an OAuth App on GitHub.
Create a fine-grained GitHub token restricted to selected vault repositories.
Copy
wrangler.example.jsoncto the ignoredwrangler.jsoncand enter only non-secret deployment values.Upload the four base runtime secrets to Cloudflare, apply the D1 migrations, and deploy. Add
OPENAI_API_KEYonly when enabling an AI automation.Connect an MCP client to
https://your-host/mcpand approve its consent screen.After the manual deployment passes its smoke tests, connect Cloudflare Workers Builds to the fork or enable the protected GitHub Actions alternative.
Web portal
The root URL serves the portal. It reuses the GitHub OAuth callback but has its own host-only browser session; MCP bearer grants are never exposed to frontend JavaScript. The browser receives neither GitHub credentials nor the OpenAI API key.
Configure chat with a Worker secret and optional non-secret settings:
bunx wrangler secret put OPENAI_API_KEYChat enables automatically when
OPENAI_API_KEYexists. SetWEB_CHAT_ENABLED=falseto turn it off explicitly, ortrueto make a missing secret fail the health check.OPENAI_CHAT_MODELselects the default amonggpt-5.6-sol,gpt-5.6-terra, andgpt-5.6-luna; users can choose the model and reasoning level per conversation.WEB_CHAT_DAILY_LIMITdefaults to50requests per GitHub user per UTC day.Chat history stays in browser memory. Prompt, note text, and answers are not stored in D1.
A read-only agent can search, read exact note revisions, and inspect the graph within one selected vault or note. The UI shows its tool activity and aggregate token usage; every citation is checked against retrieved evidence.
See Web portal and vault chat for the API, privacy model, and current multi-user boundary.
The portal's Graph Explorer filters notes by path or tag, shows incoming and outgoing link counts, and finds bounded shortest connection trails without exposing note bodies to the browser graph response.
Vault sync callbacks
The portal can connect a selected vault to Google Drive. GitHub remains canonical: every detected revision queues a coalesced internal callback that uploads a complete repository ZIP (notes, attachments, and .obsidian settings) into an app-created Drive folder. The integration requests only the non-sensitive drive.file scope, so it cannot browse unrelated Drive content.
Set GOOGLE_CLIENT_ID as a Worker variable and upload GOOGLE_CLIENT_SECRET plus a random 32-byte SYNC_CREDENTIALS_KEY as Worker secrets. Register https://your-host/api/sync/google/callback as the exact Google OAuth redirect URI. See Vault sync destinations for setup, encryption, retries, and the iCloud boundary.
Development
bun install --frozen-lockfile
bun run checkbun run check runs strict TypeScript, 80+ unit tests, a production dependency audit, and a Wrangler bundle dry-run. CI runs the same command without deployment credentials.
For local Worker development, bun run dev builds the portal and applies local D1 migrations before starting Wrangler. bun run web:dev provides frontend HMR and proxies API/auth routes to Wrangler on port 8787; use a separate development GitHub OAuth App whose callback points at your local origin, or test the authenticated flow on a preview deployment.
Limits
Up to 1,000 Markdown notes and 8 MB of Markdown source per graph snapshot.
Up to 512 KB per note.
Graph data is cached by repository and immutable Git tree revision for five minutes.
Hidden paths and non-Markdown files are never exposed as notes.
Writes create Git commits; rename and delete operations are intentionally unavailable.
GitHub is canonical: pushes made by Obsidian, the MCP, GitHub's UI, or another Git client produce the same events.
Automation handlers are internal and explicitly configured;
summarize-notewrites only managed summaries, while authenticated sync destinations reuse the durable callback queue. Arbitrary outbound callback URLs are not supported.One repository receives immediate webhook delivery per deployment; every allowlisted vault is still reconciled on the fifteen-minute schedule.
See Vault events and automations for delivery, filtering, retries, and the write-loop policy.
Project status
The personal self-hosted model is implemented. Shared multi-user hosting is a separate design and requires a GitHub App installation per tenant; it is not enabled by this codebase today.
See Security, security model, and contributing.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityCmaintenanceLocal-first MCP server for Obsidian vaults with 66 tools for reading, writing, searching, and managing notes, tasks, graphs, and more. Works without Obsidian running and requires no plugins.66MIT
- AlicenseAqualityAmaintenanceSelf-hosted MCP server for Obsidian with semantic + full-text search over PostgreSQL/pgvector, wikilink graph traversal, atomic note CRUD, OAuth 2.0, and a self-describing vault guide.208MIT
- Flicense-qualityBmaintenanceSelf-hosted MCP server that provides remote AI clients with read and write access to Obsidian vaults over HTTPS without needing the Obsidian desktop app running.2
- Alicense-qualityBmaintenanceSelf-hosted MCP server that provides embedding-powered semantic search with graph context over Obsidian vaults, supporting multiple vaults, local embeddings, and a web dashboard.MIT
Related MCP Connectors
Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers.
Markdown-first MCP server for Notion API with 8 composite tools and 39 actions.
An MCP server that gives your AI access to the source code and docs of all public github repos
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/santiagopoli/obsidian-vault-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server