MemAuthority — MCP server for Git-backed agent memory
An MCP server that keeps a project's long-term memory in Git, so a new session or another machine picks up accumulated context instead of rediscovering it.
Open on GitHubWhat MemAuthority does
MemAuthority exposes long-term project memory to an agent over MCP. The memory lives in a Git repository, which is what makes it portable across sessions and machines. The agent handles retrieval, summarising, updates and pruning; you decide what deserves to stay.
Writes go through version checks (CAS), so a stale revision cannot quietly overwrite fresher content. Retries after a dropped connection or an aborted run do not create duplicates, and interrupted writes are journalled and recovered. The working memory stays compact while Git keeps the full revision history. Loading happens on demand — nothing pulls the whole vault into the context window unless the task calls for it.
This suits projects where memory has outgrown a note and become state that later sessions rely on. Small, rarely changing memory is fine in a plain MEMORY.md. You need a Git repository to hold the memory; no API key or hosted service is involved.
What it helps with
- recover project context in a fresh session without rereading the codebase
- save task conclusions so they never have to be rediscovered
- drop obsolete entries that mislead the agent
- stop a stale revision from overwriting fresh memory during parallel runs
- park an idea in TODO without cluttering the current context
Example prompts for the agent
- Check this project's MemAuthority and pull in only what you need.
- Record this task.
How to install MemAuthority
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about MemAuthority
How do I install MemAuthority in Claude Code?
There are no ready-made install commands for Claude; the server is wired up manually through MCP configuration. Check the iasi777/memauthority repository for how to start it.
What does MemAuthority do?
It stores a project's long-term memory in Git and serves it to the agent over MCP. The agent reads the entries a task needs, updates them, and prunes what no longer holds.
How is MemAuthority different from a plain MEMORY.md?
MEMORY.md is simpler and enough for a small memory store. MemAuthority adds version checks, duplicate protection, crash recovery, and a full revision history in Git.
