Local-first memory + judgment layer for AI coding agents — warns before repeating failed fixes.
If you already use Projectmem, the projectmem mcp server is the piece that lets your assistant work with it directly. Local-first memory + judgment layer for AI coding agents — warns before repeating failed fixes.
We don't make AI smarter. We make it experienced. AI coding memory — the local-first memory + judgment layer for AI coding agents. Save up to 50%+ of AI tokens. Stop repeating yesterday's bug.
projectmem is an open-source agent memory layer built for that job. It is local-first: memory lives in a plain .projectmem/ directory inside your repository, with no cloud, no account and no telemetry. A native MCP server exposes 15 tools to Claude Code, Claude Desktop, Cursor, Antigravity and Codex, so your agent reads memory and logs its work on its own.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Pre — Commit Warnings** — pjm precheck warns you before you commit if you're about to repeat a failed approach, modify a high-churn file, or touch anStale — Memory Detection** (new in 0.1.4) — other memory tools silently decay or delete old memories; projectmem never deletes. Every decision thatSession — Start Briefing** (new in 0.1.4) — pjm brief answers "where was I?" in one screen: active warnings, possibly-stale memories, open issues, recentCross — Project Memory** — Lessons learned in one repo follow you forever. Library gotchas, decisions, and patterns live in ~/.projectmem/global/ andReal — time File Watcher** — Background daemon detects rapid edits to the same file (debugging sessions) between commits. Battery-aware, gitignore-awaremacOS — ** Claude menu → Settings… → Developer tab → Local MCP servers → Edit ConfigDoc — What's in itCapability — projectmemPrice — ✅ Free · MITCursor — Two ways to register the MCP server — pick whichever fits your workflow:Antigravity — 1. Open the Agent window (the chat panel on the right). 2. Click the ⋯ Additional Options button in the panel header. 3. Choose **MCPCodex — Codex stores MCP config as TOML (not JSON) in ~/.codex/config.toml. There's a UI form at Settings → MCP Servers → Add MCP Server, but duringInstallation goes through your MCP client rather than a global install: point it at projectmem on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Projectmem's toolset — Pre, Stale, Session and 9 more — is a fair guide to whether it matches your workflow. It is maintained by Ripon Chandra Malo; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Pre | Commit Warnings** — pjm precheck warns you *before* you commit if you're about to repeat a failed approach, modify a high-churn file, or touch an unresolved issue. No other AI tool does this — it requires the memory laye |
| Stale | Memory Detection** *(new in 0.1.4)* — other memory tools silently decay or delete old memories; projectmem **never deletes**. Every decision that cites a file is cross-checked against that file's git history — when the f |
| Session | Start Briefing** *(new in 0.1.4)* — pjm brief answers "where was I?" in one screen: active warnings, possibly-stale memories, open issues, recent decisions, stack gotchas, and your prevention score with a week-over-week |
| Cross | Project Memory** — Lessons learned in one repo follow you forever. Library gotchas, decisions, and patterns live in ~/.projectmem/global/ and auto-inherit into every new project that matches your stack. |
| Real | time File Watcher** — Background daemon detects rapid edits to the same file (debugging sessions) between commits. Battery-aware, gitignore-aware, auto-started by pjm init. |
| macOS | ** Claude menu → Settings… → Developer tab → **Local MCP servers** → **Edit Config**. |
| Doc | What's in it |
| Capability | **projectmem** |
| Price | ✅ Free · MIT |
| Cursor | Two ways to register the MCP server — pick whichever fits your workflow: |
| Antigravity | 1. Open the **Agent** window (the chat panel on the right). 2. Click the **⋯ Additional Options** button in the panel header. 3. Choose **MCP Servers** → **Manage MCP Servers** → **Add new** (or **Edit Config**). |
| Codex | Codex stores MCP config as **TOML** (not JSON) in ~/.codex/config.toml. There's a UI form at Settings → MCP Servers → Add MCP Server, but during cross-client verification the form's **Save button didn't reliably persist* |
{
"mcpServers": {
"projectmem": {
"command": "uvx",
"args": ["projectmem"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.