Ext Ops Panel
Open dashboard
Comparison

AWS API vs cloudxray

AWS API is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). cloudxray is a plugin bundle for AI coding tools published by CloudXray AI. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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

Where each is published
MarketplaceAWS APIcloudxray
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
Community marketplace cloudxrayai/cloudxray-ai Not listed Listed
Version: 1.0.0
No figure published
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 API vs cloudxray
FactAWS APIcloudxray
Marketplaces that list it11
Stars (GitHub) (differs)9 773No figure on GitHub
Pulls (Docker Hub) (differs)32 823No figure on Docker Hub
Forks (GitHub) (differs)1 805No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/aws-api-mcp-server)Remote server (cloudxray.ai/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for (differs)5, secrets among them: 2Not published
Parts of the bundle (differs)Not a bundle2
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/awslabs/mcpgithub.com/cloudxrayai/cloudxray-ai
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

In its own words, on Docker MCP Catalog:

Comprehensive AWS API support with command validation and access to all services.

cloudxray

In its own words, on Community GitHub marketplaces:

Search, compare and shortlist FinOps vendors from the CloudXray AI directory, with a guided vendor-selection skill

How to run each

AWS API As a local MCP server: Docker image

Claude Code
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-server

Requires: AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)

cloudxray As a Claude Code plugin

Claude Code
/plugin marketplace add cloudxrayai/cloudxray-ai
/plugin install cloudxray@cloudxray

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

Tools each declares

The marketplaces of cloudxray publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: AWS API · What it can do: cloudxray · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built