Menyediakan memori proyek lokal-first yang persisten bagi AI coding agent untuk menyimpan dan mengambil keputusan arsitektur, pelajaran debugging, serta konvensi coding.
Juga dikenal sebagai vasikmansuri/devmemory, @vasikmansuri/devmemory
- Stars
- 14
- Tools
- 9
- Unduhan, 30 hari
- —
- Versi terbaru
- —
- Commit terakhir
- 2 Nov 2026
- Lisensi
- MIT
Apa itu devmemory MCP?
devmemory adalah MCP server. Menyediakan memori proyek lokal-first yang persisten bagi AI coding agent untuk menyimpan dan mengambil keputusan arsitektur, pelajaran debugging, serta konvensi coding. Server ini menyediakan 9 tool, seperti memory_save, memory_search, memory_get.
Ringkasan dibuat dari README proyek
Tentang devmemory MCP server
DevMemory menyediakan cara lokal-first bagi AI coding agent untuk mempertahankan memori jangka panjang mengenai informasi spesifik proyek. Ini memungkinkan tool seperti Claude Code dan Cursor untuk menyimpan dan mengambil keputusan arsitektur, pelajaran debugging, serta konvensi coding di berbagai sesi yang berbeda. Dengan menggunakan Model Context Protocol via stdio, server ini memastikan asisten AI Anda tidak melupakan konteks kritis setiap kali percakapan baru dimulai.
sistem ini beroperasi sepenuhnya di mesin Anda menggunakan database SQLite lokal yang disimpan di direktori home Anda. Anda tidak memerlukan akun, koneksi cloud, atau telemetri. Untuk menjaga keamanan, server akan melakukan redaction pada informasi sensitif seperti API keys dan password sebelum disimpan. Server juga memperlakukan memori yang diambil sebagai data yang tidak terpercaya (untrusted data) untuk melindungi dari prompt injection. Developer dapat mengelola memori ini melalui CLI khusus dengan 15 command atau melalui 9 MCP tools spesifik termasuk memory_save, memory_search, dan memory_context.
Apa yang bisa Anda lakukan dengannya
- 1Preserve architectural decisionsInstruksikan AI agent untuk menyimpan pilihan teknologi tertentu agar dapat dipanggil kembali pada sesi mendatang.
- 2Avoid repeating debugging stepsSimpan pelajaran yang didapat dari bug yang sulit untuk mencegah AI melakukan kesalahan yang sama lagi.
- 3Enforce team coding standardsBerikan konvensi dan batasan spesifik proyek kepada AI untuk memastikan pembuatan kode yang konsisten.
- 4Automate knowledge managementGunakan command line interface untuk mengimpor atau mengekspor memori proyek secara terprogram dalam format JSON.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal devmemory MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal devmemory MCP di Claude Code
$ claude mcp add devmemory -- npx -y @vasikmansuri/devmemoryInstal devmemory MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"devmemory": {
"command": "npx",
"args": [
"-y",
"@vasikmansuri/devmemory"
]
}
}
}Instal devmemory MCP di VS Code
.vscode/mcp.json
{
"servers": {
"devmemory": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vasikmansuri/devmemory"
]
}
}
}Instal devmemory MCP di VS Code CLI
$ code --add-mcp '{"name":"devmemory","type":"stdio","command":"npx","args":["-y","@vasikmansuri/devmemory"]}'Instal devmemory MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"devmemory": {
"command": "npx",
"args": [
"-y",
"@vasikmansuri/devmemory"
]
}
}
}Instal devmemory MCP di Codex
$ codex mcp add devmemory -- npx -y @vasikmansuri/devmemoryInstal devmemory MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.devmemory] command = "npx" args = ["-y", "@vasikmansuri/devmemory"]
Instal devmemory MCP di Gemini CLI
$ gemini mcp add -s user devmemory npx -- -y @vasikmansuri/devmemoryInstal devmemory MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"devmemory": {
"command": "npx",
"args": [
"-y",
"@vasikmansuri/devmemory"
]
}
}
}Tool devmemory MCP 9
Terdeteksi dari READMEmemory_savememory_searchmemory_getmemory_updatememory_forgetmemory_listmemory_contextmemory_linkmemory_stats
| memory_save | — | |
| memory_search | — | |
| memory_get | — | |
| memory_update | — | |
| memory_forget | — | |
| memory_list | — | |
| memory_context | — | |
| memory_link | — | |
| memory_stats | — |
Pengecekan otomatis
Berjalan 13 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauLolos
- Lisensi open source (OSI)Lolos
- Ada commit atau release dalam satu tahun terakhirLolos
- Nama package tidak mirip dengan package populerLolos
- Remote endpoint menggunakan HTTPSTidak diperiksa
- Tools yang bersifat destruktif telah diberi labelLolos
- Tidak ada instruksi tersembunyi untuk modelLolos
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
README
Lihat di GitHub🧠 DevMemory
Persistent, local-first memory for AI coding agents. An MCP server and CLI for Claude Code, Cursor and other MCP clients.
Stop re-explaining your codebase. DevMemory remembers your project's decisions, architecture, debugging lessons and conventions across AI sessions. It runs 100% on your machine.
Quick start · Claude Code · Cursor · MCP tools · CLI · Security · Docs
✨ Why DevMemory?
AI coding assistants like Claude Code and Cursor forget everything when a session ends. Every new conversation, you explain the same architecture, the same "we tried X and it broke", the same team conventions.
DevMemory gives your AI agent long-term project memory through the Model Context Protocol (MCP):
| Without DevMemory | With DevMemory | |
|---|---|---|
| 🗂️ Project decisions | Re-explained every session | Saved once, retrieved automatically |
| 🐛 Debugging lessons | Rediscovered the hard way | Recalled when the same symptom appears |
| 📏 Conventions & constraints | Forgotten mid-task | Included in every relevant context bundle |
| 🔒 Privacy | Context pasted into chats | Stored locally in SQLite, never uploaded |
🚀 Features
- 🏠 Local-first and private. A single SQLite file at
~/.devmemory/. No cloud, no account, no telemetry, no network port. - 🔌 MCP server. 9 tools over stdio, verified with Claude Code. Works with any MCP client.
- 🗃️ Project-scoped memory. Each repository's knowledge is isolated, and no project can read another's.
- 🏷️ Structured memory types: decisions, architecture, debugging lessons, conventions, constraints, task context and facts. Each memory has tags, importance, confidence and an optional expiry.
- 🔎 Fast, explainable search. SQLite FTS5 full-text search with BM25 ranking, weighted by importance, confidence and recency. Every result explains its score.
- 🧾 Provenance. Every memory records where it came from: source, client, file, PR or commit reference, and timestamps.
- 🔐 Secret redaction. API keys, tokens, passwords and private keys are redacted before anything is stored.
- 🛡️ Prompt-injection aware. Retrieved memories are wrapped as untrusted data, and instruction-like content is flagged.
- ♻️ Safe lifecycle. Duplicate detection, conflict surfacing, supersede chains, reversible archiving, and hard deletes that also purge the search index.
- 📦 Import and export. Portable JSON with validation, size limits and protection against path traversal and symlinks.
- 🧰 Developer CLI. 15 commands, JSON output and meaningful exit codes for automation.
🏗️ How it works
flowchart LR
subgraph Clients
CC[🤖 Claude Code]
CU[🖱️ Cursor]
CLI[⌨️ devmemory CLI]
end
subgraph DevMemory["DevMemory (local process)"]
MCP[MCP server<br/>9 tools · stdio]
ENG[Memory engine]
SEC[🔐 Secret redaction<br/>+ validation]
RET[🔎 FTS5 / BM25<br/>ranking]
end
DB[(SQLite<br/>~/.devmemory/devmemory.db)]
CC -- JSON-RPC over stdio --> MCP
CU -- JSON-RPC over stdio --> MCP
CLI --> ENG
MCP --> ENG
ENG --> SEC --> DB
ENG --> RET --> DB
Memory across sessions
sequenceDiagram
actor Dev as Developer
participant S1 as Session 1 (Claude Code)
participant DM as DevMemory
participant S2 as Session 2 (new day)
Dev->>S1: "We chose Drizzle over Prisma because of edge runtimes"
S1->>DM: memory_save(type: decision, ...)
DM-->>S1: ✅ saved (secrets redacted, provenance recorded)
Note over S1: Session ends, the agent forgets everything
Dev->>S2: "Add a new database table"
S2->>DM: memory_context("database table")
DM-->>S2: 📋 Drizzle decision + conventions (with provenance)
S2-->>Dev: Uses Drizzle correctly, without being re-told
⚡ Quick start
Requires Node.js ≥ 22.12.
# 1. Install
npm install -g @vasikmansuri/devmemory
# 2. Verify the CLI is available
devmemory --version
# 3. Register your project
cd ~/code/my-app
devmemory init
# 4. Save knowledge
devmemory remember -t decision --title "Use Drizzle ORM" \
-c "Drizzle over Prisma: Prisma's engine binary breaks on edge runtimes." \
--tags db,orm -i 4 --source-ref docs/adr/0003.md
# 5. Find it again
devmemory search "which orm"
devmemory context "touching the data layer"
git clone https://github.com/vasikmansuri/devmemory.git
cd devmemory
npm ci && npm run build && npm link
devmemory --version
🤖 Connect Claude Code
✅ Verified end to end with Claude Code 2.1.294.
claude mcp add --transport stdio devmemory -- devmemory mcp
Share it with your team via .mcp.json:
claude mcp add --scope project --transport stdio devmemory -- devmemory mcp
Check the connection with claude mcp list or /mcp. Then try "Save to DevMemory: we deploy with Argo CD", start a new session, and ask "how do we deploy?"
💡 Claude Code starts the server in your working directory, and DevMemory finds the nearest registered project automatically, even from subfolders.
🖱️ Connect Cursor
⚠️ Configuration follows Cursor's documented format, but has not been tested end to end yet. Add this to .cursor/mcp.json:
{
"mcpServers": {
"devmemory": {
"type": "stdio",
"command": "devmemory",
"args": ["mcp", "--project", "${workspaceFolder}"]
}
}
}
🧩 MCP tools
| Tool | Description |
|---|---|
memory_save |
Save a memory. Reports duplicates and possible conflicts; can supersede older memories. |
memory_search |
Ranked keyword search with type, tag and status filters. |
memory_get |
Fetch one memory with links and lifecycle history. |
memory_update |
Edit in place; previous values are kept in history. |
memory_forget |
Archive (reversible) or permanently delete (confirm: true). |
memory_list |
Paginated, filtered listing. |
memory_context |
A token-budgeted context bundle for the current task. |
memory_link |
Relate memories: depends_on, conflicts_with, … |
memory_stats |
Project statistics. |
⌨️ CLI reference
| Command | Purpose |
|---|---|
devmemory init |
Register the current directory as a project |
devmemory remember |
Save a memory (-c - reads stdin) |
devmemory search <query> |
Ranked keyword search |
devmemory get <id> |
Full memory with provenance and history |
devmemory list |
Browse with filters and pagination |
devmemory context [query] |
The context bundle an agent receives |
devmemory update <id> |
Edit a memory |
devmemory forget <id> |
Archive, or --hard --yes to delete |
devmemory link <a> <b> |
Link two memories |
devmemory stats · projects · doctor |
Statistics, project list, health checks |
devmemory export · import |
Portable JSON backup and restore |
devmemory mcp |
Run the MCP server (stdio) |
Add --json to any command for machine-readable output.
Exit codes: 0 ok · 1 internal error · 2 validation · 3 not found · 4 project not initialized · 5 conflict · 6 database error · 7 I/O or unsafe path.
📊 Search quality (measured, not claimed)
These numbers come from 36 labelled queries over a 46-memory test project (npm run eval):
| Metric | All queries | Direct wording | Paraphrased |
|---|---|---|---|
| Recall@5 | 0.944 | 1.000 | 0.750 |
| MRR | 0.922 | 1.000 | 0.650 |
| Precision@5 (max achievable 0.228) | 0.217 | 0.229 | 0.175 |
DevMemory uses keyword search, not semantic search, so paraphrased questions with no shared words can miss. Semantic search is on the roadmap.
🔐 Security & privacy
- ✅ Runs locally: no telemetry, no network listener, no external API calls.
- ✅ Secrets are redacted before storage, covering AWS keys, GitHub tokens, OpenAI and Anthropic keys, JWTs, private keys and passwords.
- ✅ The database file is readable only by your user (mode
0600). - ✅ Projects are isolated, and all SQL is parameterized.
- ✅ Retrieved memories are treated as untrusted data, never as instructions.
- ⚠️ The database is not encrypted at rest. Use full-disk encryption for extra protection.
Read more in the security model and SECURITY.md.
⚙️ Configuration
| Variable | Default | Purpose |
|---|---|---|
DEVMEMORY_HOME |
~/.devmemory |
Data directory |
DEVMEMORY_PROJECT |
current dir | Project to use |
DEVMEMORY_SECRET_POLICY |
redact |
redact or reject writes containing secrets |
DEVMEMORY_EXTRA_TYPES |
— | Extra memory types, comma-separated |
DEVMEMORY_LOG_LEVEL |
warn |
Log level (stderr only) |
📚 Documentation
Architecture · Memory model · Security model · MCP integration · Troubleshooting · Retrieval evaluation · Roadmap · Contributing · Changelog
🛣️ Roadmap
- Local MCP server, CLI, FTS5 search, secret redaction, project isolation
- Verified Claude Code integration
- Optional local embeddings for semantic search
- End-to-end verified Cursor integration
- Better tokenization for Chinese and Japanese text
- Opt-in encryption at rest
🤝 Contributing
Contributions are welcome! Run npm run check (typecheck, lint, 129 tests, build) and see CONTRIBUTING.md.
⚠️ Known limitations
- Keyword search only (no semantic search yet).
- Chinese and Japanese text is tokenized coarsely.
- Moving a project folder requires running
devmemory initagain. - The Cursor integration is unverified.
📄 License
MIT © Vasik Mansuri
If DevMemory saves you from re-explaining your codebase, please ⭐ star the repo!
Keywords: AI memory · MCP server · Model Context Protocol · Claude Code memory · Cursor MCP · AI coding assistant · persistent context · long-term memory for LLM agents · local-first · SQLite FTS5 · developer tools
Support
If this project is useful to you, you can support my open-source work:
Pertanyaan tentang devmemory MCP
Bagaimana cara menambahkan devmemory MCP ke Claude Code?
Jalankan claude mcp add devmemory -- npx -y @vasikmansuri/devmemory di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan devmemory MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Tool apa yang disediakan devmemory MCP?
Server ini menyediakan 9 tool, termasuk memory_save, memory_search, memory_get, memory_update, memory_forget.
Bagaimana cara menangani informasi sensitif seperti API keys?
Server melakukan redaction pada secret, seperti menutupi AWS keys, GitHub tokens, dan kredensial pribadi lainnya sebelum data disimpan.
Apakah mendukung semantic search?
Saat ini, sistem menggunakan SQLite FTS5 full-text keyword search alih-alih semantic search, namun semantic search sudah masuk dalam roadmap pengembangan.
Bisakah saya menggunakannya dengan Claude Code?
Ya, sudah terverifikasi secara end-to-end dengan Claude Code.