Agent Memory MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 25 Sep 2026.
Memory, docs, and repo context layer for engineering agents.
What the code does
We read the source, 1 d ago · rules ccca72095570
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.
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 Agent Memory MCP
same job, measured the same wayToken-bounded repository context for coding agents over MCP.
Local codebase memory and repository code search for Codex, Claude Code, and MCP coding agents.
The local context engine for AI coding agents: ranked files, context packs and a code graph.
Autopilot MCP server for GEO analyses, reports, content, audits, memories and agents.
Local-first engineering cognition for AI coding agents — persistent memory over your codebase.
Local code graph and solution memory for coding agents via CLI and MCP.
Efficient context management: code search, evidence packs, and memory for coding agents.
Read-only MCP server for markdown and agent steering files: read, outline, lint, context budget.
Agent Memory MCP — questions
Answers built from our own checks of this server.