context-kit vs chat-recall
context-kit is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
context-kit is a plugin bundle for AI coding tools published by Batuhan Tunç. No marketplace we read lists it any more. chat-recall is an MCP server published by munhq. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  chat-recall | |
|---|---|---|
| Community marketplace batuhaanccs/claude-context-kit | Removed on 2026-10-15 Version: 0.2.2 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.19 Downloads/month (npm): 4 311 Downloads/week (npm): 110 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
| Fact | context-kitno longer listed · | chat-recall |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | 2 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (chatrecall.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 0 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | MIT | Elastic-2.0 |
| Repository (differs) | github.com/batuhaanccs/claude-context-kit | github.com/munhq/chat-recall |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 301 (2 days ago) |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of context-kit
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
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…
-
Persistent conversation memory for Claude Code. Semantic search across past sessions, session continuity detection, cross-project intelligence, and predictive context injection…
-
Session memory lifecycle for Claude Code. Structured handoffs between sessions, workstreams to switch context without losing it, background watcher (Haiku) that captures decisions…
-
Persistent conversation recall for Claude Code. Indexes every exchange into a local SQLite database so you can search, browse, and recover context at any time. Survives /clear…
-
100 battle-tested skills for Claude Code across 10 categories: session memory, git workflows, database migrations, security scanning, deployments, API development, frontend…
-
Switch to a fresh Claude chat without losing a single rule, correction or number. /amhandoff writes a complete handoff file, and a code word plus checkpoints warn you when it is…
What each says it does
context-kit
Cross-session memory for Claude Code projects: handoff note injected at session start, staleness warning, handoff / resume skills.
chat-recall
One searchable history across every AI coding tool, with secret scanning and a shared task board.
How to run each
context-kit
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
chat-recall As a remote MCP server
claude mcp add --transport http chat-recall https://chatrecall.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only chat-recall 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 context-kit publish no settings it asks for, so we do not compare settings.
What it can do: context-kit · What it can do: chat-recall · 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.