Impossible to use 2 distinct profiles in a single Kiro CLI session.

[psantus]

Describe the bug (Security related? please follow https://github.com/aws/mcp-proxy-for-aws/security/policy to report them to AWS Security directly.)

I set up AWS_PROFILE=profile1

then I launch Kiro CLI, set up with

"mcpServers": {
    "aws-mcp": {
      "command": "uvx",
      "transport": "stdio", 
      "timeout": 100000,
      "args": [
        "mcp-proxy-for-aws@latest",
        "https://aws-mcp.us-east-1.api.aws/mcp"
      ]
    }
}

I ask "get caller identity".

KiroCLI runs

Running tool aws___call_aws with the param (from mcp server: aws-mcp)
 ⋮  {
 ⋮    "cli_command": "aws sts get-caller-identity"
 ⋮  }

then I say "do the same with AWS_PROFILE=profile2

KrioCLI runs

Running tool aws___call_aws with the param (from mcp server: aws-mcp)
 ⋮  {
 ⋮    "cli_command": "aws sts get-caller-identity --profile profile2"
 ⋮  }

but the result returned is exactly the same (though profiles are using different roles in different accounts): the MCP sever persists in using the session that was set up with Kiro CLI started.

Expected Behavior

LLM should be able to use multiple CLI profiles.

Current Behavior

The profile used when Kiri CLI launches is the only one that get all the queries.

Reproduction Steps

See above.

Possible Solution

No response

Additional Information/Context

No response

Operating System

MacOS

Release Version

latest (this server, Kiro-cli and AWS CLI all in latest version)

Other information

No response

Search verification

• I have searched existing issues and verified this is not a duplicate

Related issues

[wzxxing]

Hi, @psantus, when you use the remote aws mcp server, there is not a way to use the --profile parameter in the call_aws tool. You can only use --profile in your MCP server config.

The remote mcp only support using the credentials of the profile specified in the MCP server config.

[psantus]

Yes, that's why the proxy should be able to dynamically switch (since the remote server can't).
Multi-account is a reality today. People won't want to have 12 configs for the same MCP server..

[jsamuel1]

It would be awesome if the mcp added a aws_switch_profile tool. This would enable this usecase nicely.

[jonesaws]

Agree this is important to add. Agents should be able to dynamically set the account and region to preserve the context etc between discrete calls to different accounts/regions.

[benjstoll]

Hello!

I to wanted to solve this problem and ended up creating a tool called switch_profile for the MCP that accomplishes exactly this. My agents are now able to authenticate across dozens of AWS accounts autonomously. I even created a flag called --allowed-profiles which lets me whitelist profiles they are allowed to use so the more critical accounts can only assume read-only profiles. If the maintainers are interested I can open a PR and they can check out what ive created, I think it would be a great addition to this project!

[anasstahr]

Hi, thank you for opening this issue!

We would love to have this feature in the proxy as many others do as well :). This is being developed in: #205, thank you for the contribution there ben!

[rshevchuk-git]

Multi profile support has been added in: #266. Release will happen soon