dbrain
Provides persistent, structured memory for AI assistants across multiple clients, with searchable facts and identity management.
README
<p align="center"> <img src="logo.png" alt="dbrain" width="600"> </p>
<p align="center"> <a href="https://www.npmjs.com/package/dbrain"><img src="https://img.shields.io/npm/v/dbrain?style=for-the-badge" alt="npm"></a> <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue.svg?style=for-the-badge" alt="License"></a> <a href="https://nodejs.org"><img src="https://img.shields.io/badge/node-%3E%3D20-green?style=for-the-badge" alt="Node"></a> </p>
Every AI conversation starts from zero. Switch machines, switch apps, and your AI forgets everything. dbrain fixes that.
Install it once, connect every AI you use — Claude Code at home, Claude Code at work, Gemini on your phone. All share the same identity, the same memories, the same knowledge.
[Home] Claude Code ──MCP──┐
[Work] Claude Code ──MCP──┤ ┌─────────────────────────────────┐
[Mobile] Gemini ──REST──────┼────→│ dbrain (your mind) │
[Server] OpenClaw ──REST────┤ │ identity + memory + knowledge. │
[Other] Custom AI ──API────┘ └─────────────────────────────────┘
Not an AI agent. Not an assistant. Not a model. Just memory — structured, searchable, persistent.
Quick Start
npm install -g dbrain
dbrain init # interactive wizard — creates DB, config, identity
dbrain start # starts API on :7878 + dashboard on :7879
Then connect Claude Code from any machine:
dbrain connect claude
The wizard asks for the brain URL and token (shown during init):
┌ dbrain — Connect to a brain
│
◇ Brain URL
│ http://localhost:7878
│
◇ Access token
│ sk-dbr_...
│
◇ Brain found
│
● Brain: dBrain — 2 entities, 0 facts
│
◇ Claude Code configured
│
◇ Files updated ──────────────────────────────────────────────╮
│ │
│ ~/.claude.json MCP server registered │
│ ~/.claude/settings.json Permissions granted │
│ ~/.claude/CLAUDE.md Behavioral instructions installed │
│ │
├──────────────────────────────────────────────────────────────╯
│
└ Connected. Restart Claude Code to activate.
Restart Claude Code and it will start using the brain. You can also skip the wizard:
dbrain connect claude http://your-server:7878 --token=sk-dbr_...
Docker
git clone https://github.com/ivncmp/dbrain.git
cd dbrain
cp .env.example .env # edit token, names, port
docker compose up -d
Then from any client machine:
dbrain connect claude http://your-server:7878
How It Works
The brain has 4 layers:
| Layer | What | How |
|---|---|---|
| Identity | Who is the AI? Who is the user? How should it behave? | documents table |
| Conversations | Raw chat history from every AI session | conversations + messages tables |
| Knowledge | Structured facts organized by PARA | entities + facts tables with hot/warm/cold tiers |
| Recall | Full-text search over all facts | FTS5 with OR logic for multi-language queries |
Memory Tiers
Memories fade if you don't use them — like a real brain.
| Tier | Rule |
|---|---|
| hot | Accessed in the last 7 days, or accessCount >= 10 |
| warm | 8–30 days since last access |
| cold | > 30 days — fading, candidate for archival |
Every search bumps accessed facts back to hot. The brain stays sharp on what matters.
MCP Tools
Available to any MCP client (Claude Code, etc.):
| Tool | Purpose |
|---|---|
recall |
Search memory + get identity (primary tool) |
remember |
Save a fact to an entity |
get_entity |
Read entity with all its facts |
list_entities |
List entities by category or type |
create_entity |
Create a new entity |
bump |
Touch a memory to keep it hot |
log |
Send conversation messages for storage |
wake_up |
Full identity load |
overview |
Brain stats |
REST API
All endpoints require Authorization: Bearer <token> except /health.
| Method | Endpoint | Purpose |
|---|---|---|
GET |
/health |
Brain pulse |
GET |
/connect |
Client config (MCP, permissions, instructions) |
GET/PUT/DELETE |
/workspace/:key |
Identity documents |
GET/POST/DELETE |
/entities/:id |
Knowledge entities |
POST |
/entities/:id/facts |
Add facts to an entity |
PATCH |
/facts/:id/access |
Bump a memory (keep it hot) |
GET/POST |
/conversations |
Chat history |
POST |
/search |
Full-text search over all facts |
GET |
/memory/summary |
Overview: entities x tiers |
CLI Commands
| Command | Where | Purpose |
|---|---|---|
dbrain init [path] |
Server | Create a new brain (DB, config, identity) |
dbrain start [path] |
Server | Start the API server + dashboard |
dbrain connect <client> [url] |
Client | Connect a client to a running brain |
dbrain status [path] |
Server | Check brain status |
init runs on the server (creates the brain). connect runs on the client (configures Claude Code). The brain serves its own client config via GET /connect.
Dashboard
Web dashboard on port 7879. Shows brain stats, entities with PARA categories, fact tiers, conversations, and full-text search. Single-file React app — no build step.
Stack
| Layer | Technology |
|---|---|
| Language | Node.js + TypeScript |
| API | Fastify |
| DB | SQLite + FTS5 (better-sqlite3) |
| MCP | @modelcontextprotocol/sdk (HTTP transport) |
| Validation | Zod |
| CLI | @clack/prompts |
| Dashboard | React 18 (CDN, no build step) |
Development
git clone https://github.com/ivncmp/dbrain.git
cd dbrain
npm install # installs deps + builds (prepare script)
npx dbrain init # create a brain (only needed once)
npm run dev # starts the server with file watching
| Script | What it does |
|---|---|
npm run dev |
Dev server with file watching (tsx) |
npm run build |
Compile TypeScript + copy dashboard HTML |
npm start |
Start the compiled server from dist/ |
npm test |
Run tests with vitest |
npm run lint |
ESLint check |
npm run lint:fix |
ESLint auto-fix |
npm run format |
Prettier format |
npm run check |
Lint + format + build (full pipeline) |
Environment Variables
For non-interactive setup (Docker, CI):
| Variable | Default | Purpose |
|---|---|---|
DBRAIN_DATA |
~/.dbrain |
Data path |
DBRAIN_PORT |
7878 |
API port |
DBRAIN_HOST |
0.0.0.0 |
Bind address |
DBRAIN_TOKEN |
Auto-generated | Access token |
DBRAIN_AGENT_NAME |
dBrain |
AI identity name |
DBRAIN_OWNER_NAME |
Human |
Owner name |
DBRAIN_TIMEZONE |
Auto-detected | Owner timezone |
License
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.