Memdex
One SQLite memory file that coding agents share, with summaries, notes and messages
- Platforms
- CLI, self-hosted
- Runs
- Locally
- Version
- 0.3.1
- Listing updated
- today
Similar MCP servers
About Memdex
Memdex is an MCP server for knowledge and memory. It runs locally on your machine and is started by your AI client.
Memdex gives several agents one memory store so a new session starts from what the last left. File summaries are keyed to a content hash rather than a path, so a summary stays valid until the file changes and the agent is told when it goes stale. Notes such as decisions and pitfalls cite the files they depend on and are flagged when those files change.
Coordination features include claim for files being edited, post and inbox for agent-to-agent messages, and handoff for the next session. Worktrees of one repository share the same memory. The README reports that on a 66-file repo, outlines took 3,471 tokens against 154,105 for reading every file, using a rough chars-divided-by-four estimate.
Setup is memdex connect, which merges config into installed clients and backs up first, with --serve-check verifying initialize and tools/list. Each agent gets a self-declared name via MEMDEX_AGENT. Data is a SQLite file under ~/.memdex.
Install
Run in a terminal
claude mcp add memdex -- uvx memdex-mcpAdd to claude_desktop_config.json
{
"mcpServers": {
"memdex": {
"command": "uvx",
"args": [
"memdex-mcp"
]
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"memdex": {
"command": "uvx",
"args": [
"memdex-mcp"
]
}
}
}Add to .vscode/mcp.json
{
"servers": {
"memdex": {
"type": "stdio",
"command": "uvx",
"args": [
"memdex-mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"memdex": {
"command": "uvx",
"args": [
"memdex-mcp"
]
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"memdex": {
"command": "uvx",
"args": [
"memdex-mcp"
]
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
MEMDEX_AGENTName this agent uses in notes, messages and claims (claude, codex, cursor, ...).MEMDEX_HOMEDirectory holding memdex.db (default ~/.memdex).
Tools this server provides (3)
Taken from the project documentation; the running server may differ.
- file_summary
- Read a stored summary for a file before reading it
- project_brief
- Show what the last session left for you
- remember
- Save a note or decision
What it does
- Hash-keyed summaries
- File summaries stay valid until content changes and warn when stale.
- Notes that expire
- Decisions and pitfalls are flagged when the files they cite change.
- Agent messaging
- Post, inbox, claim and handoff let agents coordinate on one repo.
- One-command connect
- memdex connect wires many clients and can verify the server answers.
- Token benchmark
- memdex bench estimates read cost against outlines in your checkout.
Good for
- Resume work in a new session without re-reading large files
- Stop two agents editing the same file
- Leave a handoff for the next agent
- Share lessons between Claude Code, Codex and Cursor
Pricing
Pricing unknown
Installs from PyPI; licence not published
Memdex FAQ
Where is data stored?
In a SQLite file, by default memdex.db under ~/.memdex.
Does it need a cloud?
No. The README says one SQLite file, zero dependencies and no cloud.
Which clients does connect support?
Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Zed, Cline, Gemini CLI, Codex CLI and DeepSeek Harness.
Is the agent name verified?
No. MEMDEX_AGENT is a self-declared label, not an authenticated identity.
How do I add Memdex to Claude Code?
Run this command in your terminal: claude mcp add memdex -- uvx memdex-mcp
What are the best alternatives to Memdex?
The closest alternatives to Memdex are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.


