TMCRA Agent Memory MCP server

<!-- mcp-name: io.github.reshuibuduo/tmcra-mcp-server -->

TMCRA MCP Server

TMCRA MCP Server gives MCP hosts explicit access to long-term Agent memory. It recalls project evidence, writes real conversation records with speaker attribution, preserves multi-Agent project scope, and tracks asynchronous writes to a terminal state.

中文说明

What it provides

• Cross-session project continuity. Recall bounded evidence from one stable project scope.
• Cross-tool collaboration. Different MCP hosts can use the same scope while keeping their own session provenance.
• Speaker and Agent attribution. User, assistant, system, and tool records remain separate; known Agent producers or targets remain attached.
• Explicit turn lifecycle. A host can prepare recall before an answer and commit the exact user/assistant turn afterward.
• Durable write recovery. Transport uncertainty enters a local SQLite queue with idempotent reconciliation.
• Verifiable receipts. Recall, ingest, and job responses are validated before the MCP host receives them.
• Nine MCP tools. Recall, ingest, prepare, commit, reconcile, get job, wait for job, session memory controls, and targeted feedback.

tmcramemorycontrol exposes task selection, a 12000-character default recall budget, and normal, recallonly, off modes. Pass the exact same sessionid to recall/prepare and controls. Pending older generations are discarded after a mode change; already submitted jobs remain submitted. tmcrafeedback supports ignore, correct (user-supplied replacement), and restore with a stable idempotency key. Effective feedback requires the matching backend update; check correctionindex_status separately. The visual control panel is provided by the Codex and DSH distributions. This MCP package automatically discovers the shared local installation; numeric loopback HTTP is permitted only for an explicit local identity. Hosted connections require HTTPS.

Conversational corrections now require interactive host confirmation. On an actual correction request, call tmcramemorycontrol(operation="correctionstart") before clarification or feedback to suppress automatic capture of that discussion turn. tmcrafeedback reads exact original evidence and uses MCP form elicitation to show the source, replacement and scope; only explicit acceptance submits feedback. Rejection, cancellation, expiry or an unsupported host leaves memory unchanged. Do not substitute ingestion for a rejected correction. Host lifecycle turn IDs protect the discussion from later queue replay while preserving other identified turns. A third-party host must route elicitation to its user; the server cannot guarantee that an arbitrary client will not answer automatically. Hypothetical/quoted correction language is not authorization.

Generic MCP clients decide when to call tools. Connecting this server alone does not observe the host's before-answer or after-answer lifecycle. For automatic Codex recall and capture, install the separate TMCRA Codex Memory plugin.

Install

MCPB release

Shortened. The full README is on GitHub.