Giving Claude Persistent Goal Memory Across Conversations
An MCP server that detects goal-setting language in natural speech and persists those goals across every Claude interface, so context survives between chats.
The annoyance that produced this project is one every heavy Claude user knows. You say "fix the auth system" in one conversation, do some work, come back the next day in a fresh chat, and Claude has no memory of what you were doing. MCP Goal Persistence Server fixes that by giving Claude durable memory for long-term goals across conversations.
Detecting goals instead of demanding commands
The design choice I am proudest of is that there are no new commands to learn. The server auto-detects goal-setting language from how people already talk. Say "fix the auth bug until finished," "keep working on the API refactor," or "iterate on the design doc until they match," and it recognizes the intent and persists it. It understands several pattern families: until-patterns that imply a completion condition, keep and continue patterns that imply ongoing work, and process patterns like "build and test with playwright repeatedly."
That matters because the whole value proposition collapses if using the tool is itself friction. A memory system you have to remember to invoke is a memory system you will forget to invoke. By reading natural language and requiring zero workflow changes, it stays out of the way and still catches the goals worth keeping.
Persisting across every Claude surface
The other half of the problem is that memory only helps if it follows you. This server persists goals across all Claude interfaces, so a goal set in the CLI is still there in Desktop and in Cursor. Beyond just the goal statement, it tracks progress and context, remembering what has been tried and where you left off. Storage is local, kept in your project directory, which keeps the goals close to the work they belong to and avoids shipping your intentions off to somewhere else.
The takeaway
Building this reinforced something about how memory should feel: the best persistence layer is invisible. The failure mode of most "remember this" features is that they add ceremony. By detecting goals from ordinary phrasing, storing them locally, and surfacing them everywhere Claude runs, this server makes continuity the default instead of a chore. You just talk, and the thread you were pulling on is still there when you come back.
Have something that needs building, or stabilizing?
These notes are the work log. The paid work runs through Moonshine Labs, my product and engineering studio. Tell us what you're building, or grab a call.
Work with us →