obsidian-mcp-server
Gives Claude direct access to an Obsidian vault, enabling read, write, search, and automatic git sync for cross-device use.
README
obsidian-mcp-server
An MCP server that gives Claude direct access to your Obsidian vault — read, write, search, daily notes, tags, backlinks, frontmatter, and automatic git sync so your vault stays up to date across every device.
Tools
| Tool | Description |
|---|---|
obsidian_read |
Read a note by path |
obsidian_write |
Create or overwrite a note (auto git push) |
obsidian_append |
Append to a note (auto git push) |
obsidian_delete |
Delete a note (auto git push) |
obsidian_move |
Move or rename a note (auto git push) |
obsidian_list |
List all notes or a subdirectory |
obsidian_search |
Full-text search with context |
obsidian_find |
Fuzzy search notes by title |
obsidian_tags |
Tag index — all tags and the notes that use them |
obsidian_query |
Find notes by frontmatter field (e.g. status: in-progress) |
obsidian_today |
Get or create today's daily note |
obsidian_template |
Create a note from a template |
obsidian_frontmatter |
Read or update YAML frontmatter |
obsidian_links |
Outgoing wikilinks + incoming backlinks |
obsidian_pull |
Pull latest from git |
obsidian_push |
Manually commit and push all changes |
Setup
Prerequisites
- Node.js 18+
- A GitHub account
- Your Obsidian vault on your local machine
0. Set up your vault as a git repo
If your vault isn't already on GitHub, do this once:
cd "/path/to/your/Obsidian Vault"
git init
git branch -m main
git add -A
git commit -m "initial commit"
Then create a repo on GitHub (private recommended) and link it:
gh repo create my-obsidian-vault --private --source=. --remote=origin --push
# or without the GitHub CLI:
git remote add origin https://github.com/yourusername/my-obsidian-vault.git
git push -u origin main
On any other device, just clone it:
git clone https://github.com/yourusername/my-obsidian-vault.git "/path/to/vault"
1. Clone and install
git clone https://github.com/aumsuthar/obsidian-mcp-server.git
cd obsidian-mcp-server
npm install
npm run build
2. Configure environment
cp .env.example .env
Edit .env and set OBSIDIAN_VAULT_PATH to the absolute path of your vault on this device:
OBSIDIAN_VAULT_PATH="/Users/you/Documents/My Vault"
That's the only required variable. See .env.example for optional settings (daily notes format, auto-sync intervals, etc.).
3. Register with Claude
Add to ~/.mcp.json:
{
"mcpServers": {
"obsidian": {
"command": "node",
"args": [
"--env-file=/path/to/obsidian-mcp-server/.env",
"/path/to/obsidian-mcp-server/dist/index.js"
]
}
}
}
Restart Claude Code or Claude Desktop to pick it up.
Cross-device sync
Your vault path is set per-device in .env — so on each machine you just clone the vault repo, clone this repo, set OBSIDIAN_VAULT_PATH in .env, and you're done. The vault content stays in sync via git.
Workflow:
- On device A: Claude writes a note → auto-commits and pushes to GitHub
- On device B: call
obsidian_pull(or setOBSIDIAN_AUTO_PULL_MINUTES) before reading
Auto-sync
Set these in .env to sync automatically in the background:
OBSIDIAN_AUTO_PUSH_MINUTES=5 # commit and push every 5 minutes if there are changes
OBSIDIAN_AUTO_PULL_MINUTES=5 # pull every 5 minutes
Daily notes
obsidian_today creates a daily note in the Daily/ folder using the YYYY-MM-DD format by default.
To customize:
OBSIDIAN_DAILY_DIR="Journal"
OBSIDIAN_DAILY_FORMAT="YYYY/MM/YYYY-MM-DD"
If a Templates/Daily.md exists in your vault, it will be used as the template. Supported variables: {{date}}, {{title}}.
Templates
Put .md files in your vault's Templates/ folder (configurable via OBSIDIAN_TEMPLATES_DIR). Call obsidian_template with the template name and any variables to substitute.
Example template Templates/Meeting.md:
---
date: {{date}}
type: meeting
---
# {{title}}
## Attendees
## Notes
## Action items
Development
npm run dev # run with tsx (no build needed, loads .env)
npm run build # compile to dist/
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.