Head to head

ArgosBrain vs Obsidian + MCP

Obsidian is a second brain for humans. ArgosBrain is a second brain for coding agents.

What Obsidian + MCP does

PKM vault of MD notes exposed to agents via an Obsidian MCP server.

What ArgosBrain does differently

Symbol-level retrieval about the code itself, not prose around the code.

What Obsidian + MCP is

The baseline, stated fairly.

Developers write notes in Obsidian (plugins: Smart Connections — local embeddings + chat over vault, ~2.5k stars; Copilot for Obsidian — hybrid keyword+vector RAG, ~4.5k stars). Claude Code / Cursor read the vault via an Obsidian MCP server (e.g. MarkusPfundstein/mcp-obsidian, ~800 stars) that wraps the Local REST API plugin, exposing search_notes, get_file_contents, append_content, patch_content as tools.

How it actually works

Technical facts.

StorageMD files in the vault.
RetrievalMCP tool call returns full note bodies (no ranking beyond filename/full-text match).
Cost~3–8k prompt tokens per query (full notes returned).
LimitationsChunks are paragraph-level not symbol-level; no file-hash check when code changes; PKM audience, not primarily coding agents.

Verdict

Where each one wins.

↑ Where ArgosBrain wins

Symbol-level retrieval vs full-note dump.
$0 tokens vs 3–8k per query.
Automatic staleness — Obsidian notes about code go stale silently.
Designed for code — Obsidian is for humans writing prose.

↑ Where Obsidian + MCP wins

Mature PKM — if you already live in a vault, the workflow is familiar.
Markdown is human-readable and portable.
Hybrid note-taking + agent memory is a use case we don't cover.

When to choose which

Honest recommendation.

Choose Obsidian + MCP if

You already have a vault of design docs
You want agents to read them

Choose ArgosBrain if

You want memory about the code itself
Both: Obsidian for docs, ArgosBrain for code structure — they stack