Ext Ops Panel
Open dashboard
Comparison

Python Interpreter vs Qiskit Code Assistant MCP Server

Python Interpreter is an MCP server published by akuadane. Marketplaces we read that list it: 1 (Docker MCP Catalog). Qiskit Code Assistant MCP Server is an MCP server published by Qiskit. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplacePython InterpreterQiskit Code Assistant MCP Server
Docker MCP Catalog Listed
Version: sha256:d6ce03d191c7
Forks (GitHub): 5
Pulls (Docker Hub): 57 407
Stars (Docker Hub): 2
Stars (GitHub): 16
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.0
Downloads/month (PyPI): 730
Downloads/week (PyPI): 40
Forks (GitHub): 20
Stars (GitHub): 40
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

Python Interpreter vs Qiskit Code Assistant MCP Server
FactPython InterpreterQiskit Code Assistant MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)16 (worse)40 (better)
Pulls (Docker Hub) (differs)57 407No figure on Docker Hub
Forks (GitHub) (differs)5 (worse)20 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mcp-code-interpreter)On your machine (qiskit-code-assistant-mcp-server)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/akuadane/mcp-code-interpretergithub.com/qiskit/mcp-servers
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

Python Interpreter

In its own words, on Docker MCP Catalog:

A Python-based execution tool that mimics a Jupyter notebook environment. It accepts code snippets, executes them, and maintains state across sessions — preserving variables, imports, and past results. Ideal for iterative development, debugging, or code execution.

Qiskit Code Assistant MCP Server

In its own words, on Official MCP Registry:

MCP server for the Qiskit Code Assistant intelligent code completion

How to run each

Python Interpreter As a local MCP server: Docker image

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

Qiskit Code Assistant MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "QISKIT_IBM_TOKEN=<YOUR_QISKIT_IBM_TOKEN>" --transport stdio qiskit-code-assistant-mcp-server -- uvx qiskit-code-assistant-mcp-server

Requires: QISKIT_IBM_TOKEN (secret)

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

Tools each declares

The marketplaces of Qiskit Code Assistant MCP Server publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Python Interpreter publish no settings it asks for, so we do not compare settings.

What it can do: Python Interpreter · What it can do: Qiskit Code Assistant MCP Server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built