Ext Ops Panel
Open dashboard
Comparison

AWS Core vs mcp-mail-server

AWS Core is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). mcp-mail-server is an MCP server published by yunfeizhu. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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 Coremcp-mail-server
Docker MCP Catalog Listed
Version: sha256:f624682618e2
Forks (GitHub): 1 857
Pulls (Docker Hub): 134 200
Stars (Docker Hub): 3
Stars (GitHub): 9 892
Not marked · First seen
Not listed
npm registry (MCP servers) Not listed Listed
Version: 2.1.2
Downloads/month (npm): 2 777
Downloads/week (npm): 659
Forks (GitHub): 29
Stars (GitHub): 54
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 Core vs mcp-mail-server
FactAWS Coremcp-mail-server
Marketplaces that list it11
Stars (GitHub) (differs)9 892 (better)54 (worse)
Pulls (Docker Hub) (differs)134 200No figure on Docker Hub
Forks (GitHub) (differs)1 857 (better)29 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (mcp/aws-core-mcp-server)On your machine (mcp-mail-server)
Transport (differs)stdioNot stated
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/awslabs/mcpgithub.com/yunfeizhu/mcp-mail-server
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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 Core

In its own words, on Docker MCP Catalog:

Starting point for using the awslabs MCP servers.

mcp-mail-server

In its own words, on npm registry (MCP servers):

MCP server for IMAP/SMTP email access with environment-based configuration

How to run each

AWS Core As a local MCP server: Docker image

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

mcp-mail-server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

The marketplaces of mcp-mail-server publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: AWS Core · What it can do: mcp-mail-server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). 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