Mnema — Shared Brain for You and Your AI Agents MCP server

Mnema

Your AI assistant answers from its training data, not your team's. Mnema is a self-hostable knowledge workspace that publishes your docs, decisions, and step-by-step workflows to any MCP-aware AI client (Claude, ChatGPT, Cursor, Windsurf, Cline) over the Model Context Protocol — so your agents read your context, live, with no uploads or copy-paste.

This is the open-core repository (fair-code, Mnema Community License). It is the full core product and runs on its own; the enterprise modules are separate.

<!-- ASSET: hero screenshot (editor + connected Claude) --> <!-- ASSET: 30s demo GIF (ask Claude → it reads a doc → proposes an edit → Approve) -->

Quickstart (self-host in a few minutes)

Clone to a live MCP endpoint in about 4 minutes — a one-time image build. (A stone-cold first-ever build can take longer; it's I/O-bound on Docker's filesystem, not downloads. Native Linux is as fast or faster.)

Requirements: Docker + Docker Compose. (Working on the code itself, outside Docker? Node 22 — nvm use picks it up from .nvmrc — and pnpm 10; see CONTRIBUTING.md.)

git clone https://github.com/nbkdoesntknowcoding/mnema.git
cd mnema
./scripts/self-host-init.sh          # generates secrets + the OAuth keypair, writes .env
docker compose up -d --build         # postgres, redis, api, collab, workers, web

Then:

(in Claude/Cursor, add it as a custom MCP/connector URL; you'll be sent back here to log in and approve).

• Open http://localhost:4321 and create an account at /auth/local (email + password).
• Connect an MCP client to your server: http://localhost:8080/mcp

That's it — the first workspace comes with a welcome doc and an example flow, so your first connection has something real to read.

Optional: set VOYAGEAPIKEY (semantic search) and GEMINIAPIKEY (autocomplete) in .env — bring your own keys. Both stay disabled until set.

Documentation

• Connect an AI client — Claude, ChatGPT, Cursor, Windsurf, Antigravity
• Embed Mnema in your own app — REST API + an API key
• REST API reference — every public endpoint, auth, scopes, examples

What's in the core (this repo) vs. licensed

The free layer carries the full product; the gates sit on what organizations and R&D need. Plainly:

The knowledge graph, meeting intelligence, org/IAM+SSO, audit, and multi-workspace mode are commercial add-ons — the core runs perfectly without them, and its CI proves it builds and boots with the enterprise modules entirely absent. Licensing: LICENSE for the core; enterprise inquiries via the website.

Docs, flows, collaboration, and live MCP are free forever, registered or not.

Version history and export are also free — we just ask for your email (a free

community license, entered in Settings). Your history is recorded from day

one; registering reveals it.

Self-host notes

Shortened. The full README is on GitHub.