Krimto

MCPAI代理

提供方 krimto-labs · 包名 @krimto-labs/krimto

AI代理 stdio · 本地进程 OAuth 授权 社区 / 第三方 ClaudeCursorGemini CLICodex
查看接入方式

Open-source memory for AI coding agents. Tell your agent to "remember" something in Cursor, Claude Code, Codex, or Gemini CLI, and Krimto saves it as a plain markdown file in a git repo you own — not rows in a vendor's database. Recall it later in a new chat, a different editor,

一句话选型结论

按资料字段整理

Krimto 属于AI代理类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Claude、Cursor、Gemini CLI 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

memoryai agentsmcp

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
npx -y @krimto-labs/krimto

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Cross-platform,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、Gemini CLI,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Krimto当前 未标注 stdio · 本地进程 本地部署 有 未标注
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方krimto-labs上游标注的维护方 krimto-labs
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时@krimto-labs/krimto · Cross-platform本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

5.8 KB
来自项目仓库与上游目录的原文,未做删改

Krimto

> Open-source memory for AI coding agents you own in git — governed by a real user→team→org hierarchy, not a vendor database. Solo to team. Apache-2.0.

Your agent's memory, as markdown in your own git — synced across every editor and machine. 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 on another machine — and it recalls the right answer. One command, no account,
no vendor database: your memory follows you.

You own it: every fact is a plain markdown file in a git repo you control — readable, reviewable in a
PR, and yours. When a teammate joins, that same memory becomes a shared team brain governed by a real
user → team → org hierarchy (the most specific scope wins at recall) — the one primitive no other
memory tool ships. Solo is free; the governance is what you grow into.

See it

One npx command sets it up; then your agent saves a fact in Claude Code and recalls it in Cursor —
no account, no database:

Three short demos — solo (remember in Claude Code, recall in Cursor), cross-machine (write,
git push, recall on another laptop), and team (a teammate's fact reaches you; your personal notes
stay yours).

Because every memory is just a file in your git, you can read it yourself — no API, no dashboard needed:```console
$ cat ~/.krimto/user/you@example.com/favorite-color.md


id: fct_01KT3BDSYY1KK80SG3S7KBEV58
scope: user/you@example.com
title: Favorite color
author: you@example.com
created: 2026-06-02T05:03:14Z
updated: 2026-06-02T05:03:14Z
tags:
- personal
source: claude-code


User's favorite color is red.

$ git -C ~/.krimto log --oneline -1
8bc5b86 krimto: write batch — 1 fact


That's the whole bet: **your agent's memory is plain markdown in a git repo you own — not rows in
someone else's database.**

## Why Krimto

- **You own it, in your git.** Every fact is a markdown file in a git repo you control — `git log` the
  audit trail, edit it in any editor, review it in a pull request. No vendor database, no lock-in.
- **Governed `user → team → org` hierarchy.** Knowledge is scoped to a person, a team, or the whole
  company, and the most specific scope wins at recall — a server-enforced primitive no other memory
  tool ships for free.
- **Follows you everywhere — cross-vendor, Apache-2.0.** One MCP server syncs the same memory across
  Claude Code, Cursor, Codex, Gemini CLI and more — every editor and machine. Fully open source, with
  no managed-service restriction.

## Try it in 2 minutes (solo, no account)```bash
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:```bash
claude mcp add krimto -- npx -y @krimto-labs/krimto


…or the config-file form (Cursor, Codex, Gemini CLI, etc. use the same shape):```json
{ "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:```bash
/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:

1. **Storage** — facts are markdown files in a git repository (the source of truth; git is the audit log).
2. **Index** — a SQLite + sqlite-vec hybrid index (keyword + vector) for fast retrieval, with scope
   precedence applied at ranking time.
3. **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:```bash
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:```bash
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.```bash
# 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.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Krimto 怎么安装?

在客户端按下面的安装命令接入:npx -y @krimto-labs/krimto。对应的包名是 @krimto-labs/krimto。装完在客户端配置里引用同一个包或端点。

Krimto 怎么在 Claude、Cursor、Gemini CLI 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Krimto 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Krimto 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Krimto 支持哪些客户端?

资料标注支持 Claude、Cursor、Gemini CLI、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Krimto 能提供哪些能力?

资料显示能力标签包括 memory、ai agents、mcp、markdown、git、open source。具体工具清单以官方文档为准。

Krimto 需要什么运行环境?

运行时为 Cross-platform;属于本地进程,需要在本机装好运行环境。

Krimto 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。