MemoryGuard

Name: MemoryGuard
Author: MerakOsiris

by MerakOsirisversion 0.7.15i★ –iRuns on your computer

Registry nameio.github.MerakOsiris/memoryguard

Install

Overview

Description from the maker (original English)

Local-first governed MCP memory backend for coding agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "memoryguard": {
      "command": "uvx",
      "args": [
        "agent-memguard",
        "-m",
        "memoryguard.mcp_server"
      ]
    }
  }
}

Run this in your terminal

claude mcp add memoryguard -- uvx agent-memguard -m memoryguard.mcp_server

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "memoryguard": {
      "command": "uvx",
      "args": [
        "agent-memguard",
        "-m",
        "memoryguard.mcp_server"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "memoryguard": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "agent-memguard",
        "-m",
        "memoryguard.mcp_server"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account MerakOsiris, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7249 servers in this category
Published to the registry more recently than 51% of the other 7249 servers in this category
Basic checks equal to or better than 100% of the other 7249 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MemoryGuard safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.7.15) reached the registry 37 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.15

Automatic CodeGraph builds: Trusted bootstrap starts a project's first build in a background process. Default and per-project switches persist; disabling automation preserves the graph. Supported file-write events trigger incremental refresh.
Clear graph navigation: Switch between a file overview and symbols, filter by file, inspect neighboring relations, and use zoom controls.
Bounded temporary storage: Ordinary graph queries read SQLite directly instead of retaining full-database copies. Validation and installation temporary files use the owning project/deployment cache and are cleaned up when the operation ends.

See the v0.7.15 release note and CodeGraph automation details. Reconnect or restart hosts after upgrading and repairing their provider integration.

Earlier governance improvements

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

Safe mandatory-rule replacement: Replacements validate the final 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.
Native Agent/group audience matching: Matching and deduplication no longer 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.
Readable, atomic conflict resolution: Conflict views preserve readable peer information, and resolution keeps peer groups intact while applying the selected changes atomically. Ambiguous conflicts remain unresolved.
Cursor Hook protection: Cursor MemoryGuard Hooks now use a 30-second timeout, up from 15 seconds, with failClosed: true.

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

Usage events distinguish measured_cached_input from measured_cache_write_input. measured_cache_coverage.cache_read and cache_write report complete, partial, or unavailable; measured zero remains 0, while missing provider data remains None/unavailable. Character-based estimates remain explicitly labelled estimated mg_deterministic_unit, never provider tokens.

Run the benchmark only against an authorized local workspace:

python scripts/benchmark_usage_telemetry.py --workspace . --window-days 7 --sync

Read the benchmark guide for measured, estimated, derived, and unsupported semantics. Use the demo recording checklist for a sanitized walkthrough. The repository's synthetic graph artwork is not a live product capture; it is not evidence of usage or savings.

Major V2 refactor in v0.6.0

v0.6.0 was a production data-plane refactor, not a storage-only upgrade:

Authoritative V2 domains: Memory, Rules, Evidence, Content, Runtime, Projection, Assets, CodeGraph, Skills, and System state are separated into explicit SQLite domains with governed boundaries.
Explicit cutover: V1_ACTIVE → V2_BUILDING → V2_READY → V2_ACTIVE is fail-closed; V2 never silently falls back to legacy stores or dual-writes after READY/ACTIVE.
Lossless migration: frozen-source preparation uses coherent SQLite online backups, validates source/target evidence, rechecks live-source drift, and preserves V1 data plus migration backups for rollback.
Native routing: MCP, CLI, GUI, and Hook surfaces are classified explicitly; the release closed the 233-surface cutover with 138 implemented routes, 95 retired routes, and zero neutral/blocker routes.
Governed intelligence: Rule lifecycle and RuleMerge, extraction/enrichment, External MCP import, provider control-plane, conversation history, Knowledge Library, and GUI governance all use the V2 evidence and decision paths.
Operational evidence: Reference Audit, per-domain SQLite health, guarded maintenance, rollback evidence, and safe unbound diagnostics are part of readiness and operations.

Why MemoryGuard

Persistent memory solves storage. It does not solve governance.

When several coding agents write into the same context, records become duplicated, stale, contradictory, over-broad, or unsafe to reuse. MemoryGuard sits between coding agents and their shared memory to keep that context usable.

Without governance	With MemoryGuard
Notes accumulate without a canonical state	Writes are classified, deduplicated, superseded, or surfaced as conflicts
A correction silently destroys the old value	Evidence and supersede chains preserve what changed and why
Tokens and credentials can remain active	Sensitive-looking content is quarantined from active memory
Every write needs manual approval	Agents write normally; people review exceptions and outcomes
Raw chat logs leak into future context	Conversation history remains a separate, explicitly read evidence archive

System architecture

%%{init: {"theme":"base","themeVariables":{"background":"#071521","fontFamily":"Arial, sans-serif","fontSize":"14px","primaryTextColor":"#EEF4F8","lineColor":"#557287","edgeLabelBackground":"#071521","clusterBkg":"#0A1A29","clusterBorder":"#27445A"},"flowchart":{"htmlLabels":true,"curve":"basis","nodeSpacing":32,"rankSpacing":48,"padding":14}}}%%

flowchart TB Hosts["CODING-AGENT HOSTS Claude Code · Codex · Cursor · TRAE "]:::host Gateway["LOCAL INTEGRATION MCP stdio · redirect rules · lifecycle hooks "]:::gateway

subgraph Core["GOVERNANCE CORE "] direction LR Identity["TRUST identity · scope "]:::core MemoryAPI["MEMORY governed I/O "]:::active Rules["RULES scope · assignment "]:::rule HistoryAPI["HISTORY search · timeline "]:::history Security["SAFETY validate · quarantine "]:::danger

Identity --> MemoryAPI Identity --> Rules Identity --> HistoryAPI MemoryAPI --> Security end

subgraph Stores["LOCAL GOVERNED STORES "] direction LR SharedDB[("V2 DOMAIN STORES Memory · Rules · Evidence · Content ")]:::store HistoryDB[("HISTORY STORE isolated conversations ")]:::historyStore AuditDB[("RECOVERY STORE versions · receipts · backups ")]:::store end

Bootstrap["BOUNDED CONTEXT BOOTSTRAP mandatory rule pack · relevant recall "]:::bootstrap Control["HUMAN CONTROL CLI · desktop governance console "]:::surface

Hosts --> Gateway --> Identity MemoryAPI --> SharedDB Rules --> SharedDB HistoryAPI --> HistoryDB Security --> AuditDB SharedDB --> Bootstrap Control --> Identity

classDef host fill:#12243A,stroke:#38D5C8,color:#EEF4F8,stroke-width:1.4px; classDef gateway fill:#0D3338,stroke:#38D5C8,color:#EEF4F8,stroke-width:2.4px; classDef core fill:#12243A,stroke:#557287,color:#EEF4F8,stroke-width:1.4px; classDef active fill:#0D383A,stroke:#38D5C8,color:#EEF4F8,stroke-width:2px; classDef rule fill:#3B2C18,stroke:#F3B562,color:#EEF4F8,stroke-width:1.8px; classDef history fill:#102F45,stroke:#73C7F5,color:#EEF4F8,stroke-width:1.8px; classDef danger fill:#3A2028,stroke:#EA6A6A,color:#EEF4F8,stroke-width:1.8px; classDef bootstrap fill:#EEF4F8,stroke:#38D5C8,color:#071521,stroke-width:2.4px; classDef store fill:#0B1624,stroke:#7F96A8,color:#EEF4F8,stroke-width:1.4px; classDef historyStore fill:#102436,stroke:#73C7F5,color:#EEF4F8,stroke-width:1.4px; classDef surface fill:#EEF4F8,stroke:#38D5C8,color:#071521,stroke-width:2px;

style Core fill:#081827,stroke:#27445A,stroke-width:1px,color:#EEF4F8 style Stores fill:#081827,stroke:#27445A,stroke-width:1px,color:#EEF4F8 linkStyle default stroke:#557287,stroke-width:1.4px;

Quick start

MCP Registry metadata

This package exposes a local stdio MCP server as io.github.MerakOsiris/memoryguard. Registry metadata is kept in server.json, and the marker above ships with the PyPI package README. Releases are published through GitHub OIDC to PyPI and the official MCP Registry. Verify the current package version and the Registry entry's active/latest state through their live public records.

1. Install

python -m pip install agent-memguard

For the desktop governance console:

python -m pip install "agent-memguard[gui]"

2. Authorize the current project

memoryguard source add .

3. Connect or repair your coding agent

Global provider configuration is rebuilt from the real binding in the canonical user data home. The command is idempotent and removes superseded MemoryGuard project-level overrides after a successful global takeover.

# Repair one provider

memoryguard provider repair claude memoryguard provider repair codex memoryguard provider repair cursor memoryguard provider repair trae

Only the beginning is shown; read the rest in the repo

MemoryGuard

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

What's New in v0.7.15

Earlier governance improvements

Token evidence and demo

Major V2 refactor in v0.6.0

Why MemoryGuard

System architecture

Quick start

MCP Registry metadata

1. Install

2. Authorize the current project

3. Connect or repair your coding agent