Agent-oriented memory and code intelligence over MCP. AI agents don't read docs — they call tools. nano-brain gives them structured context, symbol lookup, call-chain tracing, and change-impact analysis across sessions and repos.
Persistent memory & code intelligence server for AI coding agents. Deploy on VPS for shared memory across machines. Hybrid search (BM25 + pgvector), knowledge graph, impact analysis. 14 MCP tools. Works with Claude Code, OpenCode, Cursor, and any MCP client.
Yıldızlar
13
Araçlar
—
Çalışma süresi
—
What it is
nano-brain is an infrastructure layer between your AI agent and your code. It solves two problems agents have:
Session amnesia — agents forget everything when a session ends. nano-brain harvests, indexes, and retrieves past sessions and saved decisions.
Codebase blindness — agents can't cheaply trace dependencies, measure blast radius, or map an execution path. nano-brain builds a code graph and exposes it as MCP tools.
Self-hosted (Go binary + PostgreSQL), works with any MCP client (Claude Code, OpenCode, Cursor, …), and returns structured results — not raw file bytes.
Install
# Recommended — one-line installer (no Node.js needed): downloads the prebuilt
# binary for your platform from GitHub Releases and verifies its SHA-256.
curl -fsSL https://raw.githubusercontent.com/nano-step/nano-brain/master/install.sh | bash
# Or via npm (handy if you're already in a JS/agent toolchain)
npm install -g @nano-step/nano-brain
# Or build from source
CGO_ENABLED=0 go build -o nano-brain ./cmd/nano-brain
Prefer to read the installer first? curl -fsSL -o install.sh https://raw.githubusercontent.com/nano-step/nano-brain/master/install.sh && less install.sh && bash install.sh.
Start
# One command — the interactive wizard provisions PostgreSQL (Docker or remote URL),
# configures embeddings, starts the server, registers this project, and wires up your MCP client.
nano-brain init
Manual, per-step setup (VPS / team / no Docker / Windows): docs/SETUP_AGENT.md.
Bind a default workspace by appending ?workspace=<name-or-hash> to the URL (e.g. …/mcp?workspace=my-project) so tool calls can omit the workspace argument. An explicit workspace argument always overrides it; the value must be a name or full hash (not "all"). Run nano-brain workspaces list to see registered names/hashes.
For OpenCode, you can bootstrap the current workspace with npx @nano-step/nano-brain init -- opencode. It installs a /nano-brain slash command that keeps the workspace config local at .nanobrain/config.yml.
The agent workflow
A cold agent should follow this order — it maps 1:1 to the tools:
Orient — memory_wake_up for a workspace briefing (recent activity, collections, stats).
Locate the workspace — memory_workspaces_resolve(path) returns a deterministic hash and whether it's registered. Registering the repo root also covers its subdirectories, so resolve the root, not a single sub-repo.
Understand — memory_query (hybrid, best for natural-language questions), memory_search (exact identifiers/errors), or memory_vsearch (fuzzy concepts). Search returns 500-char snippets; fetch full text with memory_get only for the hits you keep.
Navigate code — memory_symbols to find a definition (no indexing needed), then memory_graph / memory_trace for call chains and memory_flow for an HTTP route's execution.
Before a risky edit — memory_impact(node, direction="in") for the blast radius (who calls / imports this).
Persist — memory_write to save a decision, lesson, or handoff for the next session.
Control-flow graph of a single function (branches, loops, returns)
Workspace & ops
Tool
Use it for
memory_workspaces_resolve
Resolve a path to its workspace hash + registration status
memory_workspaces_list
List registered workspaces with paths, hashes, document counts
memory_status
Server / DB / embedding-queue health
memory_update
Trigger a delta re-scan / re-embedding for a workspace
Every tool is self-describing over MCP — your client lists each tool's name, parameters, and description on connect.
Architecture
graph LR
A[Your AI Agent] -->|MCP| B[nano-brain]
B --> C[PostgreSQL + pgvector]
B --> D[Session Harvesting]
B --> E[Code Intelligence]
B --> F[Hybrid Search]
D --> D1[OpenCode Sessions]
D --> D2[Claude Code Sessions]
E --> E1[Symbol Graph]
E --> E2[Flow Diagrams]
E --> E3[Impact Analysis]
F --> F1[BM25 Full-Text]
F --> F2[Vector Similarity]
F --> F3[RRF Fusion]
Code-intelligence lookups (memory_symbols, memory_graph, memory_impact, memory_vsearch, exact memory_search) return in tens of milliseconds — fast enough that agents can run impact analysis on every edit rather than skipping it.
Search quality vs. document-memory tools
Metric
nano-brain
LlamaIndex
Qdrant/Mem0
P@5
80%
55%
27%
MRR
95%
—
—
Code intelligence (symbols / impact / flow)
✅
❌
❌
Measured on 60 domain-specific queries across three workspaces (a Go daemon, a TypeScript service, and a Rails app). nano-brain is the only one of these with code intelligence — the others target conversation memory and document retrieval.
Agent-oriented capability benchmarks
Each benchmark runs a deterministic agent workflow — natural-language question → optimized query → symbol lookup — mirroring how an agent actually explores a codebase.
Workspace
Overall
Multi-tool
Search-QA
Symbol-Lookup
Go daemon
1.000
1.000
1.000
1.000
TypeScript service
0.885
1.000
0.817
1.000
Rails app
0.795
1.000
0.726
0.667
Run them: see the per-suite READMEs under benchmarks/.
Everything is available over MCP; a REST surface exists for scripting and ops (writes go through MCP). GET /api/openapi.json serves the live OpenAPI 3.0 spec — import it into Postman/Swagger.
# Understand
curl -X POST http://localhost:3100/api/v1/query -H 'Content-Type: application/json' \
-d '{"workspace":"<hash>","query":"how does authentication work"}'
# Blast radius
curl -X POST http://localhost:3100/api/v1/graph/impact -H 'Content-Type: application/json' \
-d '{"workspace":"<hash>","node":"src/auth/login.ts","direction":"in"}'
git clone https://github.com/nano-step/nano-brain.git && cd nano-brain
CGO_ENABLED=0 go build -o nano-brain ./cmd/nano-brain
go test -race -short ./... # unit
go test -race -tags=integration ./... # integration (needs PostgreSQL)
Regenerate the OpenAPI spec after route changes: make generate-openapi.
Persistent memory & code intelligence server for AI coding agents. Deploy on VPS for shared memory across machines. Hybrid search (BM25 + pgvector), knowledge graph, impact analysis. 14 MCP tools. Works with Claude Code, OpenCode, Cursor, and any MCP client.
Araçlar
Araçlar
Henüz araç listesi yok. Uzak sunucular ilk sağlık kontrolünden sonra bir liste alır.
SSS
Sorular
Nano Brain nasıl kurulur?
Bu sayfadan Cursor, Claude Desktop, Claude Code veya VS Code için stdio yapılandırmasını kopyalayın. PlugMCP proxy'sini değil, yayıncının kurulumunu kullanır.
Bu kayıtta gerekli bir ortam değişkeni listelenmiyor.
Nano Brain hangi aktarımı kullanıyor?
Nano Brain yerel olarak stdio üzerinden çalışır.
Nano Brain en son ne zaman kontrol edildi?
Son kontrol: 2026-10-28. Persistent memory & code intelligence server for AI coding agents. Deploy on VPS for shared memory across machines. Hybrid search (BM25 + pgvector), knowledge graph, impact analysis. 14 MCP tools. Works with Claude Code, OpenCode, Cursor, and any MCP client.