MemoryGuard MCP server

MemoryGuard

<!-- mcp-name: io.github.irisxc4/memoryguard -->

Governed shared memory for coding agents. Local-first MCP memory with automatic organization, scoped rules, evidence, and rollback.

中文文档

Let agents write without turning shared memory into an unreviewed pile.

MemoryGuard organizes each write, preserves the evidence behind changes, and

keeps governance decisions reversible.

**No account. No remote server. No remote telemetry. Local-only usage telemetry

is optional and stores bounded, privacy-preserving aggregates locally.**

Quick start · Upgrade · Knowledge Library · Architecture · Supported hosts · Privacy and safety

A synthetic governed projection: signals move through memory categories while raw conversation text remains outside the graph.

What's New in v0.7.12

v0.7.12 improves MCP discovery, bounded read delivery, and local usage telemetry while preserving the existing governed action checks and MCP name:

day-to-day tools from tools/list, including capability discovery and the governed invocation broker. memoryguard_capabilities provides paginated metadata for registered MCP operations and reviewed headless GUI operations; exact advanced MCP names remain callable for compatibility.

• Compact discovery with a complete catalog: New MCP clients receive 11

UTF-8 bytes across the complete MCP envelope. Eligible oversized reads return a short-lived process-local reference rather than truncating data; reads that cannot be safely replayed or exceed the snapshot limit return a bounded narrowing hint. Pages support UTF-8 offsets and field selection. Private references revalidate the original read under the current trusted session and binding before each page. Writes and context bootstrap keep their complete receipt/mandatory-rule contracts and cannot request response paging.

• Bounded read delivery: Replayable successful reads are capped at 24,000

input counts are kept separately with complete/partial/unavailable coverage. A measured zero remains zero; missing provider data remains unknown. The deterministic unit estimate is labeled as an estimate and does not claim a measured token reduction.

• Cache-aware local telemetry: Provider-reported cache-read and cache-write

and a non-empty idempotency key, which are forwarded to the target's existing permission, scope, and readiness checks. The MCP name remains io.github.irisxc4/memoryguard.

• Governed invocation: Mutating broker targets still require confirmation

See the v0.7.12 release note and release history.

Shortened. The full README is on GitHub.