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