Ext Ops Panel
Open dashboard
Comparison

AWS Data Processing vs CloudQuell

AWS Data Processing is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). CloudQuell is an MCP server published by cloudquell.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceAWS Data ProcessingCloudQuell
Docker MCP Catalog Listed
Version: sha256:8dc85c2f47b4
Forks (GitHub): 1 817
Pulls (Docker Hub): 31 151
Stars (Docker Hub): 0
Stars (GitHub): 9 794
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.7.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

AWS Data Processing vs CloudQuell
FactAWS Data ProcessingCloudQuell
Marketplaces that list it11
Stars (GitHub) (differs)9 794No figure on GitHub
Pulls (Docker Hub) (differs)31 151No figure on Docker Hub
Forks (GitHub) (differs)1 817No figure on GitHub
Last release (differs)Not published2026-10-13
Where it runs (differs)On your machine (mcp/aws-dataprocessing-mcp-server)Remote server (mcp.cloudquell.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)32Not published
Environment variables it asks for (differs)2, secrets among them: 0Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpNot stated
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (4 h ago)

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

AWS Data Processing

In its own words, on Docker MCP Catalog:

Data processing and transformation services.

CloudQuell

In its own words, on Official MCP Registry:

Ask about AWS, Azure, GCP, OpenAI, Anthropic and Snowflake costs, budgets, and anomalies.

How to run each

AWS Data Processing As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio aws-dataprocessing -- docker run -i --rm mcp/aws-dataprocessing-mcp-server

CloudQuell As a remote MCP server

Claude Code
claude mcp add --transport http cloudquell-mcp-server https://mcp.cloudquell.com/mcp

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

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

Tools each declares

The marketplaces of CloudQuell publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: AWS Data Processing · What it can do: CloudQuell · 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