Mnema
Self-hostable shared brain for you and your AI agents — docs, flows, meetings, decisions, rationale
- Transport
- Not stated
- Package
- —
- Registry id
- in.theboringpeople/mnema
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
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.
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:
- Open http://localhost:4321 and create an account at
/auth/local(email + password). - Connect an MCP client to your server:
http://localhost:8080/mcp(in Claude/Cursor, add it as a custom MCP/connector URL; you'll be sent back here to log in and approve).
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 VOYAGE_API_KEY (semantic search) and GEMINI_API_KEY (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:
| Capability | Core (this repo) | Licensed |
|---|---|---|
| Docs, real-time editor, folders, search | ✅ | ✅ |
| Flows (build + walk step-by-step via MCP) | ✅ | ✅ |
| MCP server (read + propose/commit writes) | ✅ | ✅ |
| Built-in email+password auth, or generic OIDC | ✅ | ✅ |
| Self-host, single-workspace, unlimited docs | ✅ | ✅ |
| Version history + document export | ✅ free with a community license | ✅ |
| Knowledge graph (build, report, traverse) | ❌ | ✅ |
| Meeting intelligence (bot, transcription, summaries) | ❌ | ✅ |
| Org / IAM / SSO, audit logs, multi-workspace | ❌ | ✅ |
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
From the project's README.