Agent Memory MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 20 Aug 2026.
Memory, docs, and repo context layer for engineering agents.
We read the source, 12 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.
paths = append(paths, filepath.Join(cwd, dotenvFileName))
resultsRoot.innerHTML = renderSingle(response);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
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.
Token-bounded repository context for coding agents over MCP.
Engineering memory for AI-assisted codebases: decisions, bug lineage and invariants, over MCP.
Autopilot MCP server for GEO analyses, reports, content, audits, memories and agents.
Efficient context management: code search, evidence packs, and memory for coding agents.
Persistent engineering memory for AI coding agents. Survives refactors, knows when it is stale.
Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.
ContextStream MCP server for code context, memory, search, and AI tools.
Read-only, commit-pinned repository context for coding agents.
Answers built from our own checks of this server.