Multi-Account MCP #1994
Replies: 3 comments
|
I'm curious if the multi-profile support would help your use case or is there some other setup that would be a better fit? |
|
@mrpackethead @arnewouters We are also facing the same issue, How can we utilize aws api mcp server with multiple aws accounts. Are you able achieve this? |
|
This is affecting me too. I work with 150~ profiles and the current "Just run an MCP instance for each account you want" isn't going to work for me. My AI tooling knowing which profile goes to which account (via ~/.aws/config) and thus being able to configure the MCP on-the-fly would be a significant improvement. |
Uh oh!
There was an error while loading. Please reload this page.
I've been exploring the AWS API MCP Server codebase for multi-account use cases and noticed something interesting:
The internal call_aws_helper() function accepts a credentials parameter and the entire downstream code (in driver.py, services.py, etc.) properly handles custom credentials. However, the public call_aws MCP tool always passes credentials=None.
Was this intentional for the single-user use case, or is there a security/design reason not to expose it?
Are there any concerns or considerations we should be aware of when implementing multi-account support?
Use case:
We're looking to extend this MCP server to support AWS Organizations with multiple accounts, where users could execute commands like:
The server would internally call sts:AssumeRole to get temporary credentials for the target account and pass them to call_aws_helper().
Since the credential infrastructure is already built, this seems like a natural extension. Would love to hear your thoughts!
Thanks for the great work on this project!
All reactions