AWS Core vs Hackle
AWS Core is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Hackle is an MCP server published by hackle-io. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). 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 |  AWS Core |  Hackle |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:f624682618e2 Forks (GitHub): 1 830 Pulls (Docker Hub): 131 296 Stars (Docker Hub): 3 Stars (GitHub): 9 835 Not marked · First seen |
Listed Version: sha256:b45e8e1c6390 Forks (GitHub): 3 Pulls (Docker Hub): 16 426 Stars (Docker Hub): 0 Stars (GitHub): 3 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 3 Stars (GitHub): 3 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 | Hackle |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 9 835 (better) | 3 (worse) |
| Pulls (Docker Hub) (differs) | 131 296 (better) | 16 426 (worse) |
| Forks (GitHub) (differs) | 1 830 (better) | 3 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-core-mcp-server) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP, stdio |
| Tools it declares (differs) | 1 | 19 |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/awslabs/mcp | github.com/hackle-io/hackle-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-22 |
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.
Hackle
Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.
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-serverHackle As a remote MCP server
claude mcp add --transport http hackle-mcp https://mcp.hackle.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Hackle has a remote endpoint we check. How we check endpoints
Tools each declares
Only AWS Core declares
prompt_understanding
Only Hackle declares
active-user-seriesanalytics-chart-detailanalytics-chart-listdata-report-detaildata-report-listexperiment-detailexperiment-listin-app-message-detailin-app-message-listpush-message-detailpush-message-listremote-config-create
Show the remaining 7
remote-config-detailremote-config-listremote-config-updateremote-config-update-descriptionremote-config-update-user-identifier-criteriaretention-seriesstickiness-series
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
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: Hackle · 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.