AWS CloudFormation vs io.github.dockndevai/mcp-azure
AWS CloudFormation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.dockndevai/mcp-azure is an MCP server published by dockndevai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:d1c0846eb6e5 Forks (GitHub): 1 830 Pulls (Docker Hub): 18 068 Stars (Docker Hub): 0 Stars (GitHub): 9 835 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.0 Downloads/month (npm): 568 Downloads/week (npm): 102 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 CloudFormation | io.github.dockndevai/mcp-azure |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 835 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 18 068 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 830 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/cfn-mcp-server) | On your machine (@dockndevai/mcp-azure) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 2 | 5, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/dockndevai/mcp-azure |
| 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 CloudFormation
CloudFormation resource management via Cloud Control API.
io.github.dockndevai/mcp-azure
Azure Resource Manager inventory & ops for AI agents — governed, confirmation-gated.
How to run each
AWS CloudFormation 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 awslabs-cfn -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN mcp/cfn-mcp-server
Requires: AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)
io.github.dockndevai/mcp-azure As a local MCP server: npm package
claude mcp add --env "AZURE_CLIENT_ID=<YOUR_AZURE_CLIENT_ID>" --env "AZURE_CLIENT_SECRET=<YOUR_AZURE_CLIENT_SECRET>" --env "AZURE_TENANT_ID=<YOUR_AZURE_TENANT_ID>" --transport stdio mcp-azure -- npx -y @dockndevai/mcp-azure
Requires: AZURE_CLIENT_ID, AZURE_CLIENT_SECRET (secret), AZURE_TENANT_ID
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.dockndevai/mcp-azure publish no list of tools, so we do not compare tools.
Settings each asks for
Only AWS CloudFormation asks for
AWS_ACCESS_KEY_IDAWS_PROFILEAWS_REGIONAWS_SECRET_ACCESS_KEY (secret)AWS_SESSION_TOKEN (secret)
Only io.github.dockndevai/mcp-azure asks for
AZURE_CLIENT_IDAZURE_CLIENT_SECRET (secret)AZURE_MODEAZURE_SUBSCRIPTION_IDAZURE_TENANT_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: AWS CloudFormation · What it can do: io.github.dockndevai/mcp-azure · 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.