DevMemory

Persistent memory for AI agents. Every session starts where the last one ended.

What is DevMemory?

DevMemory is a long-term memory layer for AI coding agents, delivered via MCP. It lets Claude Code, Cursor, Windsurf, Codex, and any MCP-compatible agent remember decisions, lessons, and context across sessions — so they never start from zero.

Your AI agent stores memories as it works. Next session — same agent or a different one — it recalls what matters. No copy-pasting, no re-explaining.

The Killer Scenario

Session 1 — Claude Code, Monday afternoon:

You: "Let's use Qdrant for vector storage in this project."

Agent calls memory_store:
  content: "Architecture decision: using Qdrant for vector storage.
            Reason: cloud migration path + strong Python SDK."
  memory_type: "decision"

Session 2 — Cursor, Tuesday morning:

You: "What vector DB are we using?"

Agent calls memory_recall:
  query: "vector database choice"

→ Returns: "[DECISION] Architecture decision: using Qdrant for vector storage.
   Reason: cloud migration path + strong Python SDK.
   Project: my-app | Date: 2026-04-02"

Cross-agent, cross-session, zero friction.

Quick Start

# Install
pip install devmemory

# Initialize
devmemory init

# Set up your API key (for embeddings)
export PORTKEY_API_KEY=pk-...

# Auto-configure Claude Code (one command)
devmemory setup claude-code --write

# Done. Your agent now has persistent memory.

For other tools:

devmemory setup cursor --write
devmemory setup windsurf --write
devmemory setup codex --write

MCP Tools Reference

DevMemory exposes 6 tools via MCP that AI agents call automatically:

Agent Memory (Tier 1)

Project Context (Tier 2)

Knowledge Base (Tier 3)

CLI Reference

How It Works

┌─────────────────────────────────────────────────────────┐
│                   AI Agent Layer                        │
│                                                         │
│  ┌──────────┐  ┌──────────┐  ┌──────────┐  ┌────────┐ │
│  │ Claude   │  │ Cursor   │  │ Windsurf │  │ Codex  │ │
│  │ Code     │  │          │  │          │  │        │ │
│  └────┬─────┘  └────┬─────┘  └────┬─────┘  └───┬────┘ │
│       └──────────────┴──────────────┴──────────────┘    │
│                          │ MCP                          │
├──────────────────────────┴──────────────────────────────┤
│                  DevMemory MCP Server                   │
│                                                         │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────────┐ │
│  │  Memory     │  │  Context    │  │  Knowledge      │ │
│  │  store      │  │  get        │  │  search         │ │
│  │  recall     │  │  handoff    │  │  ingest         │ │
│  │  forget     │  │             │  │                 │ │
│  └──────┬──────┘  └──────┬──────┘  └────────┬────────┘ │
│         └────────────────┴──────────────────┘           │
│                          │                              │
├──────────────────────────┴──────────────────────────────┤
│                    Storage Layer                        │
│                                                         │
│  ┌─────────────┐  ┌──────────────┐  ┌───────────────┐  │
│  │  Qdrant     │  │  SQLite      │  │  Git-aware    │  │
│  │  (semantic  │  │  (metadata,  │  │  project      │  │
│  │   vectors)  │  │   temporal)  │  │  scoping      │  │
│  └─────────────┘  └──────────────┘  └───────────────┘  │
└─────────────────────────────────────────────────────────┘

All data is stored locally in ~/.devmemory/. Memories are embedded for semantic search (Qdrant) and indexed temporally (SQLite). Projects are auto-detected from git.

Why DevMemory?

Pricing

Documentation

• Getting Started
• Agent Memory Guide
• MCP Integration
• CLI Reference

License

MIT