Ext Ops Panel
Open dashboard
Comparison

AWS Core vs StackQL MCP Server

AWS Core is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). StackQL MCP Server is an MCP server published by stackql. Marketplaces we read that list it: 1 (Official MCP Registry). 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 CoreStackQL MCP Server
Docker MCP Catalog Listed
Version: sha256:f624682618e2
Forks (GitHub): 1 805
Pulls (Docker Hub): 128 228
Stars (Docker Hub): 3
Stars (GitHub): 9 773
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.12.778
Forks (GitHub): 87
Stars (GitHub): 1 069
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 Core vs StackQL MCP Server
FactAWS CoreStackQL MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)9 773 (better)1 069 (worse)
Pulls (Docker Hub) (differs)128 228No figure on Docker Hub
Forks (GitHub) (differs)1 805 (better)87 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (mcp/aws-core-mcp-server)On your machine (https://github.com/stackql/stackql/releases/download/v0.12.778/stackql-mcp-linux-x64.mcpb)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpgithub.com/stackql/stackql
Changes in the last 7 days (differs)02
First seen2026-10-112026-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

In its own words, on Docker MCP Catalog:

Starting point for using the awslabs MCP servers.

StackQL MCP Server

In its own words, on Official MCP Registry:

SQL-native query and provisioning engine for cloud infrastructure, served over MCP.

How to run each

AWS Core As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio aws-core-mcp-server -- docker run -i --rm mcp/aws-core-mcp-server

StackQL MCP Server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

The marketplaces of StackQL MCP Server publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: AWS Core · What it can do: StackQL MCP Server · 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.

Where the data comes from: how the catalog is built