AWS API vs dev.wraps/email
AWS API is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). dev.wraps/email is an MCP server published by wraps.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  AWS API |  dev.wraps/email |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:d7a48c778ce2 Forks (GitHub): 1 805 Pulls (Docker Hub): 32 823 Stars (Docker Hub): 0 Stars (GitHub): 9 773 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.8.2 Downloads/month (npm): 888 Downloads/week (npm): 59 Forks (GitHub): 0 Stars (GitHub): 1 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 | dev.wraps/email |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 773 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 32 823 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 805 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-api-mcp-server) | On your machine (@wraps.dev/mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 2 | 7, secrets among them: 0 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/wraps-team/wraps-js |
| 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 API
Comprehensive AWS API support with command validation and access to all services.
dev.wraps/email
Send email through your own Amazon SES account, and check domains, suppressions and sandbox status.
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)
dev.wraps/email As a local MCP server: npm package
claude mcp add --transport stdio email -- npx -y @wraps.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of dev.wraps/email publish no list of tools, so we do not compare tools.
Settings each asks for
Only AWS API asks for
AWS_ACCESS_KEY_IDAWS_API_MCP_PROFILE_NAMEAWS_SECRET_ACCESS_KEY (secret)AWS_SESSION_TOKEN (secret)
Only dev.wraps/email asks for
AWS_PROFILEWRAPS_ALLOWED_RECIPIENTSWRAPS_ALLOWED_RECIPIENT_DOMAINSWRAPS_FROM_EMAILWRAPS_HISTORY_TABLE_NAMEWRAPS_WRITE_ENABLED
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: AWS API · What it can do: dev.wraps/email · 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.