claude-memory-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@claude-memory-mcpremember that we are using SQLite for local dev"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
claude-memory-mcp
An MCP server that gives Claude Code cross-session memory — persisted to a plain .claude-memory.md file inside your repo.
Each project gets its own memory. Commit the file to git and it follows the codebase forever.
Install
# Via uvx (no install needed)
uvx claude-memory-mcp
# Or pip
pip install claude-memory-mcpRelated MCP server: claude-context-server
Configure Claude Code
Add to your project's .mcp.json (or ~/.claude.json for global):
{
"mcpServers": {
"memory": {
"command": "uvx",
"args": ["claude-memory-mcp"]
}
}
}Tools
Tool | Description |
| Read a stored value |
| Write a value |
| List all keys |
How it works
Memory is stored as ## sections in .claude-memory.md at your repo root:
# Claude Memory
## architecture-decisions
We use SQLite for local dev and Postgres in prod.
Decided 2025-01-15 — migration too risky mid-sprint.
## current-sprint-context
Working on payment webhook handler. Stripe sends events
to /api/webhooks/stripe. See stripe_handler.py:42.Project-scoped: different repos = different memory files
Git-tracked: commit
.claude-memory.md— memory persists across machines and teammatesHuman-readable: open the file, edit it, diff it like any other source file
No auth, no cloud, no database: just a file
Use cases
Remember architectural decisions across sessions
Store "where I left off" context so Claude doesn't ask again
Share team conventions without repeating them in every prompt
Track ongoing debugging context across long refactors
Show HN post
Show HN: I built an MCP server that gives Claude Code a persistent memory file
The problem: every Claude Code session starts fresh. I keep explaining the same architectural decisions, the same "don't touch X" rules, the same "we use Y for Z" conventions.
This MCP server persists memory to
.claude-memory.md— a plain markdown file in your repo. Claude reads and writes it across sessions. Commit it to git and it follows the codebase.Three tools:
memory_read,memory_write,memory_list. That's it.Install: add 8 lines to your
.mcp.json, runuvx claude-memory-mcp.
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Cloud-hosted MCP server for durable AI memory
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
- mcpOAuthai.butlerbrain
Persistent memory for AI assistants. Save once; recall from Claude, ChatGPT, or any MCP client.
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
Related MCP Servers
- AlicenseNot gradedqualityDmaintenancePersistent memory MCP server for Claude Code that captures and recalls project context across sessions, eliminating the need to re-explain architecture and decisions daily.292 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that reads all your Claude Code project memory files and exposes them as tools. Lets any Claude instance — in any project, or via Claude.ai — query your full project history and preferences.56 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides Claude Code with persistent memory across sessions, including session checkpoints, image persistence, and bidirectional sync with claude.ai projects.1MIT
- AlicenseNot gradedqualityCmaintenanceA persistent memory MCP server for Claude Code that enables long-term recall across sessions via hybrid search, code intelligence, and tools for reading/writing memory.10 npm1MIT