Booboo
About
Query your AI system's wiring, knowledge, memory, agents and crons as one rooted graph over MCP, with a live 3D viewer.
Explore
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
BoobooCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"booboo": {
"server": {
"command": "npx",
"args": [
"-y",
"@booboo-brain/cli",
"mcp"
]
}
}
}
}McpServers
{
"server": {
"command": "npx",
"args": [
"-y",
"@booboo-brain/cli",
"mcp"
]
}
}Transport
"stdio"Package
"@booboo-brain/cli"Registry
"npm"Turn any AI system's data into one living, rooted 3D brain —structure + knowledge + memory + agents + automationsfused into a single graph. Query it byREST or MCP, view it in yourbrowser or as a desktop wallpaper, andboot your agents from it in one call.
See it before you install it →booboo.fractionalhq.uk· a live brain in your browser, no signup, nothing to clone.
Named after a dachshund who never forgets where the treats are buried. Fitting, because Booboo is about exactly that:memory and recall— seeing the whole system at once, fetching what's buried, never losing the thread.
Unretouched:booboo view --demo --nodes 50000— 50k nodes, 4 layers, live in a browser tab, zero console errors. Try it yourself in one command.
Most tools show youoneslice: a knowledge graph, an agent flow chart, a memory store, a trace viewer. Booboo fuses all of them intoone graph rooted at a single point, so you can see — and query — how the whole system actually hangs together.
Status:alpha — eight packages published:@booboo-brain/spec(the contract),@booboo-brain/build(config-driven postgres/json adapters),@booboo-brain/serve(REST + MCP query layer),@booboo-brain/viewer(million-node 3D render),@booboo-brain/panel(the organigram),@booboo-brain/vault(wiki-linked markdown export),@booboo-brain/cli(the unifiedbooboocommand), andcreate-booboo(project scaffolder). Per-package semver — see eachpackage.json. MIT.
Booboo is a tinyJSON specat the center, withadaptersthat feed it andconsumersthat render/serve/query it:
your data ──▶ ADAPTERS ──▶ GRAPH JSON ──▶ CONSUMERS (postgres, (config- (the spec, (3D viewer · json, neo4j, driven, ~1 KB REST API · mcp, …) ~50 lines) contract) MCP server · wallpaper)
Emit the JSON → get the viewer, the API, and the MCP serverfor free. Weird data → a ~50-line adapter, not a fork. SeeSPEC.md.
One command. No database, no config, no signup.A synthetic brain, running on your machine:
npx @booboo-brain/cli view --demo --nodes 1000000
That's the headline flex:a million nodes at 60fps in a browser tab.Drop the count to--nodes 50000on a modest laptop. SeeSCALE.mdfor how it holds up (one draw call over a single point cloud with a custom shader, plus tier-LOD on labels).
If it holds up on your machine,leave a star. There's no marketing behind this repo; stars are how the next builder finds it.
# scaffold a project (json starter + postgres upgrade path) npx create-booboo my-brain cd my-brain npm install npm run build # booboo.config.yaml → brain.json (the snapshot) npm run serve # REST API on http://localhost:8787 npm run mcp # MCP over stdio — point Claude / Cursor / Claude Code at it
Editbooboo.config.yamlto point at your own Postgres/Supabase (a commented example ships in the scaffold). Full reference:docs/CONFIG.md· stuck?docs/TROUBLESHOOTING.md.
Roadmap:a single all-in-one command bundling build + REST + MCP + the 3D viewer together, and an interactive scaffold wizard — tracked inLAUNCH_CHECKLIST.md.
booboo build --config booboo.config.yaml # any postgres/json → one graph snapshot (privacy walls + parent spines) booboo serve --snapshot my.booboo.json --port 8787 # REST: /graph /stats /search /nodes/:id /neighbors/:id /path/:a/:b booboo mcp --snapshot my.booboo.json --org org.booboo.json # MCP over stdio (+ booboo_boot: agents boot FROM the org) booboo view --snapshot my.booboo.json # 3D viewer in your browser — no monorepo, no build step booboo panel --org org.booboo.json --snapshot my.booboo.json # THE ORGANIGRAM — see below booboo vault --snapshot my.booboo.json --org org.booboo.json --out vault # the brain as a markdown vault — see below
booboo viewserves the@booboo-brain/viewer3D renderer as a standalone app — any snapshot (or?n=1000000synthetic) in your browser, no monorepo. The build engine was proven on a real4,469-node production brainassembled straight from Supabase by config alone — privacy-walled, validated, served. See each package's README for the details.
booboo mcpspeaks MCP over stdio. Point any MCP client at it — no server to host, it runs on demand:
// Claude Desktop: claude_desktop_config.json · Cursor: .cursor/mcp.json · Claude Code: .mcp.json { "mcpServers": { "booboo": { "command": "npx", "args": ["-y", "@booboo-brain/cli", "mcp", "--snapshot", "my.booboo.json", "--org", "org.booboo.json"] } } }
Your agent can now query the whole system —search,neighbors,path,stats—booboo_boot('<agent-id>')returns an agent's rules, memory reach, and reports so itboots from the org, andbooboo_remember/booboo_reportlet itwrite backdurable memories and reports that persist across rebuilds (the live memory system). Point--snapshot/--orgat absolute paths if the client's working directory differs.
booboo_remember/booboo_reportare on by default — the live half of the memory system. Pass--no-write(orBOOBOO_READONLY=1) for a read-only server (public/locked-down deployments); it stillreadsthe journal but refuses writes.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
