Ext Ops Panel
Open dashboard
Comparison

keepgoing vs CCRider

keepgoing is a plugin bundle for AI coding tools published by keepgoing-dev. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). CCRider is an MCP server published by neilberkman. 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
MarketplacekeepgoingCCRider
Claude Code: claude-plugins-community Listed
Version: 0.6.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.13.0
Forks (GitHub): 8
Stars (GitHub): 134
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

keepgoing vs CCRider
FactkeepgoingCCRider
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)134 (better)
Forks (GitHub) (differs)0 (worse)8 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@keepgoingdev/mcp-server)On your machine (https://github.com/neilberkman/ccrider/releases/download/v1.13.0/ccrider_1.13.0.mcpb)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)5Not published
Parts of the bundle (differs)11Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/keepgoing-dev/claude-plugingithub.com/neilberkman/ccrider
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

keepgoing

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

Session memory for Claude Code automatically saves checkpoints during work, shows what you were doing upon return, and tracks progress across sessions. It includes 7 slash commands for resuming context, saving checkpoints, viewing progress, and exporting context to other AI tools. It also configures session hooks and an MCP server with 12 tools for comprehensive session awareness.

CCRider

In its own words, on Official MCP Registry:

Full-text search, browse, and resume across your coding agent sessions (Claude Code, Codex, Amp)

How to run each

keepgoing

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

CCRider

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

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: keepgoing · What it can do: CCRider · 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