Ext Ops Panel
Open dashboard
Comparison

AWS Bedrock AgentCore vs styx

AWS Bedrock AgentCore is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). styx is a plugin bundle for AI coding tools published by timmx7. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-14. 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 Bedrock AgentCorestyx
Docker MCP Catalog Listed
Version: sha256:df610a7a056f
Forks (GitHub): 1 806
Pulls (Docker Hub): 20 000
Stars (Docker Hub): 0
Stars (GitHub): 9 779
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
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

AWS Bedrock AgentCore vs styx
FactAWS Bedrock AgentCorestyx
Marketplaces that list it11
Stars (GitHub) (differs)9 779 (better)5 (worse)
Pulls (Docker Hub) (differs)20 000No figure on Docker Hub
Forks (GitHub) (differs)1 806 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/amazon-bedrock-agentcore-mcp-server)Remote server (localhost/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)122Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle5
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/awslabs/mcpgithub.com/timmx7/styx
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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 Bedrock AgentCore

In its own words, on Docker MCP Catalog:

Documentation on AgentCore platform services.

styx

In its own words, on Claude Code: claude-plugins-community:

The MCP-native AI API gateway for developers building with LLMs. Every app using AI needs API keys, cost control, and provider flexibility — Styx gives you all three through one endpoint. Route requests to OpenAI, Anthropic, Google, or Mistral with automatic failover, track spending in real-time, and manage team access with scoped API keys. Self-hosted, open source, and manageable directly from Claude Code with /styx:setup, /styx:status, and @styx-ops.

How to run each

AWS Bedrock AgentCore As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio amazon-bedrock-agentcore -- docker run -i --rm mcp/amazon-bedrock-agentcore-mcp-server

styx As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install styx@claude-community

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

Only styx has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of styx 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 Bedrock AgentCore · What it can do: styx · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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