AWS Bedrock AgentCore vs AgentExec WebMCP & Base L2 Gateway
AWS Bedrock AgentCore is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). AgentExec WebMCP & Base L2 Gateway is an MCP server published by Har50. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 806 Pulls (Docker Hub): 20 009 Stars (Docker Hub): 0 Stars (GitHub): 9 779 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.2 No figure published 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 | AgentExec WebMCP & Base L2 Gateway |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 779 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 20 009 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 806 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/amazon-bedrock-agentcore-mcp-server) | Remote server (api.agentexec.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 122 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/har50/agent1 |
| 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 | Responded 43 h ago |
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.
AgentExec WebMCP & Base L2 Gateway
Monetization and execution gateway for autonomous AI agents on Base Mainnet
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-serverAgentExec WebMCP & Base L2 Gateway As a remote MCP server
claude mcp add --transport http gateway https://api.agentexec.dev/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only AgentExec WebMCP & Base L2 Gateway has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of AgentExec WebMCP & Base L2 Gateway 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: AgentExec WebMCP & Base L2 Gateway · 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.