AWS MCP Servers
AWS's official MCP servers: sixty-plus specialised ones to pick from, plus two that AWS hosts itself
What is AWS MCP Servers?
Point Claude, Cursor, Kiro or any other MCP client at one of these servers and the model can search current AWS documentation, write CloudFormation and CDK against AWS's own guidance, query DynamoDB or PostgreSQL, read CloudWatch logs and estimate costs — each capability is its own small server, started with one uvx command and your AWS credentials. Two need no setup at all: the hosted Knowledge server answers documentation questions without an AWS account, and the preview AWS MCP Server reaches the AWS APIs under IAM permissions with CloudTrail logging. The open question is longevity: AWS announced the Agent Toolkit for AWS in May 2026 as this suite's successor, recommends it for production agent work, and says the most useful servers here will move into it over time.
What can you do with AWS MCP Servers?
- Start with the two servers AWS runs for you — The Knowledge server is a URL you paste into any MCP client: it answers from current AWS documentation, API references, What's New posts and Well-Architected guidance, and needs no AWS account at all. The AWS MCP Server — in preview — goes further and calls the AWS APIs themselves under your IAM permissions; AWS states the calls are syntactically validated and every action lands in CloudTrail.
- Pick one small server per job, not one giant one — The sixty-plus local servers each cover one service or workflow — DynamoDB, PostgreSQL, EKS, ECS, CloudWatch, pricing, Bedrock and more — and each starts with a single uvx command plus your AWS profile in the client's configuration. Enabling only the two or three you need keeps the model's tool list short enough for it to choose well.
- Infrastructure code checked against AWS's own guidance — The IaC server brings CloudFormation documentation, CDK best practices, construct examples, security validation and deployment troubleshooting into the conversation, so the model writes templates against current guidance instead of its training-data memory of AWS.
- Touching live infrastructure is a per-server decision — The operational servers separate reading from acting: explicit switches such as --allow-write, with a second one for sensitive data, decide whether a server may only inspect your account or also change it. An agent that reports on production can be wired up without the ability to modify it.
Before you choose AWS MCP Servers
- The servers you run yourself speak stdio only — AWS says streamable HTTP is still in the works — so serving a whole team from one shared endpoint is possible only with the two AWS-hosted servers.
- Individual servers get deprecated as the suite reorganises — the Cloud Control API server already points users to the IaC server instead — so a set chosen today needs re-checking on upgrades.
Star history
17 Aug to 28 Aug · +32
Frequently asked questions
Is AWS MCP Servers free for commercial use?
AWS MCP Servers is released under the Apache-2.0 licence — OSI-approved open source, which permits commercial use.
How can AWS MCP Servers be deployed?
AWS MCP Servers is available as Runs locally / Managed cloud / Self-hosted.
Documentation
Reproduced from the awslabs/mcp README, published under Apache-2.0. Read the original ↗
Open source MCP servers for AWS
A suite of specialized MCP servers that help you get the most out of AWS, wherever you use MCP.
[!TIP] The Agent Toolkit for AWS is now live! The Agent Toolkit for AWS is the successor to the MCP servers, plugins, and skills available on AWS Labs, and was informed by feedback from customers like you. If you’re building production software using coding agents or building agents for your own customers, we recommend Agent Toolkit for AWS. It includes IAM condition keys to distinguish agent actions from human ones, CloudWatch and CloudTrail visibility, and skills that have been evaluated for accuracy and effectiveness. This repo continues to work and accept contributions. Over time, the most useful projects here will move into Agent Toolkit for AWS.
Table of Contents
- Open source MCP servers for AWS
- Table of Contents
- What is the Model Context Protocol (MCP) and how does it work with MCP Servers for AWS?
- Open source MCP servers for AWS Transport Mechanisms
- Available MCP Servers: Quick Installation
- 🚀 Getting Started with AWS
- Browse by What You’re Building
- 🏗️ Infrastructure & Deployment
- 🤖 AI & Machine Learning
- 📊 Data & Analytics
- 🛠️ Developer Tools & Support
- 📡 Integration & Messaging
- 💰 Cost & Operations
- 🧬 Healthcare & Lifesciences
- Browse by How You’re Working
- MCP AWS Lambda Handler Module
- When to use Local vs Remote MCP Servers?
- Use Cases for the Servers
- Installation and Setup
- Samples
- Vibe coding
- Additional Resources
- Security
- Contributing
- Developer guide
- License
- Disclaimer
What is the Model Context Protocol (MCP) and how does it work with MCP Servers for AWS?
The Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you’re building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need.
An MCP Server is a lightweight program that exposes specific capabilities through the standardized Model Context Protocol. Host applications (such as chatbots, IDEs, and other AI tools) have MCP clients that maintain 1:1 connections with MCP servers. Common MCP clients include agentic AI coding assistants (like Kiro, Cline, Cursor, Windsurf) as well as chatbot applications like Claude Desktop, with more clients coming soon. MCP servers can access local data sources and remote services to provide additional context that improves the generated outputs from the models.
MCP Servers for AWS use this protocol to provide AI applications access to AWS documentation, contextual guidance, and best practices. Through the standardized MCP client-server architecture, AWS capabilities become an intelligent extension of your development environment or AI application.
MCP Servers for AWS enable enhanced cloud-native development, infrastructure management, and development workflows—making AI-assisted cloud computing more accessible and efficient.
The Model Context Protocol is an open source project run by Anthropic, PBC. and open to contributions from the entire community. For more information on MCP, you can find further documentation here
Open source MCP servers for AWS Transport Mechanisms
Supported transport mechanisms
The MCP protocol currently defines two standard transport mechanisms for client-server communication:
- stdio, communication over standard in and standard out
- streamable HTTP
The MCP servers in this repository are designed to support stdio only.
You are responsible for ensuring that your use of these servers comply with the terms governing them, and any laws, rules, regulations, policies, or standards that apply to you.
Server Sent Events Support Removal
Important Notice: On May 26th, 2025, Server Sent Events (SSE) support was removed from all MCP servers in their latest major versions. This change aligns with the Model Context Protocol specification’s backwards compatibility guidelines.
We are actively working towards supporting Streamable HTTP, which will provide improved transport capabilities for future versions.
For applications still requiring SSE support, please use the previous major version of the respective MCP server until you can migrate to alternative transport methods.
Why MCP Servers for AWS?
MCP servers enhance the capabilities of foundation models (FMs) in several key ways:
-
Improved Output Quality: By providing relevant information directly in the model’s context, MCP servers significantly improve model responses for specialized domains like AWS services. This approach reduces hallucinations, provides more accurate technical details, enables more precise code generation, and ensures recommendations align with current AWS best practices and service capabilities.
-
Access to Latest Documentation: FMs may not have knowledge of recent releases, APIs, or SDKs. MCP servers bridge this gap by pulling in up-to-date documentation, ensuring your AI assistant always works with the latest AWS capabilities.
-
Workflow Automation: MCP servers convert common workflows into tools that foundation models can use directly. Whether it’s CDK, Terraform, or other AWS-specific workflows, these tools enable AI assistants to perform complex tasks with greater accuracy and efficiency.
-
Specialized Domain Knowledge: MCP servers provide deep, contextual knowledge about AWS services that might not be fully represented in foundation models’ training data, enabling more accurate and helpful responses for cloud development tasks.
Available MCP Servers: Quick Installation
Get started quickly with one-click installation buttons for popular MCP clients. Click the buttons below to install servers directly in Cursor or VS Code:
🚀 Getting Started with AWS
For AWS interactions, we recommend starting with:
| Server Name | Description | Install |
|---|---|---|
| AWS MCP Server (in preview) | Start here for secure, auditable AWS interactions! This remote, managed MCP server is hosted by AWS and combines comprehensive AWS API support with access to the latest AWS documentation, API references, What’s New posts, and Getting Started information. Features pre-built Agent SOPs that follow AWS best practices, helping agents complete complex multi-step AWS tasks reliably. Built with safety and control in mind: syntactically validated API calls, IAM-based permissions with zero credential exposure, and complete CloudTrail audit logging. Access all AWS services for managing infrastructure, exploring resources, and executing AWS operations with full transparency and traceability. Read more |
Browse by What You’re Building
📚 Real-time access to official AWS documentation
| Server Name | Description | Install |
|---|---|---|
| AWS Knowledge MCP Server | A remote, fully-managed MCP server hosted by AWS that provides access to the latest AWS docs, API references, What’s New Posts, Getting Started information, Builder Center, Blog posts, Architectural references, and Well-Architected guidance. | |
| AWS Documentation MCP Server | Get latest AWS docs and API references |
🏗️ Infrastructure & Deployment
Build, deploy, and manage cloud infrastructure with Infrastructure as Code best practices.
| Server Name | Description | Install |
|---|---|---|
| AWS IaC MCP Server | Complete Infrastructure as Code toolkit with CloudFormation documentation access, CDK best practices guidance, construct examples, security validation, and deployment troubleshooting | |
| AWS Cloud Control API MCP Server ⚠️ DEPRECATED | Direct AWS resource management with security scanning and best practices (Use AWS IaC MCP Server instead) |
Container Platforms
| Server Name | Description | Install |
|---|---|---|
| Amazon EKS MCP Server | Kubernetes cluster management and application deployment | |
| Amazon ECS MCP Server | Container orchestration and ECS application deployment | |
| Finch MCP Server | Local container building with ECR integration |
This README has been shortened. The full version is on GitHub. Read the original ↗