AWS MCP Credential Proxy

1. Reads the AWS_CONTAINER_AUTHORIZATION_TOKEN and AWS_CONTAINER_CREDENTIALS_FULL_URI environment variables passed from running AWS Vault in server mode.

2. Exchanges those for traditional STS credentials (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_SESSION_TOKEN).

3. Passes those credentials down the line to the next command that only understands traditional STS credentials.

Install

go install github.com/northwood-labs/aws-mcp-credential-proxy@latest

Example

aws-vault exec --duration=15m --ecs-server --region=us-east-2 --lazy {PROFILE} -- \
  aws-mcp-credential-proxy -- \
    docker mcp gateway run \
      --servers=aws-api \
      --servers=aws-core-mcp-server \
      --servers=aws-documentation \
      --servers=aws-terraform \
      --tools=call_aws \
      --tools=fetch_agentcore_doc \
      --tools=manage_agentcore_gateway \
      --tools=manage_agentcore_memory \
      --tools=manage_agentcore_runtime \
      --tools=mcp-add \
      --tools=mcp-create-profile \
      --tools=mcp-find \
      --tools=prompt_understanding \
      --tools=recommend \
      --tools=search_agentcore_docs \
      --tools=suggest_aws_commands \
;

Helps address the fact that the Docker MCP Toolkit version of these AWS MCP servers don't (yet) support AWS Container Credentials.

Refreshes

This will automatically refresh the credentials from the credential server ~30 seconds before expiration.

• If the downstream command reads environment variables on-demand, they should pick up the latest changes.
• If the downstream command reads environment variables on-load, they may not pick up until the process halts and restarts.