Ext Ops Panel
Open dashboard
Comparison

better-compact vs io.github.sumanaddanki/suma-memory

better-compact is a plugin bundle for AI coding tools published by AshishKumar4. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.sumanaddanki/suma-memory is an MCP server published by sumanaddanki. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacebetter-compactio.github.sumanaddanki/suma-memory
Community marketplace ashishkumar4/better-compact Listed
Version: 0.2.0
Forks (GitHub): 2
Stars (GitHub): 16
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.5.0
Downloads/month (npm): 188
Downloads/week (npm): 27
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

better-compact vs io.github.sumanaddanki/suma-memory
Factbetter-compactio.github.sumanaddanki/suma-memory
Marketplaces that list it11
Stars (GitHub) (differs)16 (better)0 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (sumapro.quadframe.work/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/ashishkumar4/better-compactgithub.com/sumanaddanki/suma-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (28 h ago)

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

better-compact

In its own words, on Community GitHub marketplaces:

Context pruning for Claude Code through the better-compact daemon: keeps long sessions lean without losing recallable history.

io.github.sumanaddanki/suma-memory

In its own words, on Official MCP Registry:

Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.

How to run each

better-compact As a Claude Code plugin

Claude Code
/plugin marketplace add ashishkumar4/better-compact
/plugin install better-compact@better-compact

io.github.sumanaddanki/suma-memory As a remote MCP server

Claude Code
claude mcp add --transport http suma-memory https://sumapro.quadframe.work/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: SUMA_API_KEY (secret), Authorization header

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

Only io.github.sumanaddanki/suma-memory has a remote endpoint we check. How we check endpoints

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 better-compact publish no settings it asks for, so we do not compare settings.

What it can do: better-compact · What it can do: io.github.sumanaddanki/suma-memory · 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