Krimto
Open-source team memory layer for AI coding agents. Markdown-in-git, user/team/org hierarchy, MCP. Apache-2.0.
README
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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.