The AWS MCP Server now supports cross-account and cross-role access

AWS has enhanced its Model Context Protocol (MCP) Server with cross-account and cross-role access capabilities, allowing developers to work with AI coding agents across multiple AWS accounts and IAM roles without interrupting their sessions. The update eliminates the previous workflow friction where developers had to stop their AI coding sessions, update local AWS credentials, and restart the MCP server every time they needed to switch between accounts or roles. The new functionality enables AI agents using the AWS MCP Server to specify different AWS profiles on each command, creating seamless transitions between environments. This allows developers to perform tasks like querying CloudWatch logs across production and staging accounts or updating Lambda configurations in one account while adjusting S3 bucket policies in another, all within a single conversation session. Each request explicitly specifies which profile to use, reducing the risk of commands being executed against the wrong account. The enhanced AWS MCP Server is currently available in the US East (N. Virginia) and Europe (Frankfurt) regions as part of the Agent Toolkit for AWS. The feature specifically targets developers using AI coding agents like Kiro, Claude Code, or Codex who work in multi-account AWS environments.