aws-api-mcp-server: migration to AWS MCP Server

Summary

The AWS API MCP Server (awslabs.aws-api-mcp-server) is entering end of development. Beginning July 15, 2026, it will no longer receive regular updates or support for new AWS services, features and APIs released after that date. It will remain available with security and critical fixes, and will be removed on July 15, 2027.

We recommend migrating to the AWS MCP Server, which provides the same access to AWS APIs and is fully managed and supported.

Why this is happening

The AWS API MCP Server depends on AWS CLI v1, which enters maintenance mode on July 15, 2026. After that date, AWS CLI v1 will no longer receive support for new AWS services, features, or API updates — and neither will the AWS API MCP Server.

How to migrate

Update your MCP configuration to point at the AWS MCP Server. For step-by-step instructions, see the migration guide.

You can also install the AWS MCP Server through the Agent Toolkit for AWS.

What does the AWS MCP Server offer?

The AWS MCP Server is fully managed and supported, stays current with new AWS services and APIs, and adds:

• Up-to-date AWS documentation retrieval at query time
• Sandboxed script execution for multi-step tasks
• Amazon CloudWatch metrics for monitoring agent activity
• AWS CloudTrail audit trail for every API call
• OAuth 2.0 authorization

To learn more, see the launch announcement.

Timeline

Date	What happens
July 15, 2026	AWS API MCP Server enters end of development. No new features or service coverage.
July 15, 2027	AWS API MCP Server is removed.

Feedback

If you have questions, run into issues during migration, or want to share feedback, please comment on this issue.