Ext Ops Panel
Open dashboard
Comparison

AWS Documentation vs Eco Router

AWS Documentation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Eco Router is an MCP server published by stevensu04. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 DocumentationEco Router
Docker MCP Catalog Listed
Version: sha256:07888232dde9
Forks (GitHub): 1 826
Pulls (Docker Hub): 121 942
Stars (Docker Hub): 2
Stars (GitHub): 9 823
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (npm): 348
Downloads/week (npm): 20
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

AWS Documentation vs Eco Router
FactAWS DocumentationEco Router
Marketplaces that list it11
Stars (GitHub) (differs)9 823 (better)1 (worse)
Pulls (Docker Hub) (differs)121 942No figure on Docker Hub
Forks (GitHub) (differs)1 826 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/aws-documentation)On your machine (eco-router-mcp)
Transportstdiostdio
Tools it declares (differs)4Not published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpgithub.com/stevensu04/eco-router-mcp
Changes in the last 7 days00
First seen2026-10-112026-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 Documentation

In its own words, on Docker MCP Catalog:

Tools to access AWS documentation, search for content, and get recommendations.

Eco Router

In its own words, on Official MCP Registry:

Rank AWS, Google Cloud and Azure regions by grid carbon intensity and latency.

How to run each

AWS Documentation As a local MCP server: Docker image

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

Eco Router As a local MCP server: npm package

Claude Code
claude mcp add --env "ELECTRICITY_MAPS_API_TOKEN=<YOUR_ELECTRICITY_MAPS_API_TOKEN>" --transport stdio eco-router-mcp -- npx -y eco-router-mcp

Requires: ELECTRICITY_MAPS_API_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 Eco Router publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: AWS Documentation · What it can do: Eco Router · 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