gosidian runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 3 Nov 2026.
Self-hosted Obsidian-compatible markdown vault with a web UI and a 71-tool MCP server for AI agents
We read the source, 3 d 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.
target := filepath.Join(targetDir, name)
delete this.byProject[project]
},
invalidateAll() {
epoch++
if (refreshTimer) {
.nodeVal(nodeVal)
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.
Self-hosted agent memory as a markdown vault: semantic and keyword search, wikilink graph, OAuth
Self-host your Obsidian vaults: a web UI for you, MCP for your AI agents. No Obsidian, no plugins.
MCP server for Obsidian vaults - AI tools with consistent canonical context. Local-first.
Self-hosted multi-user memory for AI agents: a human-readable Markdown wiki with per-fragment ACL.
Local MCP server for tasks and notes in any Markdown folder or Obsidian vault. No account needed.
Local Markdown/Obsidian knowledge substrate for MCP agents with governed memory and hybrid search.
MCP server for AI agent read/write access to Obsidian vaults via EVC Team Relay.
Give AI agents access to your Obsidian vault via local files or Self-hosted LiveSync.
Answers built from our own checks of this server.