Cerebro MCP Server¶
Cerebro MCP is a Model Context Protocol server that connects AI assistants to Gnosis Chain's on-chain analytics infrastructure. It exposes ~50 tools that query a ClickHouse data warehouse, traverse ~862 dbt models, drive six interactive mini-apps, and orchestrate multi-phase analytical workflows — all over a single MCP connection.
New to Cerebro?
Start with the Setup Guide, then the Usage Guide for an end-to-end tour. For the dispatcher pattern (the front door for non-trivial requests) see Cerebro Dispatcher.
What is MCP?¶
The Model Context Protocol (MCP) is an open standard that lets AI hosts (Claude Desktop, VS Code, Claude Code, custom clients) connect to external tools and data sources through a unified interface. A single MCP server can serve every MCP-compatible client without per-client integration work.
What's in this section¶
| Subsection | Purpose |
|---|---|
| Setup | Install, configure, connect Claude Desktop / VS Code / Claude Code. Multi-tenant CEREBRO_OWNER env. |
| Available Tools | Categorised reference of every MCP tool. |
| Agent Fleet | The 27-persona library loadable via get_agent_persona. |
| Cerebro Dispatcher | Top-level intent triage + binding dispatch manifest. |
| Report Generation | generate_report, generate_research_report, generate_case_study_report, gates. |
| Security & Audit | Tool risk classes, JSONL audit log, multi-tenant identity. |
| Observability | Prometheus metrics, structured logs, Grafana dashboard. |
| Workflows | Research projects, storyteller, sandboxes, resumable workflows. |
| Mini-Apps | Five interactive UI surfaces (Report Renderer, Portfolio, Graph Explorer, Metric Lab, Contract Explorer). |
| Advanced | Hybrid search internals, event log, quality gates, multi-tenant, semantic metrics, full usage guide. |
| MMM / MMM User Guide | Marketing-mix modeling SOP and prompt recipes. |
Architecture¶
flowchart TB
H[MCP Host<br/>Claude Desktop / VS Code / Claude Code] -- stdio / SSE --> S
subgraph S[cerebro-mcp - FastMCP]
direction TB
T[Tool Registry<br/>~50 tools] --> CH[ClickHouse Client]
T --> D[dbt Manifest<br/>BM25 + networkx]
T --> ES[(Event Log<br/>SQLite WAL)]
T --> RS[(Research Store<br/>JSON)]
T --> SB[(Sandboxes<br/>DuckDB + Parquet)]
T --> UI[Mini-App Bundles<br/>React + ECharts]
end
CH --> CHC[(ClickHouse Cloud<br/>Gnosis Chain)] The server multiplexes four persistence layers:
- Event log (
~/.cerebro/cerebro_state.db) — append-only SQLite WAL holding workflows / events / gates. Powers crash recovery and resume hints. See Memory & Resume. - Research JSON store (
~/.cerebro/research_projects/) — durable per-project state. - Sandbox snapshots (
~/.cerebro/sandboxes/) — DuckDB + Parquet for what-if simulations. - In-memory singletons — storyteller phase machine, session counters.
Transport modes¶
stdio (default)¶
Local-only. Claude Desktop / Claude Code spawn cerebro-mcp as a subprocess and talk over stdin/stdout.
SSE / HTTP (remote)¶
For team deployments. Starts a uvicorn server.
The hosted team instance is at mcp.analytics.gnosis.io with bearer-token auth.
Capability summary¶
Discovery & query¶
- 6 ClickHouse databases, ~862 dbt models across 8 modules (execution, consensus, bridges, p2p, contracts, ESG, probelab, crawlers).
- Hybrid BM25 + RRF search (
search_models,discover_models) —hit@1improved 4× over the legacy ranker (see Hybrid Search). - Deterministic networkx lineage (
get_upstream_lineage,get_downstream_impact). - Column-scoped schema injection for wide tables (
get_relevant_columns). - 5.3M+ Dune address labels, token metadata, ENS / Safe / Circles / GPay resolution.
Visualisation & reporting¶
- Batch chart generation with ECharts (
generate_charts). - Three report layouts: dashboard (
generate_report), research essay (generate_research_report), scrollytelling case study (generate_case_study_report). - Eight enforcement gates on
generate_report(stock/flow discipline, residual buckets, stationarity, aggregator dedup, discovered-model coverage, …). See Quality Gates. - Reports render as native UI in MCP-aware hosts; standalone HTML at
~/.cerebro/reports/.
Workflows¶
- Research projects — multi-phase plan/execute/verify with peer-review gate.
- Storyteller — eight-step narrative pipeline (context brief → big idea → storyboard → visual specs → final story).
- Simulation sandboxes — DuckDB + Parquet what-if isolation.
- Resumable workflows — every workflow phase logged;
list_resumable_workflowsrecovers from crashes.
Mini-apps¶
Five React + ECharts mini-apps that render inline in MCP-aware hosts: Report Renderer, Portfolio, Graph Explorer, Metric Lab, Contract Explorer. See Mini-Apps.
Safety¶
- Read-only ClickHouse SQL (allowlisted statements, identifier validation, row + time caps).
- Tool-risk classification with detection-first JSONL audit log.
- Optional multi-tenant identity via SHA-256
ownerhash on every workflow. - 30-day reasoning trace retention with auto-redaction of secrets.
Where to go next¶
- New users → Setup → Usage Guide.
- Looking for a tool? → Available Tools.
- Building a report? → Report Generation + Quality Gates.
- Long-running analysis crashed? → Resumable Workflows.
- Want to write narrative deliverables? → Storyteller.
- Running counterfactuals? → Simulation Sandboxes.
- Dashboards / specific data? → Mini-Apps.