AWS Cloud Control API vs Nerdio Manager MCP
AWS Cloud Control API is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Nerdio Manager 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-15. 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 Cloud Control API |   Nerdio Manager MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b53d235b43c4 Forks (GitHub): 1 808 Pulls (Docker Hub): 14 586 Stars (Docker Hub): 0 Stars (GitHub): 9 782 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.4 Forks (GitHub): 13 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 Cloud Control API | Nerdio Manager MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 9 782 (better) | 59 (worse) |
| Pulls (Docker Hub) (differs) | 14 586 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 808 (better) | 13 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/ccapi-mcp-server) | On your machine (https://github.com/Servosity/msp-skills/releases/download/nerdio-v0.1.4/nerdio-mcp.mcpb) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 14 | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | 6, secrets among them: 5 |
| 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 Cloud Control API
Direct resource management with security scanning.
Nerdio Manager MCP
The first non-PowerShell client for the Nerdio Manager for MSP API - cross-account AVD fleet
How to run each
AWS Cloud Control API As a local MCP server: Docker image
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --transport stdio awslabs-ccapi -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY mcp/ccapi-mcp-serverRequires: AWS_SECRET_ACCESS_KEY (secret)
Nerdio Manager MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install nerdio@msp-skillsRequires: NERDIO_BASE_URL (secret), NERDIO_CLIENT_ID (secret), NERDIO_CLIENT_SECRET (secret), NERDIO_OAUTH_SCOPE (secret), NERDIO_TOKEN_URL (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 Nerdio Manager MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only AWS Cloud Control API asks for
AWS_ACCESS_KEY_IDAWS_PROFILEAWS_REGIONAWS_SECRET_ACCESS_KEY (secret)
Only Nerdio Manager MCP asks for
NERDIO_BASE_URL (secret)NERDIO_CLIENT_ID (secret)NERDIO_CLIENT_SECRET (secret)NERDIO_NO_CONFIG_WRITENERDIO_OAUTH_SCOPE (secret)NERDIO_TOKEN_URL (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: AWS Cloud Control API · What it can do: Nerdio Manager 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.