Obsidian MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 2 Sep 2026.
Filesystem-based MCP server for Obsidian vaults — read, search, and edit notes, no app required.
We read the source, 16 h ago · rules 3dff92dd89df
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.
- name: Update release notes
env:
GH_TOKEN: ${{ github.token }}
certPath := filepath.Join(dir, certFileName)
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.
Filesystem-direct Obsidian MCP server — search and edit your vault with low context-tax.
Obsidian MCP server: semantic search, knowledge graph, and vault editing. No plugin required.
Access Obsidian vaults via Local REST API - read, search, and interact with notes
Read, write, search, and surgically edit Obsidian notes, tags, and frontmatter via MCP.
Standalone MCP server for Obsidian vaults — hybrid search, notes & files, memory, tasks, OAuth 2.1
Read-only semantic search MCP server for Obsidian vaults using local Ollama embeddings.
MCP server for AI agent read/write access to Obsidian vaults via EVC Team Relay.
Complete Obsidian vault MCP server. 35 tools: notes, search, graph, tags, canvas.
Answers built from our own checks of this server.