Ext Ops Panel
Open dashboard
Comparison

agent-recall vs io.github.gitmem-dev/gitmem

agent-recall is a plugin bundle for AI coding tools published by mnardit. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.gitmem-dev/gitmem is an MCP server published by gitmem-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
Marketplaceagent-recallio.github.gitmem-dev/gitmem
Claude Code: claude-plugins-community Listed
Version: 0.4.0
Forks (GitHub): 1
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.1
Forks (GitHub): 1
Stars (GitHub): 9
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

agent-recall vs io.github.gitmem-dev/gitmem
Factagent-recallio.github.gitmem-dev/gitmem
Marketplaces that list it11
Stars (GitHub) (differs)14 (better)9 (worse)
Forks (GitHub)11
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (gitmem-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Hooks it runs (differs)2Not published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/mnardit/agent-recallgithub.com/gitmem-dev/gitmem
Changes in the last 7 days00
First seen2026-10-112026-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

agent-recall

In its own words, on Claude Code: claude-plugins-community:

Persistent memory for AI coding agents. SQLite knowledge graph with scoped entities, MCP tools, and LLM-summarized briefings.

io.github.gitmem-dev/gitmem

In its own words, on Official MCP Registry:

Persistent institutional memory for AI coding agents. Memory that compounds.

How to run each

agent-recall

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.gitmem-dev/gitmem As a local MCP server: npm package

Claude Code
claude mcp add --env "SUPABASE_SERVICE_ROLE_KEY=<YOUR_SUPABASE_SERVICE_ROLE_KEY>" --transport stdio gitmem -- npx -y gitmem-mcp

Requires: SUPABASE_SERVICE_ROLE_KEY (secret)

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

The marketplaces of agent-recall publish no settings it asks for, so we do not compare settings.

What it can do: agent-recall · What it can do: io.github.gitmem-dev/gitmem · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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