AWS Core vs Azure DevOps On-Premises
AWS Core is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Azure DevOps On-Premises is an MCP server published by zwitbaum. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 Core |  Azure DevOps On-Premises |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:f624682618e2 Forks (GitHub): 1 812 Pulls (Docker Hub): 129 227 Stars (Docker Hub): 3 Stars (GitHub): 9 782 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.1.0 Downloads/month (PyPI): 409 Downloads/week (PyPI): 55 Forks (GitHub): 1 Stars (GitHub): 5 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 Core | Azure DevOps On-Premises |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 782 (better) | 5 (worse) |
| Pulls (Docker Hub) (differs) | 129 227 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 812 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-core-mcp-server) | On your machine (mcp-devops-onpremise) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 3 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/zwitbaum/mcp-devops-on-prem |
| 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 Core
Starting point for using the awslabs MCP servers.
Azure DevOps On-Premises
MCP server for on-premises Azure DevOps Server and TFS: repos, pull requests, work items, and wiki.
How to run each
AWS Core As a local MCP server: Docker image
claude mcp add --transport stdio aws-core-mcp-server -- docker run -i --rm mcp/aws-core-mcp-serverAzure DevOps On-Premises As a local MCP server: PyPI package
claude mcp add --env "DEVOPS_API_URL=<YOUR_DEVOPS_API_URL>" --env "DEVOPS_PASSWORD=<YOUR_DEVOPS_PASSWORD>" --env "DEVOPS_PAT=<YOUR_DEVOPS_PAT>" --env "DEVOPS_TOKEN=<YOUR_DEVOPS_TOKEN>" --transport stdio mcp-devops-on-prem -- uvx mcp-devops-onpremiseRequires: DEVOPS_API_URL, DEVOPS_PASSWORD (secret), DEVOPS_PAT (secret), DEVOPS_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 Azure DevOps On-Premises publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of AWS Core publish no settings it asks for, so we do not compare settings.
What it can do: AWS Core · What it can do: Azure DevOps On-Premises · 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.