promem-mcp
This server provides AI coding agents with persistent, searchable project memory and context management across sessions.
Search project context (rules, decisions, conventions, facts) with token-budgeted retrieval
Save, update, delete, and fetch memories with provenance, confidence, and tags
Retrieve project information, rules, and technical/architecture decisions
Get recent memories and session summaries for continuity
Access Git intelligence: commits, changed files, branches, TODOs/FIXMEs
Inspect environment details: Python version, venv, dependencies, Docker, .env status
Run environment diagnostics and health checks
Generate compact handoff summaries for switching between agents or sessions
Detects Docker environment as part of environment diagnostics and context gathering.
Provides Git context including recent commits, changed files, and TODOs/FIXMEs from the repository.
Can be installed via pipx as a global CLI tool for project context management.
Detects pytest as a test framework during project detection.
Detects Python version, venv status, and other Python environment information as part of project context.
Uses SQLite for persistent memory storage with FTS5 search capabilities, no external database required.
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., "@promem-mcp Save a decision: use React for frontend."
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.
Promem-MCP
Project Memory MCP — persistent project context for AI coding agents. Built by DIP-RO.
pip install promem-mcpNo database setup. No cloud. No daemon. No manual config.
Promem-MCP is a local-first, MCP-native context runtime that gives AI coding agents persistent project understanding — architecture, rules, decisions, conventions, environment intelligence, and Git context — without repeated explanations or context waste.
Quick Start
pip install promem-mcpThat's it. On first run, Promem-MCP auto-detects and auto-configures all your installed AI coding clients (Cursor, Claude, VS Code, Cline, etc.). Just restart your AI client after install.
Prefer manual control?
# See which clients are detected
promem config
# Auto-configure all detected clients at once
promem config --all
# Configure a specific client
promem config cursor
promem config claude-code
promem config vscodeOr manually add to your client's MCP config:
{
"mcpServers": {
"promem-mcp": {
"command": "promem",
"args": []
}
}
}VS Code note: VS Code uses
"servers"key, not"mcpServers". Runpromem config vscodefor the correct format.
Related MCP server: Tages
How It Works
Features
Zero-setup storage — SQLite database created automatically in OS-appropriate directory
Automatic project detection — language, framework, package manager, test framework
Persistent memory — rules, decisions, conventions, environment facts, Git intelligence
Token-efficient retrieval — FTS5 search with token budgeting, returns only relevant context
Provenance tracking — every memory knows where it came from and how confident it is
Secret redaction — API keys, tokens, passwords are never stored or returned
Project isolation — project memories never leak across projects
Stale context detection — flags memories that conflict with current project state
Contradiction detection — identifies conflicting project rules
Session continuity — handoff summaries for switching between agents/sessions
Git intelligence — recent commits, changed files, TODOs/FIXMEs
Environment diagnostics — Python version, venv, .env completeness, Docker
Local-first — no network requests, no cloud, no external services
MCP Tools
Tool | Description |
| Search persistent project context with token budget |
| Get a specific memory by ID |
| Save a memory, decision, rule, or fact |
| Update an existing memory |
| Delete a memory |
| Get current project information |
| Get all project rules and conventions |
| Get all technical/architecture decisions |
| Get recent memories and latest session |
| Get Git intelligence |
| Get environment intelligence |
| Run environment diagnostics |
| Get compact project summary for handoff |
CLI
contextmcp --version # Version
promem status # Project + storage status
promem doctor # Health checks
promem stats # Usage statistics
promem search "query" # Search context
promem memory list # List memories
promem decision "text" # Save a decision
promem privacy # Privacy info
promem config # Client configuration
promem repair # Rebuild index, optimize DB
promem reset # Delete all data (with confirmation)Client Support
Client | Auto-config? | Config Key |
Claude Code |
|
|
Claude Desktop |
|
|
Cursor |
|
|
VS Code / Copilot |
|
|
OpenCode |
|
|
Gemini CLI |
|
|
Windsurf |
|
|
Cline |
|
|
Roo Code |
|
|
Amazon Q |
|
|
ZCode (GLM/Zhipu) |
|
|
Tabnine |
|
|
No client supports true zero-config auto-registration. ContextMCP detects installed clients, offers to write config (with backup + merge), and provides exact copy-paste snippets.
Privacy
Local only — no network requests
Project contents not uploaded
Secrets redacted — never stored or returned
No cloud dependencies
promem privacyStorage Location
ContextMCP uses project-local storage — no centralized OS directory, no wasted space.
Location | Path |
Project-local (default) |
|
Each project gets its own .contextmcp/contextmcp.db. Storage travels with the project. No global storage bloat.
Add .contextmcp/ to your .gitignore (already included by default in ContextMCP's ignore patterns).
Override with CONTEXTMCP_DATA_DIR environment variable if needed.
Installation
# pip
pip install promem-mcp
# uv
uv add promem-mcp
# pipx (global CLI)
pipx install promem-mcpWorks in venv, virtualenv, uv, pipx, and system Python.
Development
git clone https://github.com/DIP-RO/MCP_Package.git
cd MCP_Package
pip install -e ".[dev]"
pytestLicense
MIT
Available Tools
13 toolsctx_decisionsA
Get all technical/architecture decisions with reasoning.
Inputs: no named parameters. Returns: result
ctx_deleteC
Delete a memory from persistent context.
Inputs: memory_id (required). Returns: result
ctx_diagnosticsA
Run environment diagnostics: missing env vars, config issues, health checks.
Inputs: no named parameters. Returns: result
ctx_environmentA
Get environment intelligence: Python version, venv, dependencies, Docker, .env status.
Inputs: detailed. Returns: result
ctx_getB
Get a specific memory by its ID with full provenance.
Inputs: memory_id (required). Returns: result
ctx_gitB
Get Git intelligence: recent commits, changed files, branches, TODOs/FIXMEs.
detail can be: summary, commits, files, todos
Inputs: detail. Returns: result
ctx_projectA
Get current project information: name, language, framework, root, git status.
Inputs: no named parameters. Returns: result
ctx_recentC
Get recent memories and latest session summary for continuity between sessions.
Inputs: limit. Returns: result
ctx_rulesA
Get all project rules and coding conventions.
Inputs: no named parameters. Returns: result
ctx_saveA
Save a memory, decision, rule, or fact to persistent context.
Use this to store technical decisions, project rules, coding conventions, or any important context that should persist across AI coding sessions.
Inputs: content (required), tags, type, scope, +4 more. Returns: result
ctx_searchA
Search persistent project context for rules, decisions, conventions, and facts.
Use this BEFORE writing code to understand project patterns and avoid inconsistencies. Returns relevant memories within the specified token budget.
Inputs: query (required), limit, scope, context_pack, +1 more. Returns: result
ctx_summaryA
Get a compact project context summary for handoff between sessions or agents.
Includes project info, key rules, recent decisions, environment status, and latest session.
Inputs: no named parameters. Returns: result
ctx_updateC
Update an existing memory. Only provided fields are changed.
Inputs: memory_id (required), tags, content, confidence, +1 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Each tool targets a distinct concern (search, get, save, update, delete, project info, etc.) with clear descriptions, making it easy for an agent to choose the right one. No two tools overlap in purpose.
There is a deep inconsistency: most tools use a 'ctx_' prefix (ctx_search, ctx_get, ctx_save, etc.), but a few tools like 'ctx_git', 'ctx_environment', and 'ctx_diagnostics' do not follow this pattern. Additionally, 'ctx_git''s description includes a confusing 'detail' parameter that is not shown in the tool name, breaking the expected consistency.
13 tools is a reasonable count for a project-context memory server, covering search, CRUD for memories, project info, environment, and session summaries. Each tool has a distinct purpose and earns its place.
The tool set covers core memory operations (CRUD), project info, decisions, rules, environment diagnostics, and session continuity. There are no obvious dead ends for common agent tasks like retrieving, storing, updating, or searching context. Minor gap: no tool for batch operations or listing all memories.
Maintenance
Related MCP Connectors
Long-term memory for AI coding agents: durable project facts, recalled by every MCP client.
Persistent memory, knowledge graph, task management and more for AI agents via MCP.
Team memory for AI coding agents and code reviews, reviewed by humans and served over MCP.
Share one project context across ChatGPT, Claude, Telegram and any MCP client.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that provides persistent project context, workflow management, and knowledge capture for AI coding agents. It enables agents to maintain structured memory across sessions by tracking project profiles, conventions, skills, and technical debt.7-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to maintain persistent, cross-session memory of codebase architecture, naming conventions, and decisions through MCP tools. Eliminates repetitive project re-explanation by automatically injecting stored context into every session with local-first SQLite storage and optional team sharing capabilities.4MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides persistent, cross-session memory and team knowledge sharing for AI development workflows. It enables project DNA scanning, semantic search, context budgeting, and git-aware indexing to prevent AI context loss between sessions.44 npmMIT
- AlicenseBqualityDmaintenanceMCP server that provides cross-session persistent memory for AI coding assistants using local vector database and semantic search, enabling automatic recall of project context, issues, and tasks.9114 PyPI92Apache 2.0