mwe-mcp — Memory Wiki Engine runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 19 Sep 2026.
Self-hosted multi-user memory for AI agents: a human-readable Markdown wiki with per-fragment ACL.
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
proc = subprocess.run(cmd, shell=True, cwd=bridge_dir, env=env)
proc = subprocess.run(cmd, shell=True, cwd=bridge_dir, env=env)
exec: (cmd: string) => execSync(cmd, { cwd: FORK, encoding: 'utf-8', stdio: ['ignore', 'pipe', 'pipe'] }),
const inputs = inputsFromEnv(fs.readFileSync(path.join(FORK, skillDir, 'SKILL.md'), 'utf-8'));
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Self-hosted Obsidian-compatible markdown vault with a web UI and a 71-tool MCP server for AI agents
Self-hosted agent memory as a markdown vault: semantic and keyword search, wikilink graph, OAuth
Local persistent memory and Markdown wiki for AI coding agents: 24 MCP tools, no gateway required.
Two-layer memory MCP server for AI agents with 37 tools, RAG, graphs, wiki, auth
Self-hosted remote MCP server for Docmost CE: members read and edit the wiki as themselves
Hosted markdown project wikis your team's AI assistants read, search, and update over MCP.
Local Markdown/Obsidian knowledge substrate for MCP agents with governed memory and hybrid search.
Self-hostable team wiki; agents read & write it via MCP; Atlas turns your repo into a cited wiki.
Answers built from our own checks of this server.