Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldAWS Documentation MCPMCP100 SelectedDocker MCP GatewayMCP100 Selected
Task fit
Best for
  • Searching and reading current AWS service and API documentation
  • Finding related AWS documentation and regional documentation variants
  • Cloud-development questions that do not require AWS account access
  • Running multiple MCP servers behind one stdio connection
  • Isolating catalog MCP servers in containers with restricted privileges and resources
  • Centralizing server profiles, secrets, OAuth, logs, and call traces
Not ideal for
  • Inspecting or changing resources in an AWS account
  • Authoritative architecture approval without human review
  • Users who need only one simple remote MCP endpoint
  • Hosts where Docker Desktop or Docker Engine cannot run
Avoid when
  • Queries may contain credentials, customer data, or confidential architecture details
  • The environment cannot make outbound requests to public AWS documentation
  • You cannot review every downstream MCP server and profile permission
  • The agent must not be able to discover or add tools dynamically
  • Container isolation is being treated as protection from an over-privileged downstream credential
Provenance
Provenance details

First-party MCP

Amazon Web Services · Publisher source ↗

First-party MCP

Docker · Publisher source ↗

Maintenance
Maintenance details

Repo: Aug 14, 2026

Package: Not documented

Repo: Aug 13, 2026

Package: Not documented

Popularity evidence
GitHub stars

9,513

GitHub stars · checked 2026-08-14T18:46:26.000Z

1,529

GitHub stars · checked 2026-08-14T18:46:26.000Z

Shared repository stars

9,598

Shared repository stars (not MCP-specific) · checked 2026-08-14T18:46:26.000Z

Not documented
External adoption evidence
  • github: repository stars: 9,598Non-comparable contextual signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
  • github: repository stars: 1,529Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationNo AWS account authentication is documented for the local AWS Documentation MCP Server. The local stdio process requires Python and uv/uvx plus outbound network access.The gateway handles downstream server credentials and OAuth flows. The client connects locally over stdio by running `docker mcp gateway run`, optionally with a named profile.
CostThe AWS Labs server is open source and no separate MCP fee is documented. Network access, the selected AI client, and any AWS services subsequently chosen remain separately chargeable.The open-source gateway documents no standalone usage fee. Docker Desktop licensing, Docker AI Governance invite-only features, container infrastructure, downstream MCP services, and AI-client charges may apply.
PermissionsThe documented server exposes read-oriented AWS documentation search, page reading, recommendation, and related-content tools. It does not require AWS account credentials or grant AWS resource permissions.The gateway exposes the servers and tools included in the selected profile. It starts catalog servers in containers with restricted privileges, network access, and resource usage, injects configured secrets, and can support OAuth. Dynamic MCP can additionally expose tools that discover, add, configure, remove, and execute servers during a session.
Data handlingSearch phrases, documentation URLs, and requested page sections are sent to public AWS documentation services; matching public documentation is returned to the MCP client. Do not include secrets or private workload details in queries.Tool requests and results pass through the local gateway to downstream MCP containers or remote services. Docker documents built-in logging and call tracing. Credentials are managed and injected by the gateway; downstream servers can still receive data and reach networks allowed by their configuration.
Limitations
Tradeoffs
  • It avoids AWS account credentials but still sends documentation searches over the network.
  • Using @latest simplifies updates but is less reproducible than pinning a reviewed package version.
  • Documentation retrieval can be current without guaranteeing that a suggested design is appropriate for the user's workload.
  • Gateway isolation improves lifecycle and credential management but adds Docker runtime complexity and local resource use.
  • The MCP Toolkit is documented as Beta, and Dynamic MCP is experimental.
  • The gateway reduces direct host privileges, but network access and injected credentials still let downstream servers affect external systems.
Risk contextThis is a comparatively narrow read-only integration, but retrieved text is external content and may be incomplete, outdated, or unsuitable. Keep queries non-sensitive and validate consequential recommendations against current AWS service documentation and account-specific requirements. This documentary review does not claim MCP100 execution testing.Gateway safety is only as strong as the selected profile, catalog provenance, tool filters, network policy, and downstream credentials. Disable experimental Dynamic MCP unless required, use narrow profiles, verify signatures where available, inspect traces, and treat each downstream server as a separate trust decision. This review does not claim MCP100 execution testing.
Evidence date
Editorial review2026-07-242026-07-24
Candidate evidence2026-08-14T18:46:26.000Z2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →