AI & MemoryMCP RegistrymcpbB · 76

mwe-mcp — Memory Wiki Engine

Name: mwe-mcp — Memory Wiki Engine
Author: Fr4nZ82

io.github.Fr4nZ82 · Updated 3mo ago

Self-hosted multi-user memory for AI agents: a human-readable Markdown wiki with per-fragment ACL.

At a glance

mwe-mcp — Memory Wiki Engine is an MCP server in the AI & Memory category. It runs locally over stdio via `npx -y https://github.com/Fr4nZ82/mwe-mcp/releases/download/v1.4.0/mwe-mcp-v1.4.0-x86_64-unknown-linux-gnu.tar.gz`, and declares no required credentials. It scores B (76/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 6

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install mwe-mcp — Memory Wiki Engine in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install mwe-mcp — Memory Wiki Engine in Claude CodeAnthropic's agentic CLI

Add the server

bash

claude mcp add mwe-mcp -- npx -y https://github.com/Fr4nZ82/mwe-mcp/releases/download/v1.4.0/mwe-mcp-v1.4.0-x86_64-unknown-linux-gnu.tar.gz

2
Verify it's connected
bash
```
claude mcp list
```
Sharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.

How to install mwe-mcp — Memory Wiki Engine in Claude DesktopDesktop app (MCP config)

Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

json

{
  "mcpServers": {
    "mwe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Fr4nZ82/mwe-mcp/releases/download/v1.4.0/mwe-mcp-v1.4.0-x86_64-unknown-linux-gnu.tar.gz"
      ]
    }
  }
}

Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install mwe-mcp — Memory Wiki Engine in CursorAI-first code editor

Create / edit .cursor/mcp.json in your project

json

{
  "mcpServers": {
    "mwe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Fr4nZ82/mwe-mcp/releases/download/v1.4.0/mwe-mcp-v1.4.0-x86_64-unknown-linux-gnu.tar.gz"
      ]
    }
  }
}

Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

How to install mwe-mcp — Memory Wiki Engine in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

[mcp_servers.mwe-mcp]
command = "npx"
args = ["-y", "https://github.com/Fr4nZ82/mwe-mcp/releases/download/v1.4.0/mwe-mcp-v1.4.0-x86_64-unknown-linux-gnu.tar.gz"]

Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

How to install mwe-mcp — Memory Wiki Engine in WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

{
  "mcpServers": {
    "mwe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Fr4nZ82/mwe-mcp/releases/download/v1.4.0/mwe-mcp-v1.4.0-x86_64-unknown-linux-gnu.tar.gz"
      ]
    }
  }
}

Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

How to install mwe-mcp — Memory Wiki Engine in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

{
  "mcpServers": {
    "mwe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Fr4nZ82/mwe-mcp/releases/download/v1.4.0/mwe-mcp-v1.4.0-x86_64-unknown-linux-gnu.tar.gz"
      ]
    }
  }
}

How to install mwe-mcp — Memory Wiki Engine in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

{
  "servers": {
    "mwe-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Fr4nZ82/mwe-mcp/releases/download/v1.4.0/mwe-mcp-v1.4.0-x86_64-unknown-linux-gnu.tar.gz"
      ]
    }
  }
}

Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

What tools does mwe-mcp — Memory Wiki Engine expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

The published package could not be downloaded or read for analysis.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
Downloads at launch — The package is fetched from its registry each run unless you pin a version.

Last commit 1 month ago — Actively maintained.
6 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 76

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%99%
Last commit 39 days ago.
Adoption20%26%
6 stars.
Transparency20%75%
3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.
Provenance15%75%
Links to its own repository; package linkage unverified.
Packaging15%100%
Publishes a pinned version (1.4.0).

Documentation

Full README

mwe-mcp — the Memory Wiki Engine

Every AI agent you use, remembering into one shared Markdown wiki. Every fact in it governed individually: who it's about, who said it, who may read it, and when it stops being true.

[▸ Open the public demo · demo.contea.casa](https://demo.contea.casa)

One household's shared memory: three people, three assistants, 203 turns of conversation from 2 March to 18 July 2026, rebuilt by the engine and then frozen. Enter as Bob, Alice or Zoe with one click, on any page, and see what each of them may read. It is read-only: nothing you do changes it, nothing you click calls a model, and no agent can be attached to it. The guided tour walks eight pages of it.

Why · The demo · The tour · The idea, in one page · Quickstart · Where it fits · How it works · Docs

Why this exists

Ask most agent frameworks where their memory lives and the honest answer is *"in a vector index somewhere."* That works until you want to do something human with it: open it, fix a wrong fact, understand why the agent believes what it believes. Or the hard one, let more than one person share a memory without everyone seeing everything.

A blob of embeddings has no answer to *who is this fact about, who told us, who's allowed to read it, and is it still true?*

mwe-mcp answers all four. The memory is a folder of Markdown pages you can open and read. Underneath, every fact on those pages is indexed and governed one by one, and the rules are enforced by the engine in code, not by asking a model nicely.

Same page, two readers, two answers

A family runs one shared memory. Every assistant they talk to writes into it and recalls from it: the voice assistant in the kitchen, a bot on Telegram, Claude Code on a laptop. Alice and Bob are on the team. Zoe is family, but not on the team.

Alice: *"Bob changed jobs, he's at AcmeCorp now."* Assistant: *"Noted in Bob's profile."*

The engine resolves "Bob", decides the fact is *about* Bob so it lands on his page, keeps Alice as the one who reported it, and scopes it to group:team. Later, two different people ask:

Excerpt — the full document is on GitHub.

Alternatives to mwe-mcp — Memory Wiki Engine

Maintain mwe-mcp — Memory Wiki Engine? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![mwe-mcp — Memory Wiki Engine on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-fr4nz82-mwe-mcp)](https://mcp-skills-hub.vercel.app/mcps/io-github-fr4nz82-mwe-mcp)

Catalog data refreshed Oct 28, 2026. Something wrong? Report it.