Obsidian Vault MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 162 installs a week from npm. Last commit 25 Oct 2026.
Access Obsidian vaults via Local REST API - read, search, and interact with notes
What the code does
We read the source, 21 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.
postinstall: bun run build
execSync(`bash "${scriptPath}"`, { stdio: "inherit" })
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
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.
Connect this server
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 mcp-obsidian-via-rest -e 'API_KEY=<API_KEY>' -e 'API_URLS=<API_URLS>' -- npx -y @oleksandrkucherenko/mcp-obsidian{
"mcpServers": {
"mcp-obsidian-via-rest": {
"command": "npx",
"args": [
"-y",
"@oleksandrkucherenko/mcp-obsidian"
],
"env": {
"API_KEY": "<API_KEY>",
"API_URLS": "<API_URLS>"
}
}
}
}[mcp_servers.mcp-obsidian-via-rest]
command = "npx"
args = ["-y", "@oleksandrkucherenko/mcp-obsidian"]
env = { API_KEY = "<API_KEY>", API_URLS = "<API_URLS>" }{
"mcpServers": {
"mcp-obsidian-via-rest": {
"command": "npx",
"args": [
"-y",
"@oleksandrkucherenko/mcp-obsidian"
],
"env": {
"API_KEY": "<API_KEY>",
"API_URLS": "<API_URLS>"
}
}
}
}{
"servers": {
"mcp-obsidian-via-rest": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@oleksandrkucherenko/mcp-obsidian"
],
"env": {
"API_KEY": "<API_KEY>",
"API_URLS": "<API_URLS>"
}
}
}
}Put your own values in place of
<API_KEY> (Obsidian Local REST API key), <API_URLS> (JSON array or semicolon-separated list of Obsidian REST API URLs for failover).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
MCP_TRANSPORTS (Enabled transports (default: stdio,http)), MCP_HTTP_PORT (HTTP transport bind port (default: 3000)), MCP_HTTP_HOST (HTTP transport bind host (default: 0.0.0.0)), MCP_HTTP_TOKEN (Bearer token for HTTP transport authentication).
Alternatives to Obsidian Vault MCP Server
same job, measured the same wayFilesystem-based MCP server for Obsidian vaults — read, search, and edit notes, no app required.
Local MCP server for tasks and notes in any Markdown folder or Obsidian vault. No account needed.
MCP server for AI agent read/write access to Obsidian vaults via EVC Team Relay.
Read, write, search, and surgically edit Obsidian notes, tags, and frontmatter via MCP.
Read-only semantic search MCP server for Obsidian vaults using local Ollama embeddings.
Filesystem-direct Obsidian MCP server — search and edit your vault with low context-tax.
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.
Obsidian Vault MCP Server — questions
Answers built from our own checks of this server.