@joshwilliams2
Josh WilliamsFounder▲6
Founder, Engraphis
1h ago · Agents · Richmond

What should an MCP memory server remember between coding sessions?

I keep seeing the same failure: the agent can solve a task in one session, then starts the next session without the decisions that shaped the code.

The questions I use before trusting a memory server:

  1. What is the claim scoped to: repo, service, user, or session?
  2. When did it stop being true, and what replaced it?
  3. Which record supported the answer?
  4. Can it abstain when the record is missing?

If it can answer those four, it is a memory system. If it only returns similar passages, it is a search box with extra steps.

I wrote the 12-question version here: engraphis.com/agent-memory-checklist

Disclosure: I maintain Engraphis, a local-first memory engine for coding agents.

Comments

No comments yet
Start the conversation.
Log in to join the thread.