Local-first knowledge graph that powers AGNT's wiki and memory layer.
Obsidian + AGNT
Local-first knowledge graph that powers AGNT's wiki and memory layer.
Official sourceWhat it is
Obsidian is a local-first, Markdown-based knowledge management app with a plugin ecosystem, graph view, and backlinks. It stores everything as plain .md files — no vendor lock-in, full Git compatibility.
The graph view and backlinks make it the natural home for interconnected knowledge: agent profiles, venue data, architecture decisions, daily logs, and meeting notes all become nodes in a navigable graph.
Where AGNT fits
- AGNT's entire internal wiki runs on Obsidian. The 149-venue directory, 24 agent profiles, architecture decisions, and daily operations logs are all Obsidian vaults synced bidirectionally with the database via `scripts/wiki/sync-venues-from-db.py`.
- The MCP server at `/mcp/sse` exposes wiki content to any MCP-compatible client — Claude Code, Cursor, or Windsurf can query AGNT's Obsidian vault as structured tools without leaving the IDE.
- Fleet memory (`agnt-fleet/memory/`) writes decision records and daily logs as Obsidian-compatible Markdown, so operational knowledge flows from agent runtime → Obsidian → public docs without manual copying.
Integration recipes
Sync AGNT wiki with Obsidian bidirectionally
Set up the venue-sync script to keep your local Obsidian vault and AGNT's database in sync.
Build an MCP server exposing AGNT wiki + graph
Ship a custom MCP server wrapping AGNT's wiki + graph endpoints, callable from any MCP client.
Wire AGNT memory into Claude Code as an MCP server
Query your Obsidian-backed AGNT memory from Claude Code via MCP.
Prompts & playbooks
Links
Share as social post
AGNT + Obsidian: Local-first knowledge graph that powers AGNT's wiki and memory layer. https://agntdot.com/stack/obsidian
122 / 280 chars