AllBrain Agent Runtime

One brain. Many agents. One shared memory.

Without AllBrain vs with AllBrain

Related MCP server: Enhanced Sequential Thinking MCP Server

The problem

Your AI coding agents don't talk to each other. Agent A saves a plan, Agent B starts fresh, Agent C has no idea what happened. Each agent works in isolation, repeating mistakes and missing context.

AllBrain gives every agent a shared workbench. Each tool call is recorded in an append-only event store. When the next agent arrives, it sees everything that happened before — events, sessions, conflicts, decisions — and picks up cleanly.

What AllBrain gives you

• Shared memory — save_event, list_events, resume_project across any MCP client

• Agent attribution — every event is tagged with the agent that wrote it

• Conflict detection — automatic surface of conflicting state updates

• Decision pipelines — counterfactual reasoning, scenario planning, foresight

• Deterministic replay — rebuild project state from raw events

• 53 tools in full profile across 18 domain modules (start with 3, enable more as needed)

30-second demo

# Agent A: save a plan
uv run allbrain start --project . --agent agent-a
# In Agent A's client, call:
#   save_event(type="task_planned", payload={"task": "implement auth"})

# Agent B: see what Agent A did
uv run allbrain start --project . --agent agent-b
# In Agent B's client, call:
#   list_events()
#   resume_project()

See examples/two_agent_sqlite_pilot.py for a full two-agent workflow with conflict detection and replay verification.

Install for one client

The PyPI distribution is allbrain-agent-runtime. The canonical CLI command is allbrain; allbrain-mcp and allbrain-agent-runtime remain compatibility aliases for existing installations and scripts.

uvx allbrain-agent-runtime install --codex

This configures Codex to start AllBrain automatically. Replace --codex with the client name:

Use --all to configure every supported client at once.

Verify it works

uvx allbrain-agent-runtime install --codex --verify

The --verify flag starts the server, saves a test event, reads it back, and confirms shared memory is working.

Tool profiles

Start with --tool-profile minimal (3 tools) and expand when needed:

uv run allbrain start --project . --agent my-agent --tool-profile memory

Glama MCP Portal

Glama MCP evaluates this server with the balanced core tool profile (--tool-profile core in glama.json). Its 11 public tools cover shared memory, task orchestration, snapshots, Git context, and decision workflows without exposing the entire development surface.

For local development or to access all capabilities, use the full profile:

uv run allbrain start --project . --agent claude-code --tool-profile full

Alternatively, standard client configurations like .mcp.json (which default to full) can be used.

From source

git clone https://github.com/Mustafa-Ali-Ertugrul/allbrain-mcp.git
cd allbrain-mcp
uv sync
./scripts/install-mcp.sh --all --isolate --verify

Or run the guided onboarding wizard:

uv run allbrain onboard

It walks you through client selection, install, verification, and your first event step by step.

See the full setup guide for manual config, troubleshooting, and shared-vs-isolated databases.

First memory save

Once AllBrain is installed and the client is restarted, call:

save_event(type="task_started", payload={"task": "implement auth", "agent": "codex"})

Then verify it was recorded:

list_events()

Switch to another client, call list_events() again — the same event appears.

Tool count and supported clients

Note: Glama evaluates the balanced 11-tool core profile. The full profile remains available for local development.

• 53 tools in the full MCP profile across 18 server tool implementation modules (src/allbrain/server/tools/)

• Default profile (full) registers all tools

• minimal profile: 3 tools (save_event, list_events, resume_project)

• core profile: 11 tools (essential workflow + reasoning + context pack)

What's New in v1.1.0

Security hardening (threat-model remediation)

• Fail-closed sanitization (§B1): Depth-limit bypass closed; configurable max depth and payload size cap.

• gitbrain RCE sandbox (§D): No-shell argv, hard env isolation, and dangerous git config overrides.

• SQLite permissions (§E1): Restrictive file/dir modes and umask hardening (Windows best-effort documented).

• Memory poisoning defense (§1): Event-sourced quarantine, default exclusion from context, untrusted event boundaries, promote_event / review_quarantined.

• Safe install (§C1): .mcp.json backup + merge + confirm/--force + integrity hash.

• Windows path hardening (§C2): Case-insensitive normcase + realpath containment checks.

• Event hash-chain (§A2): Lightweight tamper-evidence via chained payload hashes.

Runtime changes

• Full tool surface: 53 tools (promote_event, review_quarantined added)

• list_events default limit raised to 1000

• CI matrix: Python 3.12 & 3.13, coverage gate 85%

What's New in v1.0.0

1. 6 Bounded Contexts & 73 Domain Modules Migration

• Modular Namespace: All 73 domain packages have been reorganized into the canonical allbrain.domains.* namespace across 6 bounded contexts: reasoning, analysis, learning, governance, memory, and collaboration.

• Backward Compatibility Shims: Root imports (allbrain.<module>) remain functional with DeprecationWarning and are slated for removal in v2.0.0.

2. High-Performance Benchmarks & FastMCP Engine

• Cold Startup: $\le 0.11$s server initialization.

• Throughput: 277–371+ eps across varying payload sizes on local SQLite WAL.

• Snapshot Generation: 0.091s for 10,000 events.

• Memory Footprint: ~150 MB RSS peak under concurrent load.

3. Production Security & Verification

• Secret Redaction: Multi-layer masking for 13+ secret formats and Pydantic validation error sanitization.

• Input Validation: Strict Pydantic models with null-byte rejection and prompt injection filtering across MCP tools.

• Filesystem Sandbox: ALLBRAIN_ALLOWED_PROJECT_ROOTS path traversal isolation.

• Dual-Window Rate Limiting: Process-local thread-safe rate limiter (1,000 RPS burst, 100,000 RPM rolling).

Data lifecycle and security

AllBrain stores events, sessions, and audit logs in local SQLite. Data never leaves your machine. Credential-like values are redacted before storage.

• Data lifecycle — what is stored, retention, cleanup, restore

• Uninstall guide — remove AllBrain from clients and delete data

Advanced docs

• Full setup guide — all clients, shared vs isolated databases, troubleshooting

• Custom agent integration — use AllBrain from any MCP client

• Python SDK — typed async client (experimental)

• Architecture — event sourcing, reducers, stream ordering, pipeline, bounded contexts

• Storage backends — SQLite vs PostgreSQL vs queue adapters

• Package maturity — production core vs opt-in vs experimental packages

• Multi-agent pilot — two-agent workflow walkthrough

• Upgrade guide — migrations, rollback, breaking changes

• Community examples — real user setups, terminal output, workflows

Status

• 3,110 passed tests, 5 skipped tests (100% green)

• 53 tools in full profile

• stdio FastMCP handshake verified

• Python 3.12 & 3.13 (CI matrix)

• Coverage: 86.54% (enforced threshold 85%)