AWS API vs Amazon Web Services MCP
AWS API is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Amazon Web Services MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, 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
| Marketplace |  AWS API |   Amazon Web Services MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:d7a48c778ce2 Forks (GitHub): 1 806 Pulls (Docker Hub): 32 985 Stars (Docker Hub): 0 Stars (GitHub): 9 779 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.4 Forks (GitHub): 12 Stars (GitHub): 59 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 API | Amazon Web Services MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 9 779 (better) | 59 (worse) |
| Pulls (Docker Hub) (differs) | 32 985 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 806 (better) | 12 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-api-mcp-server) | On your machine (https://github.com/Servosity/msp-skills/releases/download/aws-billing-v0.1.4/aws-billing-mcp.mcpb) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 2 | 6, secrets among them: 3 |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/awslabs/mcp | github.com/servosity/msp-skills |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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 API
Comprehensive AWS API support with command validation and access to all services.
Amazon Web Services MCP
Get a non-expert from zero to a Slack-delivered, plain-English, waste-flagged AWS bill breakdown
How to run each
AWS API As a local MCP server: Docker image
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --env "AWS_SESSION_TOKEN=<YOUR_AWS_SESSION_TOKEN>" --transport stdio aws-api -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN mcp/aws-api-mcp-serverRequires: AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)
Amazon Web Services MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install aws-billing@msp-skillsRequires: AWS_ACCESS_KEY_ID (secret), AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_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 Amazon Web Services MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only AWS API asks for
AWS_API_MCP_PROFILE_NAME
Only Amazon Web Services MCP asks for
AWS_BILLING_BASE_URLAWS_BILLING_SLACK_CHANNEL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: AWS API · What it can do: Amazon Web Services 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. 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.