Ext Ops Panel
Open dashboard
Comparison

context-checkpoint vs io.github.NyxToolsDev/claude-memory-manager

context-checkpoint is a plugin bundle for AI coding tools published by adeotek. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.NyxToolsDev/claude-memory-manager is an MCP server published by NyxToolsDev. 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
Marketplacecontext-checkpointio.github.NyxToolsDev/claude-memory-manager
Claude Code: claude-plugins-community Listed
Version: 54dfb69
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (PyPI): 89
Downloads/week (PyPI): 27
Forks (GitHub): 0
Stars (GitHub): 2
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

context-checkpoint vs io.github.NyxToolsDev/claude-memory-manager
Factcontext-checkpointio.github.NyxToolsDev/claude-memory-manager
Marketplaces that list it11
Stars (GitHub)22
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (claude-memory-manager)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/adeotek/claude-codegithub.com/nyxtoolsdev/claude-memory-manager
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

context-checkpoint

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

Save and restore named session checkpoints so you can pick up exactly where you left off across Claude Code sessions.

io.github.NyxToolsDev/claude-memory-manager

In its own words, on Official MCP Registry:

Cross-session memory for Claude Code — context capture, semantic search, recall

How to run each

context-checkpoint As a Claude Code plugin

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

io.github.NyxToolsDev/claude-memory-manager As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio claude-memory-manager -- uvx claude-memory-manager

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: context-checkpoint · What it can do: io.github.NyxToolsDev/claude-memory-manager · 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