Obsidian Sync MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 154 installs a week from npm. Last commit 1 Nov 2026.
Give AI agents access to your Obsidian vault via local files or Self-hosted LiveSync.
We read the source, 23 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const full = path.join(base, rel);
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
# The base image runs as the unprivileged `node` user, but Fly volumes are # mounted root-owned at /data, so keep root here to stay able to write to it. USER root
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add obsidian-sync-mcp -- npx -y obsidian-sync-mcp
{
"mcpServers": {
"obsidian-sync-mcp": {
"command": "npx",
"args": [
"-y",
"obsidian-sync-mcp"
]
}
}
}
[mcp_servers.obsidian-sync-mcp]
command = "npx"
args = ["-y", "obsidian-sync-mcp"]
{
"mcpServers": {
"obsidian-sync-mcp": {
"command": "npx",
"args": [
"-y",
"obsidian-sync-mcp"
]
}
}
}
{
"servers": {
"obsidian-sync-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"obsidian-sync-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
VAULT_PATH (Path to your Obsidian vault directory (filesystem mode)), COUCHDB_URL (CouchDB server URL (CouchDB mode)), COUCHDB_USER (CouchDB username), COUCHDB_PASSWORD (CouchDB password (required in CouchDB mode)), COUCHDB_DATABASE (CouchDB database name), COUCHDB_PASSPHRASE (LiveSync E2E encryption passphrase (must match plugin setting)), COUCHDB_OBFUSCATE_PROPERTIES (Set to 'true' if 'Obfuscate Properties' is enabled in LiveSync (obfuscates file paths, sizes, dates)), VAULT_NAME (Vault name for deep links and index storage), MCP_AUTH_TOKEN (Password for OAuth authentication), BASE_URL (Public URL for OAuth callbacks (required when using a tunnel)), PORT (HTTP port).
Self-host your Obsidian vaults: a web UI for you, MCP for your AI agents. No Obsidian, no plugins.
MCP server for AI agent read/write access to Obsidian vaults via EVC Team Relay.
Long-term memory for AI agents — your Obsidian vault as searchable persistent memory.
Self-hosted Obsidian-compatible markdown vault with a web UI and a 71-tool MCP server for AI agents
Access Obsidian vaults via Local REST API - read, search, and interact with notes
On-demand Obsidian vault access for AI coding assistants — 17 tools, 5 resources, 4 prompts.
MCP server for Obsidian vaults - AI tools with consistent canonical context. Local-first.
Local-first MCP server: Claude searches, asks & drafts from your Obsidian vault. 21 tools, no keys.
Answers built from our own checks of this server.