aws / aws/amazon-q-developer-cli

[RFC] Replace use_aws with AWS API MCP

Open
#2,407 0 comments 6 reactions 0 assignees View on GitHub
enhancement
Dominant language
Rust
Stars
2k
Forks
439
PR merge metrics
No merged PRs in 30d

Description

## Summary
This RFC proposes replacing the current `use_aws` functionality with AWS API MCP server that launched at NY Summit [ [launch blog post](https://aws.amazon.com/about-aws/whats-new/2025/07/aws-api-mcp-server-available/)]

## Motivation
Current `use_aws` implementation has a few limitations:
- Manual updates needed for new AWS services, as it relies on the parametric knowledge of foundational models.
- `use_aws` relies on AWS CLI being available as well as running in a shell.

The AWS API MCP Server addresses these limitations by:
1. Allowing MCP clients (like our CLI) to dynamically discover and interact with supported AWS APIs.
2. Enabling direct API calls without relying on AWS CLI or shell environments.
3. Providing secure access control through AWS Identity and Access Management (IAM) credentials and pre-configured API permissions.
4. Ensuring that foundation models can only access or perform authorized actions on permitted AWS APIs [e.g. read-only mode]

## Next Steps
1. Seek approval for this RFC from Q CLI stakeholders
2. Start integrating AWS API MCP :)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.