aws-api-mcp-server: For high-level API commands, is the profile specified by AWS_API_MCP_PROFILE_NAME not being used? #886
-
What happened
What I confirmed
mcp/src/aws-api-mcp-server/awslabs/aws_api_mcp_server/server.py Lines 220 to 236 in c486aaf
What I'd like to ask
Thank you for your consideration. |
Beta Was this translation helpful? Give feedback.
Answered by
PCManticore
Jul 22, 2025
Replies: 1 comment 1 reply
-
|
Hi @naoki85 Thank you for the report. This was actually a bug we just fixed yesterday. Our 0.1.3 release should address this issue. Do give it a try and let us know if you still encounter the issue. |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
PCManticore
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @naoki85
Thank you for the report. This was actually a bug we just fixed yesterday. Our 0.1.3 release should address this issue.
AWS_API_MCP_PROFILE_NAMEis now used appropriately for both low level commands and high level commands (what we callCLI customizations).Do give it a try and let us know if you still encounter the issue.