Ext Ops Panel
Open dashboard
Comparison

AWS Bedrock AgentCore vs strands-sdk

AWS Bedrock AgentCore is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). strands-sdk is a plugin bundle for AI coding tools published by sagarr-shellkode. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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 Bedrock AgentCorestrands-sdk
Docker MCP Catalog Listed
Version: sha256:df610a7a056f
Forks (GitHub): 1 805
Pulls (Docker Hub): 19 985
Stars (Docker Hub): 0
Stars (GitHub): 9 773
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: da1522d
Forks (GitHub): 0
Stars (GitHub): 0
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 strands-sdk
FactAWS Bedrock AgentCorestrands-sdk
Marketplaces that list it11
Stars (GitHub) (differs)9 773 (better)0 (worse)
Pulls (Docker Hub) (differs)19 985No figure on Docker Hub
Forks (GitHub) (differs)1 805 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/amazon-bedrock-agentcore-mcp-server)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)122Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpgithub.com/sagarr-shellkode/strands-sdk
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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.

strands-sdk

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

Comprehensive Strands-agents SDK reference for Claude Code — tools, hooks, multi-agent patterns (A2A, swarms, agents-as-tools), prompt caching, guardrails, model providers, metrics, prompt engineering, best practices, and troubleshooting

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

strands-sdk As a Claude Code plugin

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

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

Tools each declares

The marketplaces of strands-sdk 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: strands-sdk · 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