context-bench vs Code Context Engine
context-bench is a plugin bundle for AI coding tools published by nessos666. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Code Context Engine is an MCP server published by ai-elara. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |  context-bench |  Code Context Engine |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.13 Downloads/month (PyPI): 728 Downloads/week (PyPI): 170 Forks (GitHub): 66 Stars (GitHub): 430 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-bench | Code Context Engine |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (worse) | 430 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 66 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (code-context-engine) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/nessos666/context-bench | github.com/elara-labs/code-context-engine |
| Changes in the last 7 days | 0 | 0 |
| 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
context-bench
Plugin description: Self-learning Claude Code plugin that automatically detects what project you're working on and injects the right file context into every session. No manual configuration needed — it learns from your usage patterns, builds confidence scores, and removes stale topics automatically. Uses three hooks: UserPromptSubmit (match & inject), PostToolUse (track changes), SessionEnd (learn & decay). Zero dependencies, Python 3.9+ stdlib only.
Code Context Engine
Index your codebase. AI searches instead of re-reading files. 94% token savings.
How to run each
context-bench As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install context-bench@claude-communityCode Context Engine As a local MCP server: PyPI package
claude mcp add --transport stdio code-context-engine -- uvx code-context-engineCommands 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-bench · What it can do: Code Context Engine · 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.