About
One neutral memory of you that every agent plugs into — kept honest by a quality gate.
Jamgate is a neutral, cross-agent memory quality gate, delivered as an MCP server. The goal is simple: give a person one shared memory of who they are, how they're doing, and what they're working on — and let every MCP-capable agent (Claude Code, Cowork, Cursor, and others) read from and write to that same memory.
The hard part isn't storing memories; it's keeping shared memory clean. Most systems store everything and slowly fill with duplicates, trivia, and stale state. Jamgate sits in the write path and acts as a gate. A memory is kept only if it is durable and would change a future answer. The gate drops exact duplicates, and because every memory is a timestamped event, a newer fact supersedes an older one by recency rather than piling up as a contradiction.
It runs locally, so your memory stays on your machine, and it is store-agnostic — a built-in flat-file store by default, with the option to bring your own.
The MCP tools today
- save_memory
- recall_memory
- forget_memory
The core works end to end over the MCP protocol, with a rule pre-filter, duplicate detection, and time-aware supersession. Next up: a classifier for ambiguous cases, contradiction handling, and multi-device sync — built in the open.
Jamgate is open source and MIT-licensed. The aim is impact, not profit.
About the author
This blog is written by jam, who builds Jamgate. It's a working log — design decisions, dead ends, and what shared memory should actually do.