Install
$ agentstack add mcp-bhavindivecha-devmemoryos ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Super Memory
Open-source, self-hosted memory infrastructure for AI coding workflows.
Super Memory gives Codex/Claude/Cursor/Windsurf a shared long-term memory layer with safe review workflows, repo scanning, and MCP integration.
What It Solves
- Avoid repeating project context in every new AI chat.
- Store durable technical decisions, repo rules, preferences, and architecture notes.
- Keep memory quality high with duplicate/conflict/stale detection and review queues.
- Reuse the same memory across tools via API + MCP.
Core Features
Phase 1: Core Memory Platform
- Fastify + TypeScript API with JWT auth.
- PostgreSQL + pgvector memory store.
- Memories CRUD, archive/restore, bulk archive.
- Projects/Clients/Repos CRUD and tagging.
- Keyword/semantic-ready search.
- API keys (hashed, shown once).
- JSON import/export.
- Docker Compose local stack.
Phase 2: MCP Integration
apps/mcp-serveras your own MCP package.- API-key authenticated MCP access to Super Memory API.
- Tools:
memory_searchmemory_get_user_preferencesmemory_get_project_contextmemory_get_repo_rulesmemory_get_decision_historymemory_suggestmemory_save(guarded by mode)- Write modes:
readonly,suggest,direct. - MCP audit logging in API.
Phase 3: CLI + Repo Scanner
apps/clicommand:supermemory.- Commands:
init,login,logout,set-api-keydoctor,scan,push,pull,export,import- Repo scanning detects stack/rules/routes/models/env templates/docker.
- Generates pending memory suggestions +
.supermemory/context.md. /scan-resultsdashboard review/apply flow.
Phase 4: Smart Memory Engine (MVP)
- Smart analysis on memory creation.
- Duplicate detection + review items.
- Conflict detection + review items.
- Quality scoring + low-quality flags.
- Memory relation graph table.
- Memory review center UI.
- Worker scaffold (
apps/worker) + queue foundation.
Architecture
flowchart TD
U["Developer / AI Agent"] --> WEB["Web Dashboard (apps/web)"]
U --> CLI["CLI (apps/cli)"]
U --> MCP["MCP Server (apps/mcp-server)"]
WEB --> API["Super Memory API (apps/api)"]
CLI --> API
MCP --> API
API --> DB["PostgreSQL + pgvector"]
API --> REDIS["Redis"]
WORKER["Smart Worker (apps/worker)"] --> REDIS
WORKER --> API
Memory Lifecycle Flow
flowchart LR
A["Memory created/suggested/imported/scanned"] --> B["Smart analysis"]
B --> C["Duplicate/Conflict/Quality checks"]
C --> D["Review item created"]
D --> E["User review in /memory-review"]
E --> F["Approve / Reject / Ignore / Merge / Replace"]
F --> G["Clean active memory for MCP + search"]
Monorepo Structure
super-memory/
├── apps/
│ ├── api/
│ ├── web/
│ ├── mcp-server/
│ ├── cli/
│ └── worker/
├── packages/
│ └── shared/
├── docs/
├── docker-compose.yml
└── README.md
Quick Start (Local)
Prerequisites
- Node.js 20+
- npm 10+
- Docker + Docker Compose
Setup
cd /Volumes/BhavinDivecha/Projects/DevMemoryOS/super-memorycp .env.example .env- Update
.env:
JWT_SECRETOPENAI_API_KEY(optional)SUPER_MEMORY_API_KEY(for MCP tests)
- Install deps:
npm install - Prisma sync:
npm run db:generate -w @super-memory/apinpm run db:migrate -w @super-memory/api
- Start services:
- Core stack:
docker compose up --build - With worker profile:
docker compose --profile worker up --build - With mcp profile:
docker compose --profile mcp up --build
Local URLs
- API:
http://localhost:4000 - Web:
http://localhost:5173 - Postgres:
localhost:5432 - Redis:
localhost:6379
How to Use
1) Web Dashboard
- Register/login.
- Create Project/Client/Repo.
- Create memories tagged to scope.
- Search/filter memories.
- Use
/memory-reviewfor smart suggestions. - Use
/scansto apply scanner-generated memories.
2) CLI Workflow
supermemory init --project "Algo Trading" --repo "algo-trading"- Authenticate:
- API key mode:
supermemory set-api-key - or user mode:
supermemory login
- Validate setup:
supermemory doctor - Scan repo:
supermemory scan . --push --pending - Review/apply in dashboard
/scans.
3) MCP Workflow (Codex/Claude)
- Create API key in dashboard.
- Configure MCP server env with that key.
- Start MCP server.
- In coding chat, tools can pull project context, repo rules, preferences, and decisions.
Deploy Steps
Option A: Single VM (Recommended first)
- Provision Linux VM.
- Install Docker + Docker Compose.
- Copy project or use your published Docker images.
- Set production
.envvalues. - Run:
docker compose up -ddocker compose --profile worker up -d
- Put Nginx/Caddy in front for TLS + domain routing.
- Backup Postgres volume regularly.
Option B: Image-Only Distribution (for users)
- Ship only Docker images + a
docker-compose.yml+.env.example. - Users configure env and run
docker compose up -d. - No source code required on user machine.
Test Steps
API + Web Smoke Test
- Register/Login.
- Create project/client/repo.
- Create memory (active + pending).
- Search memory.
- Export JSON.
- Import JSON.
- Create API key.
Smart Memory Smoke Test
- Create two near-duplicate memories.
- Open
/memory-review. - Confirm duplicate/conflict items appear.
- Approve/reject and verify status updates.
CLI Smoke Test
supermemory doctorsupermemory scan . --dry-runsupermemory scan . --push --pending- Confirm scan appears in
/scans.
MCP Smoke Test
- Set valid
SUPER_MEMORY_API_KEY. - Call
memory_get_project_contextfor existing project. - Call
memory_searchand verify relevant results. - Call
memory_suggestand verify pending memory created.
Security Notes
- Passwords are hashed.
- API keys are stored hashed and shown once.
- Data is user-isolated.
- Smart actions are review-driven, not destructive by default.
- Do not store passwords/private keys/customer-sensitive secrets.
Useful Docs
- CLI: [
docs/phase3-cli.md](docs/phase3-cli.md) - MCP setup: [
docs/codex.md](docs/codex.md), [docs/claude-code.md](docs/claude-code.md) - MCP tools: [
docs/mcp-tools.md](docs/mcp-tools.md) - Security: [
docs/security.md](docs/security.md)
Support This Project
If Super Memory helps you, support development:
- Patreon: Patreon link
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: BhavinDivecha
- Source: BhavinDivecha/DevMemoryOS
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.