Ext Ops Panel
Open dashboard
Comparison

JetBrains vs context-bench

JetBrains is an MCP server published by GannaChernyshova. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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). 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

Where each is published
MarketplaceJetBrainscontext-bench
Docker MCP Catalog Listed
Version: sha256:a662cac15c5d
Forks (GitHub): 7
Pulls (Docker Hub): 59 064
Stars (Docker Hub): 2
Stars (GitHub): 9
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
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

JetBrains vs context-bench
FactJetBrainscontext-bench
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)2 (worse)
Pulls (Docker Hub) (differs)59 064No figure on Docker Hub
Forks (GitHub) (differs)7 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/jetbrains)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)30Not published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Hooks it runs (differs)Not published3
Parts of the bundle (differs)Not a bundle3
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/gannachernyshova/mcp-jetbrainsgithub.com/nessos666/context-bench
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

JetBrains

In its own words, on Docker MCP Catalog:

A model context protocol server to work with JetBrains IDEs: IntelliJ, PyCharm, WebStorm, etc. Also, works with Android Studio.

context-bench

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

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.

How to run each

JetBrains As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio jetbrains -- docker run -i --rm mcp/jetbrains

context-bench As a Claude Code plugin

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

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of context-bench publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of context-bench publish no settings it asks for, so we do not compare settings.

What it can do: JetBrains · What it can do: context-bench · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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