Obsidian Gate

An MCP server that opens your Obsidian vault to any AI agent.

npx obsidian-gate init     # point at your vault
npx obsidian-gate          # dashboard on :3100

Your Obsidian vault is your second brain. Your AI agents should be able to use it.

Claude Code, Codex, Cursor — one line of config and your vault becomes an agent-accessible workspace. Every note, every link, every tag. All local, all yours, no cloud.

Try It

# One command to set up
npx obsidian-gate init

# Start the dashboard
npx obsidian-gate
# → http://localhost:3100/dashboard

That's it. Your agents can now read, search, and write to your vault.

Related MCP server: obsidian-mcp

Quick Start

1. Point at your vault

npx obsidian-gate init

You'll be asked for your vault path. Paste it in, get an API key back.

2. Connect your agent

Claude Code — drop this into your MCP config:

{
  "mcpServers": {
    "obsidian": {
      "command": "npx",
      "args": ["obsidian-gate", "--mcp"]
    }
  }
}

Any MCP client over HTTP:

{
  "mcpServers": {
    "obsidian": {
      "type": "http",
      "url": "http://localhost:3100/mcp",
      "headers": { "Authorization": "Bearer sk-your-key" }
    }
  }
}

3. Ask your agent

Try these:

Tools — 9 Operations

Notes are also exposed as MCP resources: obsidian://{vault}/{path}.

CLI

Pricing

14-day free trial on paid plans. No risk. Cancel anytime.

Architecture

┌────────────┐     ┌──────────────────────┐     ┌──────────────┐
│ AI Agent   │────▶│   obsidian-gate      │────▶│  Obsidian    │
│ (Claude,   │◀────│   (MCP Server)       │◀────│  Vault       │
│  Codex,    │     │                      │     │  (files)     │
│  Cursor)   │     │  stdio ─ dashboard   │     └──────────────┘
└────────────┘     └──────────────────────┘

• All local. Every byte lives on your machine. No cloud, no servers, no sync.

• Config in ~/.obsidian-gate/config.json (mode 0600)

• API keys are local secrets. You own the stack.

• Activity log tracks every agent action in JSONL.

What Gate Is Not

• ❌ Not an Obsidian plugin (but a community plugin is planned)

• ❌ Not a sync engine (reads/writes your vault directory directly)

• ❌ Not a note editor (Obsidian is better at that)

• ❌ Not a cloud service (runs entirely on your machine)

It's one small thing done well: an MCP server for your vault.

Roadmap

• MCP server with 9 tools

• Local dashboard + activity log

• API key auth + permissions

• Stripe licensing (free + paid tiers)

• Obsidian community plugin (one-click install)

• Agent write-back with LLM frontmatter

• Auto-tagging from vault content

• Daily digest: what changed in your vault

Development

git clone https://github.com/rileygramlich/obsidian-gate.git
cd obsidian-gate
npm install
npm run build     # compile TypeScript → dist/
npm run dev       # hot-reload with tsx

Built by Riley G. — inspired by the Marc Lou playbook: ship fast, free tier, zero ad spend, build in public.

MIT — build on it, ship it, sell it.