AWS Data Processing vs Yaw Labs AWS MCP
AWS Data Processing is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Yaw Labs AWS MCP is an MCP server published by YawLabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
| Marketplace |  AWS Data Processing |  Yaw Labs AWS MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:8dc85c2f47b4 Forks (GitHub): 1 812 Pulls (Docker Hub): 31 078 Stars (Docker Hub): 0 Stars (GitHub): 9 782 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.6.0 Downloads/month (npm): 4 585 Downloads/week (npm): 697 Forks (GitHub): 1 Stars (GitHub): 5 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
| Fact | AWS Data Processing | Yaw Labs AWS MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 782 (better) | 5 (worse) |
| Pulls (Docker Hub) (differs) | 31 078 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 812 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-dataprocessing-mcp-server) | On your machine (@yawlabs/aws-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 32 | Not published |
| Environment variables it asks for | 2, secrets among them: 0 | 2, secrets among them: 0 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/yawlabs/aws-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
AWS Data Processing
Data processing and transformation services.
Yaw Labs AWS MCP
AWS MCP server — call any AWS API from AI assistants, with first-class SSO re-login
How to run each
AWS Data Processing As a local MCP server: Docker image
claude mcp add --transport stdio aws-dataprocessing -- docker run -i --rm mcp/aws-dataprocessing-mcp-serverYaw Labs AWS MCP As a local MCP server: npm package
claude mcp add --transport stdio aws-mcp -- npx -y @yawlabs/aws-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Yaw Labs AWS MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only AWS Data Processing asks for
None
Only Yaw Labs AWS MCP asks for
None
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: AWS Data Processing · What it can do: Yaw Labs AWS MCP · 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.