Query your AI system's wiring, knowledge, memory, agents and crons as one rooted graph over MCP.
Query your AI system's wiring, knowledge, memory, agents and crons as one rooted graph over MCP. That is what the booboo mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
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.
The server publishes 8 tools. What each one is for:
booboo_stats — Node/link counts for the whole graph, broken down by layerbooboo_count — Counts alone, without pulling the payload — use when sizing a querybooboo_search — Search nodes by label or id (ranked: exact > prefix > substring). Use this first to find a node's idbooboo_node — Fetch a single node (all fields + data) by its exact idbooboo_neighbors — The neighbourhood around a node: connected nodes + links out to depth hopsbooboo_path — Shortest path (chain of nodes) between two node ids; null if unreachablebooboo_remember — Write a durable memory — one atomic fact, tied to an agent. Appended to the journal beside the snapshot; queryable the same session, survivesbooboo_report — Write a report — what an agent just closed. Lands on the panel's Reports timelineBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Booboo's toolset — booboo_stats, booboo_count, booboo_search and 5 more — is a fair guide to whether it matches your workflow. It is maintained by jessedu29260-netizen; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Booboo's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| booboo_stats | Node/link counts for the whole graph, broken down by layer. |
| booboo_count | Counts alone, without pulling the payload — use when sizing a query. |
| booboo_search | Search nodes by label or id (ranked: exact > prefix > substring). Use this first to find a node's id. |
| booboo_node | Fetch a single node (all fields + data) by its exact id. |
| booboo_neighbors | The neighbourhood around a node: connected nodes + links out to depth hops. |
| booboo_path | Shortest path (chain of nodes) between two node ids; null if unreachable. |
| booboo_remember | **Write** a durable memory — one atomic fact, tied to an agent. Appended to the journal beside the snapshot; queryable the same session, survives every rebuild. |
| booboo_report | **Write** a report — what an agent just closed. Lands on the panel's Reports timeline. |
{
"mcpServers": {
"booboo": {
"command": "npx",
"args": ["-y", "@booboo-brain/cli"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.