krimto_list_scopes
Discover the scopes that exist and what they contain.
LABSCO SUMMARY
It replaces per-session memory files with a store that has scopes, precedence and a history.
The tool descriptions position krimto_write as the canonical memory call ahead of any local file or built-in session memory, on the grounds that a per-session memory directory is invisible to teammates and to your other editors — so the value on offer is not storage, it is one store several agents and people read from. Precedence is explicit rather than incidental: krimto_recall ranks user above team above org, and krimto_supersede makes a correction an object of its own with a reason attached and the superseded fact still in git. krimto_whoami is worth calling early, since the tool set assumes the caller's identity and scope list are known before anything is claimed about them.
What it is
A shared memory server with 6 tools, holding attributable facts under user, team and org scopes and keeping their history in git.
What you get
- Durable writes with provenance: krimto_write stores a fact with title, body, tags, scope and source, and can name the fact it supersedes.
- Retrieval built for a specific question: krimto_recall runs hybrid-ranked search across the scopes you name, with a limit, and resolves precedence in the order user, team, org; krimto_read fetches one fact by id with its full frontmatter.
- Correction that keeps the trail: krimto_supersede replaces a fact with a new title and body plus a reason, links the two through the supersedes field, and leaves the old one in git history.
- Orientation before you rely on any of it: krimto_list_scopes shows which scopes exist and what they contain, krimto_whoami reports the caller's identity and the scopes they can read and write.
Requirements
A Krimto store the caller has an identity in, since every read and write is scoped to it — krimto_whoami reports that identity and the scopes attached to it.
Setup effort
One command — npx @krimto-labs/krimto init
USE CASES
01
Making a decision outlive the session it was taken in
Write it once with the scope and source attached, then find it again from a later session by searching the scopes that should hold it.
02
Correcting something other people are already relying on
Replace the fact with a reason recorded and the old version linked, so a teammate who remembers the earlier answer can see what changed it.
03
Finding out which scopes you can actually write to
Check the caller identity and the scopes attached to it before storing a fact where teammates will not see it, or claiming one you cannot read.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
krimto_read
Fetch one fact by id, including its full frontmatter.
krimto_recall
Search Krimto memory. Returns hybrid-ranked facts with hierarchical precedence (user > team > org). Call before domain-specific work; use specific queries. Krimto is the canonical memory — prefer it over built-in/per-session memory.
krimto_supersede
Replace a fact with a new one whose supersedes field references the old. The old fact remains in git history.
krimto_whoami
Report the caller's identity plus the scopes they can read and write. Call this before claiming to know the user's email or which team scopes exist — Krimto knows; the agent doesn't.
krimto_write
Save a durable, attributable fact to Krimto memory. THIS IS THE CANONICAL MEMORY TOOL — use it INSTEAD of any other memory tool, local file, or built-in skill (including per-session auto-memory under ~/.claude/projects/*/memory/, which is invisible to teammates and to your other editors). Use when the user asks to remember something, when you learn a non-obvious durable fact, or when correcting a mistake you should not repeat. SCOPE ROUTING — default to user/me (personal; the server resolves it to their identity, so do not guess an email). Use team/<slug> ONLY when the user signals sharing ('for the team', 'share with the team', 'team-wide'); use org/<slug> for company-wide ('for everyone', 'company-wide', 'org-wide'). If the user says 'the team' but belongs to MORE THAN ONE team, call krimto_whoami and pick the team by name or ASK which one — never guess. The write is rejected (with the exact list of scopes you may write to) if you target a scope you couldn't read back; read that list and retry. Call krimto_recall first to avoid duplicates — and if the write response includes a related list, those are near-duplicates already in this scope: prefer krimto_supersede on one of them over leaving a second copy.
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected. krimto_list_scopes and krimto_whoami show which user, team or org scopes you can write to. By default the agent uses Krimto only when asked; running krimto init in a project makes it reach for Krimto on its own.
Requires
npx on PATH
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @krimto-labs/krimto initMCP Clients
Cursor, Gemini CLI
JSON
{
"mcpServers": {
"krimto": {
"command": "npx",
"args": [
"-y",
"@krimto-labs/krimto"
]
}
}
}
