Skip to content
← Tools / Skills
ToolAWS Labs/10 trustVerified

AWS Labs MCP Servers

AWS's official collection of MCP servers — manage EC2, S3, Lambda, and 100+ AWS services from your agent.

Visit official site →

About

awslabs/mcp (9.7k stars, Apache-2.0) is AWS Labs' official collection of MCP servers covering dozens of AWS services: EC2, S3, Lambda, CloudWatch, cost analysis, CDK, EKS, and more — installable per-server via uvx.

Verified Oct 2026 from the repo README: AWS now positions Agent Toolkit for AWS (launched May 2026) as the successor for production agent builds — "the successor to the MCP servers, plugins, and skills available on AWS Labs" — while this repo "continues to work and accept contributions." There is also a hosted, managed AWS MCP Server (remote, IAM-based, zero credential exposure, CloudTrail audit logging) documented at docs.aws.amazon.com. As with any cloud-control-plane tool, the agent inherits your AWS credentials' power: scope IAM roles tightly, and note at least one server in the collection (Cloud Control API) is marked DEPRECATED.

What it can do

  • MCP servers for dozens of AWS services (compute, storage, serverless, EKS, observability, cost)
  • Hosted managed AWS MCP Server option: remote, IAM-based, zero credential exposure, CloudTrail logging
  • Apache-2.0, AWS Labs-maintained, 100 releases in 12 months
  • One-click installers for Kiro, Cursor, and VS Code per server
  • Note: AWS now steers production builds toward Agent Toolkit for AWS (May 2026); this collection continues with contributions

Setup

  1. Install uv (recommended): most servers run as uvx awslabs.<server-name>@latest.
  2. Configure AWS credentials (aws configure or IAM roles) with least-privilege policies.
  3. Pick the servers you need from the collection README's install table.
  4. Add each server's command to your MCP client config (one-click installers exist for Kiro, Cursor, VS Code).
  5. For production: evaluate the hosted AWS MCP Server (IAM-based, no local credential exposure) or the new Agent Toolkit for AWS instead of individual lab servers.

Prerequisites

An AWS account; AWS credentials with scoped IAM permissions; uv or Node.js.

Use cases

mcpmcp-serversdevopsautomationdata

Works with

Claude CodeCursorAny agent (.md)Generic API

Trust score — 8/10

/10 trustVerified

Scored 8/10 (metrics tier). AWS-official, Apache-2.0, and the most actively released collection in this batch (100 releases/12mo, 9.7k stars). Docked two points: (1) an agent with your AWS credentials is one mis-scoped IAM role away from an expensive mistake — least privilege is mandatory; (2) quality varies across 100+ servers in a monorepo, so evaluate the specific ones you need.

★ 9,773 GitHub stars

How the trust score is built

Full methodology →
Adoption · stars/downloads, log-scaled vs peers
7.6/10
Maintenance · recency, releases, issue load
9.0/10
Openness · license + docs
10.0/10
Manual review · sanity read + red-flag check
8.0/10
  • · 9,773 GitHub stars (log-scaled vs catalog peers)
  • · last push 0d ago; 100 releases/12mo; 243 open issues
  • · manual review: AWS-official collection (9.7k stars), 100 releases/12mo; AWS now steers production builds to Agent Toolkit for AWS (May 2026) — this repo continues with contributions; agent inherits AWS credential power, least-privilege IAM mandatory

Sources

Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.