MemAuthority runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 8 Sep 2026.
Git-backed long-term memory authority for AI agents via MCP.
What the code does
We read the source, 21 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
raw, err = gitview.ReadFile(service.root, service.head, filepath.ToSlash(filepath.Join(projectID, filename)))
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to MemAuthority
same job, measured the same wayA lightweight, Git-backed permanent memory for AI agents.
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
Local-first, governable long-term memory for AI coding agents
Shared long-term memory vault for AI agents with 20 MCP tools.
Git-backed org memory for AI agents — hybrid search, tables, files & a URI graph over MCP.
Secure, fragment-based long-term memory for MCP-compatible AI agents.
Local-first governed MCP memory backend for coding agents.
Self-hosted long-term memory for AI agents over MCP — hierarchical recall backed by pgvector
MemAuthority — questions
Answers built from our own checks of this server.