Ext Ops Panel
Open dashboard
Comparison

session-recharge vs Mneme Memory

session-recharge is a plugin bundle for AI coding tools published by edo-ceder. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Mneme Memory is an MCP server published by modusensus. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplacesession-rechargeMneme Memory
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (npm): 717
Downloads/week (npm): 267
Forks (GitHub): 21
Stars (GitHub): 148
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

session-recharge vs Mneme Memory
Factsession-rechargeMneme Memory
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)148 (better)
Forks (GitHub) (differs)0 (worse)21 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mneme-memory)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/edo-ceder/session-rechargegithub.com/slow-stack/mneme
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

session-recharge

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

Preserves important architectural decisions and user requests that get lost during compaction and long sessions. Automatically extracts structured session memory (goals, decisions, state, blockers, corrections) before compaction and re-injects it after. Can also be triggered mid-session anytime you want Claude to refocus on what's been decided.

Mneme Memory

In its own words, on Official MCP Registry:

Cross-session memory for AI coding agents via six tools; local-first SQLite store.

How to run each

session-recharge As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install session-recharge@claude-community

Mneme Memory As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mneme-memory -- npx -y mneme-memory

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: session-recharge · What it can do: Mneme Memory · 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