AWS Bedrock AgentCore vs agent-orchestration
AWS Bedrock AgentCore is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). agent-orchestration is a plugin bundle for AI coding tools published by Grey Haven Studio. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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 Bedrock AgentCore | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:df610a7a056f Forks (GitHub): 1 817 Pulls (Docker Hub): 20 143 Stars (Docker Hub): 0 Stars (GitHub): 9 798 Not marked · First seen |
Not listed |
| Community marketplace greyhaven-ai/claude-code-config | Not listed | Listed Version: 1.0.0 Forks (GitHub): 5 Stars (GitHub): 30 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 Bedrock AgentCore | agent-orchestration |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 798 (better) | 30 (worse) |
| Pulls (Docker Hub) (differs) | 20 143 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 817 (better) | 5 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/amazon-bedrock-agentcore-mcp-server) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 122 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/awslabs/mcp | github.com/greyhaven-ai/claude-code-config |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-20 |
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
Documentation on AgentCore platform services.
agent-orchestration
Multi-agent orchestration with context management, workflow composition, and agent coordination. Enables complex multi-step tasks through systematic agent delegation, context handoff, and workflow automation.
How to run each
AWS Bedrock AgentCore As a local MCP server: Docker image
claude mcp add --transport stdio amazon-bedrock-agentcore -- docker run -i --rm mcp/amazon-bedrock-agentcore-mcp-serveragent-orchestration As a Claude Code plugin
/plugin marketplace add greyhaven-ai/claude-code-config
/plugin install agent-orchestration@grey-haven-pluginsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of agent-orchestration 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: agent-orchestration · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.