keepgoing vs KLYPIX Shared Project Memory
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). KLYPIX Shared Project Memory is an MCP server published by dahshanlabs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-27. 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
| Marketplace |  keepgoing |  KLYPIX Shared Project Memory |
|---|---|---|
| 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.108.1 Downloads/month (npm): 4 387 Downloads/week (npm): 875 Forks (GitHub): 5 Stars (GitHub): 10 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.108.1 Downloads/month (npm): 4 387 Downloads/week (npm): 875 Forks (GitHub): 5 Stars (GitHub): 10 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
| Fact | keepgoing | KLYPIX Shared Project Memory |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 10 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 5 (better) |
| Last release (differs) | Not published | 2026-10-25 |
| Where it runs (differs) | On your machine (@keepgoingdev/mcp-server) | On your machine (klypix-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Hooks it runs (differs) | 5 | Not published |
| Parts of the bundle (differs) | 11 | Not a bundle |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/keepgoing-dev/claude-plugin | github.com/dahshanlabs/klypix-mcp |
| Changes in the last 7 days (differs) | 0 | 15 |
| First seen | 2026-10-11 | 2026-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
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.
KLYPIX Shared Project Memory
Shared project memory for Claude Code, Codex and Cursor: decisions, corrections, overlap warnings.
How to run each
keepgoing As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install keepgoing@claude-communityKLYPIX Shared Project Memory As a local MCP server: npm package
claude mcp add --transport stdio klypix-mcp -- npx -y klypix-mcpCommands 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
The marketplaces of keepgoing publish no settings it asks for, so we do not compare settings.
What it can do: keepgoing · What it can do: KLYPIX Shared Project Memory · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.