Shared Memory for AI Agents
Persistent team knowledge that follows your agents across sessions. Every agent starts with the full context of everything your team has learned.
Claude Code memory is local. Cursor has none. Your agents forget everything between sessions.
3 lines to connect
{
"mcpServers": {
"memory": {
"command": "npx",
"args": ["-y", "@buildd/memory-plugin"],
"env": {
"BUILDD_MEMORY_API_KEY": "bld_mem_..."
}
}
}
}How it works
Connect via MCP
Add the MCP config to your project. Works with Claude Code, Cursor, Windsurf — any MCP-compatible agent.
Agents save discoveries
As agents work, they record gotchas, patterns, and architecture decisions. Memories are typed, tagged, and searchable.
Every session starts informed
New sessions automatically load relevant memories. Your 10th agent avoids the mistakes of your first.
Memory types
Structured knowledge, not raw text. Each memory has a type, tags, and relevance scoring.
Gotcha
Traps and footguns that waste time. "Don't use db.transaction() with neon-http driver."
Architecture
How the system is structured. "Auth uses dual model: API keys for pay-per-token, OAuth for seat-based."
Pattern
Recurring solutions. "All API routes validate auth with getAuthContext() first."
Decision
Why things are the way they are. "Chose Pusher over SSE for real-time because of Vercel cold starts."
Discovery
Found during investigation. "The proxy.ts file handles all subdomain routing — don't add middleware."
Summary
Condensed understanding. "The worker claim flow: POST /claim → optimistic lock → return task."
Agent-native pricing
One API key per agent. One workspace per project. Pay for knowledge, not seats.
Pro
- 3 workspaces
- 5k memories
- 20 API keys
- 10k context calls/mo
- 25k search + write/mo
Scale
- Unlimited workspaces
- 50k memories
- Unlimited API keys
- 100k context calls/mo
- 250k search + write/mo
FAQ
What's a workspace?
A workspace maps to a project or repo. Each workspace has its own memories, API keys, and usage limits. Agents in one workspace can't see memories from another.
Do agents count as users?
No. You pay for knowledge capacity, not seats. Connect as many agents as you want — each gets an API key, and they all share the workspace's memory pool.
Can I self-host?
Yes. Memory is fully open source. Run it on your own infrastructure with your own Postgres database. The hosted version at memory.buildd.dev is the easiest way to get started.
How does the free tier work?
Sign up, create a workspace, connect your agents. No credit card required. You get 200 memories and 500 context calls per month — enough to evaluate Memory on a real project.
Stop losing knowledge between sessions
Connect Memory in 3 lines. Your agents will thank you.