Hatchdoor runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 27 Oct 2026.
Self-host your Obsidian vaults: a web UI for you, MCP for your AI agents. No Obsidian, no plugins.
What the code does
We read the source, 5 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.
const update = () => {
const hidden =
window.innerHeight - (viewport.height + viewport.offsetTop);
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.
Alternatives to Hatchdoor
same job, measured the same waySelf-hosted Obsidian-compatible markdown vault with a web UI and a 71-tool MCP server for AI agents
Give AI agents access to your Obsidian vault via local files or Self-hosted LiveSync.
Long-term memory for AI agents — your Obsidian vault as searchable persistent memory.
MCP server for AI agent read/write access to Obsidian vaults via EVC Team Relay.
MCP server for Obsidian vaults - AI tools with consistent canonical context. Local-first.
AI agents use your Obsidian secrets by name — values never reach their context.
Your Obsidian vault as private, searchable memory for Claude, Cursor, Hermes and any MCP client
MCP server for Obsidian Smart Connections. Semantic search using your vault's embeddings.
Hatchdoor — questions
Answers built from our own checks of this server.