TMCRA Agent Memory runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 18 Aug 2026.
Role-aware Agent memory with cross-session recall, durable writes, and multi-Agent project scope.
What the code does
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.
return subprocess.run(
environment = dict(os.environ)
# Directory inspectors need to initialize the stdio server and enumerate tools. # This public placeholder is never used for a production API request. ENV TMCRA_API_KEY=directory-inspection-placeholder \
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 TMCRA Agent Memory
same job, measured the same wayCross-session, cross-device memory for your agent: remember and recall notes. No key to start.
Durable project-memory MCP: decisions, constraints, and pipelines across Claude sessions.
Local-first durable AI memory with policy-bound recall and a typed project graph.
Persistent memory for AI agents. Search, store, and recall across sessions.
Persistent memory for AI agents. Store, recall, and share knowledge across sessions.
AI agent memory: task tracking, scoped work packages, decisions, and cross-session continuity
Issue tracker and durable project memory for your coding agent, scoped to the folder you open.
Durable user/project memory for MCP clients: recall context and remember selected facts.
TMCRA Agent Memory — questions
Answers built from our own checks of this server.