Memory Guard MCP Server

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

People who work with agent memory, ai governance and codex and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in Python.

VERIFIED ACTIVE

LAST COMMIT 2026-09-28 · ★ 3 · #61 OF 250 MAINTAINED CODING AGENT · VERIFIED 2026-09-30

MIT · Python servers · how we verify → /methodology

01 · Install Memory Guard

before you install - you'll need

The README does not document required environment variables for a basic install.

Claude Code

claude mcp add irisxc4-memoryguard -- uvx agent-memguard

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "irisxc4-memoryguard": {
      "command": "uvx",
      "args": [
        "agent-memguard"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

pypi package agent-memguard - check the name against the project README before installing (PyPI has no namespace ownership)

registry namespace io.github.irisxc4 is GitHub-verified and matches the repo owner

03 · What Memory Guard can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v0.7.14 · 2026-09-28

MemoryGuard v0.7.14 · This release corrects distribution metadata after the GitHub repository rename: · the MCP server namespace is now io.github.MerakOsiris/memoryguard, and the · registry manifest points to · No…

v0.7.13 · 2026-09-28

MemoryGuard v0.7.13 · Mandatory-rule replacement and publication budgets · Mandatory-rule updates validate the final rule package with the same audience · matching, canonical-head selection, deduplication, sensitivity…

v0.7.12 · 2026-09-12

MemoryGuard v0.7.12 · MCP discovery and registered capabilities · New MCP clients receive a compact default discovery surface of 11 day-to-day · tools through tools/list. The surface includes capability discovery and…

04 · Who maintains Memory Guard

MemoryGuard is maintained by irisxc4. It's the only MCP server we track from this author; the repo dates to Jul 2026.

05 · Facts

category
coding agent - ranked #61 of 250 actively-maintained coding agent servers as of 2026-09-30.
release cadence
10+ releases in the last 90 days (latest 2026-09-28)
registry
io.github.irisxc4/memoryguard (active, first published 2026-09-04 · 4 versions)
packages
pypi:agent-memguard

06 · Memory Guard FAQ

What is Memory Guard?

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

Is Memory Guard still maintained?

Yes - as of 2026-09-30, its last commit was 2026-09-28 and it shipped 10+ releases in the last 90 days. We re-verify nightly.

How do I install Memory Guard?

Run `uvx agent-memguard`. The README does not document required environment variables for a basic install. You can also paste the ready-made client config above.

Does Memory Guard run locally?

Yes - it's a stdio server: it runs on your machine (via uvx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Memory Guard