Ext Ops Panel
Open dashboard
Comparison

session-normalizer vs memory-boost

session-normalizer is a plugin bundle for AI coding tools published by mutale. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). memory-boost is an MCP server published by arnaugonzalez. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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-normalizermemory-boost
Claude Code: claude-plugins-community Listed
Version: 3.2.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 (PyPI): 276
Downloads/week (PyPI): 34
Forks (GitHub): 0
Stars (GitHub): 0
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-normalizer vs memory-boost
Factsession-normalizermemory-boost
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (memory-boost)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)51
Parts of the bundle (differs)96
Licence (differs)Not statedMIT
Repository (differs)github.com/mutale/session-normalizergithub.com/arnaugonzalez/memory-boost
Changes in the last 7 days (differs)02
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-normalizer

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

Auto-cleanup junk sessions on startup, show project-relevant sessions as context, and merge old sessions into project docs. Sessions carry accumulated knowledge about your project — decisions made, bugs fixed, architecture chosen. This plugin consolidates that knowledge so it's never lost when sessions pile up, and surfaces the right session when you return to a project.

memory-boost

In its own words, on Official MCP Registry:

Markdown memory for coding agents that audits itself: drift reports and session digests.

How to run each

session-normalizer As a Claude Code plugin

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

memory-boost As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio memory-boost -- uvx memory-boost serve

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-normalizer · What it can do: memory-boost · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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