Krimto
Open-source team memory layer for AI coding agents. Markdown files in git, a user→team→org hierarchy, one cross-vendor MCP server. Apache-2.0.
Krimto
Open-source team memory for AI coding agents. Markdown files in git, a
user → team → orghierarchy, one cross-vendor MCP server. Apache-2.0.
Krimto gives every AI coding agent on your team one shared memory. Tell your agent "remember X" in any editor and it saves a durable, attributable fact; ask later — in a new chat, a different editor, or from a teammate's machine — and it recalls the right answer. Your personal notes override the team's; the team's override the org's.
Facts are plain markdown files in a git repo you own — readable, reviewable, and yours. No lock-in, no proprietary store.
Why Krimto
- Markdown-in-git storage. Every fact is a markdown file with frontmatter. Audit it with
git log, edit it in any editor, review it in a pull request. user → team → orghierarchy. Knowledge is scoped to a person, a team, or the whole company, and the most specific scope wins at recall time.- Cross-vendor + Apache-2.0. One MCP server works with Claude Code, Cursor, Codex, Gemini CLI, and more — fully open source, with no managed-service restriction.
Try it in 2 minutes (solo, no account)
npx @krimto-labs/krimto init
The setup wizard detects your editor, wires it up, and turns on automatic memory. Then, in any chat:
"Remember that our staging DB resets every Sunday."
Open a new chat and ask:
"What do you know about staging?" → it remembers.
See your notes with krimto notes (terminal) or krimto ui (browser dashboard). Your data lives in
~/.krimto — the same folder no matter which project you're working in.
Connect your agent
krimto init wires supported editors for you. What auto-connects vs. needs one copy-paste step:
| Editor | Setup |
|---|---|
| Cursor | auto-connects |
| Claude Code | auto-connects |
| Codex | manual snippet |
| Gemini CLI | manual snippet |
To connect any MCP client manually, point it at Krimto over stdio:
claude mcp add krimto -- npx -y @krimto-labs/krimto
…or the config-file form (Cursor, Codex, Gemini CLI, etc. use the same shape):
{ "mcpServers": { "krimto": { "command": "npx", "args": ["-y", "@krimto-labs/krimto"] } } }
By default an agent uses Krimto only when you ask. Running krimto init once in your project drops a
standing rule so it uses Krimto on its own.
Install as a Claude Code plugin
Prefer Claude Code's plugin system? Add Krimto's marketplace and install it directly:
/plugin marketplace add krimto-labs/krimto
/plugin install krimto@krimto
This bundles the MCP server together with Krimto's skills, the /krimto-status command, and the
memory hooks — no separate krimto init needed.
How it works
Three layers, one source of truth:
- Storage — facts are markdown files in a git repository (the source of truth; git is the audit log).
- Index — a SQLite + sqlite-vec hybrid index (keyword + vector) for fast retrieval, with scope precedence applied at ranking time.
- Access — an API server enforces who can read and write each scope (
user/team/org).
Team mode
When you're ready to share memory with teammates:
npx @krimto-labs/krimto team init
This walks you through an admin email, your org/team name, an optional shared git remote, and teammate invites — then prints a join command for each teammate:
krimto join --server <url> --key <key>
Teammates can connect to one shared server, or each run their own Krimto synced over a shared git
remote. Personal and team notes live together and sync as a unit. Step back to solo any time with
krimto team disband (your notes are preserved).
Self-host
Krimto runs anywhere Node 20+ runs.
# HTTP server + browser dashboard at http://localhost:8080
npx @krimto-labs/krimto serve
# or Docker
docker run -d -p 8080:8080 -v ~/.krimto:/data ghcr.io/krimto-labs/krimto:latest
Run npx @krimto-labs/krimto --help for the full command surface.
Roadmap
v0.2 (current) ships the memory core, teams, the web dashboard, and the cross-vendor MCP server. Next: OAuth sign-in and a pull-request approval flow (v0.3), then a hosted Krimto Cloud (v1.0). See ROADMAP.md.
Contributing & license
Contributions welcome — see CONTRIBUTING.md and our Code of Conduct. Security reports: SECURITY.md.
Licensed under Apache-2.0. The same code is self-hostable by a solo developer or an enterprise — no tier walls.
Related Servers
OpenMemBrain
OpenMemBrain is the intelligent membrane for AI coding memory. It autonomously reads and learns from your coding sessions — you never have to tell it what to save. It selectively absorbs project knowledge, blocks secrets, filters noise, resolves conflicts, and persists only what matters.
vault-cortex
MCP server for Obsidian vaults — plugin-free search, memory, and full vault access for any AI agent.
Obsidian MCP Server
Self-hosted MCP server for Obsidian: semantic + full-text search, wikilink graph, note CRUD, OAuth, and a self-describing vault guide.
Memanto MCP
MEMANTO is a memory agent. It remembers, recalls, and answers — so your agents can achieve long-term goals and avoid confusion.
MarsNMe
Agent-agnostic persistent memory backend. 13 MCP tools, Supabase + Jina embeddings, multi-profile isolation, semantic recall across sessions.
MemoraEu
Personal memory layer for AI assistants. Store, search and recall preferences, decisions and facts — available from any MCP-compatible client.
trilium-mcp
Read and write a self-hosted TriliumNext knowledge base over its ETAPI. Ten tools: create/get/update/append/delete notes, full search, labels and relations.
NOUZ MCP Server
Local-first MCP server that turns Obsidian and Markdown knowledge bases into an agent-readable graph
Presence
Presence: cross-session memory and a verification gate for Claude Code
mem0-mcp-server
mem0-mcp-server — exposes Mem0 persistent semantic memory as an MCP HTTP server; supports add/search/read/update/delete operations and semantic search for agent memory.