AWS MCP Servers (awslabs/mcp)

Use it when

• Your AI coding assistant keeps suggesting deprecated AWS APIs or invented CloudFormation properties and you need it grounded in current official AWS documentation
• You want an agent in Cursor, Claude Code, Kiro, or Windsurf to inspect and operate AWS services such as EKS, ECS, Lambda, Bedrock, or Kendra through vetted MCP tools instead of hand-written scripts

What it solves

Not the fit when

• SSE transport clients (SSE support removed May 2025; repo servers are stdio only)
• clouds other than AWS
• production agent deployments where AWS recommends the successor Agent Toolkit for AWS
• servers that manage live resources require AWS credentials and IAM permissions; grant write and sensitive-data flags deliberately
• building your own custom MCP server from scratch
• non-AWS cloud provider operations
• browser automation
• local LLM inference
• general web search for agents

Install

uvx awslabs.aws-documentation-mcp-server@latest (run via your MCP client; other servers in the suite install the same way, e.g. awslabs.eks-mcp-server, awslabs.aws-serverless-mcp-server)

Invoke

Add to your MCP client config (e.g. .mcp.json for Claude Code): {"command":"uvx","args":["awslabs.aws-documentation-mcp-server@latest"],"env":{"FASTMCP_LOG_LEVEL":"ERROR"}} - the agent then queries live AWS docs and service tools

Alternatives

No reviewed alternatives recorded yet.