Ext Ops Panel
Open dashboard
Comparison

Rekal Memory vs io.github.krimto-labs/krimto

Rekal Memory is a plugin bundle for AI coding tools published by Rekal. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.krimto-labs/krimto is an MCP server published by krimto-labs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceRekal Memoryio.github.krimto-labs/krimto
Community marketplace rekal-dev/rekal-cli Listed
Version: 0.3.5
Forks (GitHub): 3
Stars (GitHub): 206
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.47
Downloads/month (npm): 143
Downloads/week (npm): 24
Forks (GitHub): 0
Stars (GitHub): 7
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Rekal Memory vs io.github.krimto-labs/krimto
FactRekal Memoryio.github.krimto-labs/krimto
Marketplaces that list it11
Stars (GitHub) (differs)206 (better)7 (worse)
Forks (GitHub) (differs)3 (better)0 (worse)
Last release (differs)2026-11-06Not published
Where it runs (differs)Installs as a plugin bundleOn your machine (@krimto-labs/krimto)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/rekal-dev/rekal-cligithub.com/krimto-labs/krimto
Changes in the last 7 days (differs)30
First seen (differs)2026-11-032026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Rekal Memory

In its own words, on Community GitHub marketplaces:

Memory for your coding agent. Rekal saves every AI session transcript raw and append-only — no summaries to rot — then recalls the reasoning behind any change: why an approach was chosen, what was tried, what was rejected. Agent agnostic: Claude Code, Cursor, Codex, Gemini, Copilot, Kiro and OpenCode sessions all land in one ledger. Retrieval reasons at query time over the real record, with keyword and semantic search running locally — embedding is local, so there is no server, no account, no external memory service. Git is the transport: memory travels with your repo on push and reaches your team when work merges. Persistent cross-session context that maintains itself.

io.github.krimto-labs/krimto

In its own words, on Official MCP Registry:

Memory for AI coding agents — markdown in your own git, not a vendor database. Apache-2.0.

How to run each

Rekal Memory As a Claude Code plugin

Claude Code
/plugin marketplace add rekal-dev/rekal-cli
/plugin install rekal@rekal-dev

io.github.krimto-labs/krimto As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio krimto -- npx -y @krimto-labs/krimto

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Rekal Memory · What it can do: io.github.krimto-labs/krimto · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built