A suite of specialized MCP servers that provide AI applications with access to AWS documentation, contextual guidance, and best practices.
Open source MCP servers for AWS is a suite of specialized servers that implement the Model Context Protocol to provide AI applications with real-time access to AWS documentation, contextual guidance, and best practices. It solves the problem of foundation models lacking up-to-date knowledge of AWS services by bridging this gap through standardized client-server architecture.
Cloud developers, DevOps engineers, and AI application builders who use AI coding assistants (like Cursor, Kiro, Windsurf) or chatbots and need accurate, current AWS information and workflow automation integrated into their tools.
Developers choose this project because it provides a standardized, open-source way to enhance AI assistants with the latest AWS knowledge, reducing hallucinations, improving output quality, and automating complex cloud workflows with security and best practices built-in.
Official MCP Servers for AWS
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The suite includes servers for documentation, IaC, containers, serverless, AI/ML, and databases, as shown in the categorized installation tables, providing comprehensive access to AWS capabilities.
Servers like AWS Knowledge MCP Server fetch the latest AWS docs, API references, and What's New posts, ensuring AI assistants have current information to reduce hallucinations and improve accuracy.
Built on the open Model Context Protocol, it seamlessly integrates with various AI clients such as Kiro, Cursor, and VS Code, promoting interoperability and ease of adoption.
Features like IAM-based permissions, syntactical validation, and CloudTrail logging in the AWS MCP Server enhance security and compliance for AWS operations, as detailed in the README.
Each server requires specific environment variables and setup (e.g., AWS_PROFILE, region, function prefixes), which can be tedious to manage across multiple servers, as evidenced by the lengthy installation examples.
The README admits that Server Sent Events support was removed, and only stdio is currently supported, with Streamable HTTP still in development, restricting deployment flexibility and potentially causing migration issues.
All servers are AWS-specific and do not support other cloud providers, making them unsuitable for hybrid or multi-cloud strategies and limiting portability.
Several servers (e.g., AWS Cloud Control API MCP Server, AWS CDK MCP Server) are marked as deprecated, indicating potential breaking changes and the need for migration efforts, as noted in the README.