brainmaxxing
a three-tier knowledge pipeline for AI agents
Raw sources go in, compiled wiki pages come out, generated artifacts build on top. The knowledge doesn't decay — it compounds.
Install
npm install -g brainmaxxing
brainmaxxing setup
The setup wizard walks you through 4 steps:
- Knowledge base mode — global wiki, project-specific (
.wiki/ per repo), or both (default)
- Storage location — auto-detects Obsidian vaults, or pick a custom path. Defaults to
~/.brainmaxxing/wiki
- Search engine —
fts (BM25, no download, default) or hybrid (BM25 + ~2GB vector model)
- Register MCP server with Claude Code — say yes. Writes
brainmaxxing into ~/.claude.json
Install the Claude Code plugin (optional)
Adds /wiki:* slash commands on top of the MCP tools. Run each command separately — pasting all at once breaks /plugin since it takes the whole line as arguments:
/plugin marketplace add ShahriarBijoy/brainmaxxing
/plugin install brainmaxxing@brainmaxxing
Then restart Claude Code so the plugin loads.
Prefer the UI? Run /plugin and use the Marketplaces and Discover tabs.
Verify
/mcp
You should see brainmaxxing listed as connected. If not, restart Claude Code.
Quick start
Just talk to Claude — it calls the MCP tools for you:
You: dump ~/papers/attention-is-all-you-need.pdf into my wiki
You: cook a page about the transformer architecture from that paper
You: lookup "attention mechanism"
You: what does my wiki currently contain?
You: check the health of my knowledge graph
Or use the plugin's workflow commands:
/wiki:setup # interactive walkthrough
/wiki:research RLHF # full pipeline: web search → raw → wiki → output
/wiki:ingest # process anything sitting in raw/
/wiki:query "what do I know about reward hacking?"
/wiki:lint # graph health check with fix suggestions
/wiki:compile # synthesize wiki pages into an output document
Dashboard
Auto-starts with the MCP server at http://localhost:6969 (force graph, page browser, graph health). To launch standalone:
brainmaxxing web
MCP tools
14 tools across three tiers. All data-only — no internal LLM calls, no API key needed. The host agent does its own reasoning.
Wiki tier
| Tool | What it does |
|---|
recall | Read a wiki page by slug |
cook | Create/update a page with typed relationships |
lookup | Search pages (BM25 via FTS5, or hybrid BM25 + qmd vector ranking) |
shelf | List all pages |
inventory | Full manifest with metadata and relationships |
vibes | Graph health check: orphans, contradictions, broken links |
yap | Append to the operation log |
tidy | Regenerate the index page |
status | System health across all three tiers |
Raw tier
| Tool | What it does |
|---|
dump | Add a file to raw/ for later processing |
stash | List raw files with processing status |
Output tier
| Tool | What it does |
|---|
drop | Write a generated artifact to output/ |
receipts | List outputs with citation and promotion status |
glow_up | Promote an output to a full wiki page |
All tools accept scope: "auto" (default), "global", "project", or "all".
Plugin skills
| Skill | Workflow |
|---|
/wiki:setup | Interactive setup wizard |
/wiki:research | Full pipeline: web search → raw/ → wiki/ → output/ |
/wiki:ingest | Process raw/ files into wiki/ pages |
/wiki:query | Answer questions from wiki/, save to output/ |
/wiki:lint | Graph health check with fix suggestions |
/wiki:compile | Synthesize wiki/ pages into output/ documents |
How it works
Three folders:
your-wiki/
raw/ ← Dump anything here. PDFs, articles, notes.
wiki/ ← Compiled knowledge. Agent-organized, interconnected.
output/ ← Generated artifacts. Reports, answers, analyses.
The agent reads from raw/, writes structured pages to wiki/ with typed semantic relationships, and generates research outputs that cite wiki pages. When an output is good enough, it gets promoted back into the wiki with glow_up.
Research orchestration
