Give AI agents access to your Obsidian vault via local files or Self-hosted LiveSync.
Obsidian MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Give AI agents access to your Obsidian vault via local files or Self-hosted LiveSync.
Give any AI agent access to your Obsidian vault over MCP. Run it locally against your vault files, or pair it with Self-hosted LiveSync and deploy to the cloud so it works even when your machine is off.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Obsidian is connected, these are the calls the assistant has available:
read_note — Read a note's markdown content by pathwrite_note — Create or overwrite a note (replaces entire content)edit_note — Edit a note without rewriting it — append, prepend (after frontmatter), or replace exact textlist_folders — List all folders in the vault with note counts — use to discover folder nameslist_tags — List all tags in the vault with counts — use to discover tags before filteringlist_notes — List notes with timestamps. Filter by folder, name, tag, or date. Sort by name or modifieddelete_note — Delete a notemove_note — Move or rename a note — works across folders, creates destination folders automaticallyget_note_metadata — Get frontmatter, tags, outgoing links, backlinks, size, and timestamps — navigate the knowledge graphYou will need 4 environment variables: COUCHDB_URL, MCP_AUTH_TOKEN, BASE_URL, VAULT_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Obsidian's toolset — read_note, write_note, edit_note and 6 more — is a fair guide to whether it matches your workflow. It is maintained by es617; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| read_note | Read a note's markdown content by path |
| write_note | Create or overwrite a note (replaces entire content) |
| edit_note | Edit a note without rewriting it — append, prepend (after frontmatter), or replace exact text |
| list_folders | List all folders in the vault with note counts — use to discover folder names |
| list_tags | List all tags in the vault with counts — use to discover tags before filtering |
| list_notes | List notes with timestamps. Filter by folder, name, tag, or date. Sort by name or modified. |
| delete_note | Delete a note |
| move_note | Move or rename a note — works across folders, creates destination folders automatically |
| get_note_metadata | Get frontmatter, tags, outgoing links, backlinks, size, and timestamps — navigate the knowledge graph |
{
"mcpServers": {
"obsidian-sync": {
"command": "npx",
"args": ["-y", "obsidian-sync-mcp"],
"env": {
"COUCHDB_URL": "your-value",
"MCP_AUTH_TOKEN": "your-value",
"BASE_URL": "your-value",
"VAULT_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| COUCHDB_URL | Endpoint or connection string the server talks to. | Yes |
| MCP_AUTH_TOKEN | Credential the server authenticates with. | Yes |
| BASE_URL | Endpoint or connection string the server talks to. | Yes |
| VAULT_PATH | Filesystem location the server is allowed to use. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.