Your notes, articles, and podcasts turned into a connected graph Claude can query, plus a second, separate graph that audits Cloze's help center for contradictions.
graphify reads the source material, extracts concepts and their relationships, de-duplicates, and writes one graph.json that several consumers read.
Same engine (graphify), two independent corpora, two MCP servers. Kept fully separate by design.
The graph is exposed as a read-only MCP server, so any Claude session can ask it questions. No tokens, no network, just the local graph.
Fetch a concept and everything known about it.
What's directly connected to a concept.
Search the whole graph by topic or term.
How two ideas connect, step by step.
Pull a whole cluster of related notes.
The most-connected hubs. Your core themes.
The size and shape of the graph at a glance.
cloze-audit surfaces contradictions, coverage gaps, and redundant articles with sourced quotes.
You run /graphify --update by hand. It's Max-covered (no metered cost) and keeps a human in the loop, which matters because Brain ingests untrusted web text, an injection surface an unattended agent shouldn't touch.
A canonicalization step merges duplicate concepts so the graph stays clean as new material lands.
An agent-crawlable wiki (1,261 files) rebuilds itself whenever the graph changes. Pure-local, no token cost.
Building the graph costs (supervised). Querying it doesn't. The MCP server reads the local file, so every Claude session gets the graph for $0.