MemoryGuard MCP server

MemoryGuard

<!-- mcp-name: io.github.MerakOsiris/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.13

v0.7.13 strengthens mandatory-rule replacement and recovery, improves audience-aware identity handling, and improves conflict resolution:

mandatory package against audience matching, canonical rules, deduplication, sensitivity checks, and publication budgets. Equivalent unlocked predecessors retire in the same transaction; failed validation rolls back the complete update. See the replacement and recovery details.

• Safe mandatory-rule replacement: Replacements validate the final

split the same native audience solely by provider or runtime role. Distinct Agent identities remain separate, and project-scoped audiences retain their project boundaries. Provider repair uses the verified identity for its target provider.

• Native Agent/group audience matching: Matching and deduplication no longer

peer information, and resolution keeps peer groups intact while applying the selected changes atomically. Ambiguous conflicts remain unresolved.

• Readable, atomic conflict resolution: Conflict views preserve readable

timeout, up from 15 seconds, with failClosed: true.

• Cursor Hook protection: Cursor MemoryGuard Hooks now use a 30-second

v0.7.14 only corrects release metadata for the GitHub repository rename; it does not change runtime behavior. See the v0.7.14 release note.

See the v0.7.13 release note and release history.

Earlier release details are kept in the Changelog and GitHub release records.

Token evidence and demo

Shortened. The full README is on GitHub.