Ext Ops Panel
Open dashboard
Comparison

coremem vs io.github.Sisuthros/claude-amplifier

coremem is a plugin bundle for AI coding tools published by corememapp. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.Sisuthros/claude-amplifier is an MCP server published by Sisuthros. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplacecorememio.github.Sisuthros/claude-amplifier
Claude Code: claude-plugins-community Listed
Version: 8a0074f
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.5.3
Downloads/month (npm): 228
Downloads/week (npm): 46
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

coremem vs io.github.Sisuthros/claude-amplifier
Factcorememio.github.Sisuthros/claude-amplifier
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (claude-amplifier)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/corememapp/claude-plugingithub.com/sisuthros/claude-amplifier
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

coremem

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

CoreMem gives Claude persistent memory across every session. Your preferences, project context, and working style live in mems — structured notes you write and control. Claude can search and load relevant mems automatically as you work, and propose updates when it learns something new.

io.github.Sisuthros/claude-amplifier

In its own words, on Official MCP Registry:

Persistent memory + decision tracking for Claude across sessions. Local SQLite, no cloud.

How to run each

coremem As a Claude Code plugin

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

io.github.Sisuthros/claude-amplifier As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio claude-amplifier -- npx -y claude-amplifier

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: coremem · What it can do: io.github.Sisuthros/claude-amplifier · 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