MCPStale – project memory that expires

Expires AI coding agents' project memory when the code changes

Problem

AI coding tools either forget project context between sessions or remember facts that quietly stopped being true. Tell an agent 'we use Postgres', migrate to MySQL two weeks later, and it keeps building on the old fact. Users need one shared project memory across Claude Code, Cursor, and Codex that goes stale with the code.

Solution

An MCP server that keeps memory entries per project with sources and freshness; when related files or commits change, it marks matching memories as 'needs confirmation' and asks the user to review, so agents don't keep acting on stale facts. The point isn't remembering more—it's remembering what expires.

Users

Indie developers and small engineering teams using multiple AI coding tools on long-lived projects

MVP

MCP server shared by Claude Code, Cursor, and Codex; manual or semi-automatic fact entry; bind facts to file paths or commits; mark memories stale when code changes; surface pending items during sessions

Revenue

Open-source core plus a hosted team sync subscription; or seat-based self-hosted licenses

Why now

MCP makes cross-tool memory practical, and AI coding is entering long-lived projects where remembering the wrong thing is worse than remembering nothing. Small teams can build this themselves.