Ext Ops Panel
Open dashboard
Comparison

Python Interpreter vs appwrite

Python Interpreter is an MCP server published by akuadane. Marketplaces we read that list it: 1 (Docker MCP Catalog). appwrite is a plugin bundle for AI coding tools published by appwrite. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). 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
MarketplacePython Interpreterappwrite
Docker MCP Catalog Listed
Version: sha256:d6ce03d191c7
Forks (GitHub): 5
Pulls (Docker Hub): 57 363
Stars (Docker Hub): 2
Stars (GitHub): 16
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: 0.2.0
Forks (GitHub): 1
Stars (GitHub): 10
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 10
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 appwrite
FactPython Interpreterappwrite
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)16 (better)10 (worse)
Pulls (Docker Hub) (differs)57 363No figure on Docker Hub
Forks (GitHub) (differs)5 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mcp-code-interpreter)Remote server (mcp.appwrite.io)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)Not a bundle15
Licence (differs)MITBSD-3-Clause
Repository (differs)github.com/akuadane/mcp-code-interpretergithub.com/appwrite/claude-plugin
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 h ago, requires a key

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.

appwrite

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

Appwrite tools for Claude Code, including SDK skills, Appwrite MCP servers, and deployment commands.

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

appwrite As a Claude Code plugin

Claude Code
/plugin install appwrite@claude-plugins-official

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

Only appwrite has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of appwrite 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: appwrite · 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-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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