Ext Ops Panel
Open dashboard
Comparison

JetBrains vs mcp-debugger

JetBrains is an MCP server published by GannaChernyshova. Marketplaces we read that list it: 1 (Docker MCP Catalog). mcp-debugger is a plugin bundle for AI coding tools published by bherbruck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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
MarketplaceJetBrainsmcp-debugger
Docker MCP Catalog Listed
Version: sha256:a662cac15c5d
Forks (GitHub): 7
Pulls (Docker Hub): 59 098
Stars (Docker Hub): 2
Stars (GitHub): 9
Not marked · First seen
Not listed
Community marketplace bherbruck/mcp-debugger Not listed Listed
Version: 1.2.0
No figure published
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 mcp-debugger
FactJetBrainsmcp-debugger
Marketplaces that list it11
Stars (GitHub) (differs)9No figure on GitHub
Pulls (Docker Hub) (differs)59 098No figure on Docker Hub
Forks (GitHub) (differs)7No figure on GitHub
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 for1, secrets among them: 01, secrets among them: 0
Parts of the bundle (differs)Not a bundle5
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/gannachernyshova/mcp-jetbrainsgithub.com/bherbruck/mcp-debugger
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14

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.

mcp-debugger

In its own words, on Community GitHub marketplaces:

Multi-language debugging via DAP - debug Python, JavaScript/TypeScript, Go, and Rust

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

mcp-debugger As a Claude Code plugin

Claude Code
/plugin marketplace add bherbruck/mcp-debugger
/plugin install mcp-debugger@mcp-debugger

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

Tools each declares

The marketplaces of mcp-debugger publish no list of tools, so we do not compare tools.

Settings each asks for

Only JetBrains asks for

  • IDE_PORT

Only mcp-debugger asks for

  • NODE_ENV

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: JetBrains · What it can do: mcp-debugger · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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