AWS MCP Server

Installation path

For Cosmos cloud sessions, add AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY as string secrets at app.augmentcode.com/app/secrets and set them as env vars. For local CLI use, configure credentials with aws login, aws configure sso, or aws configure. Then choose Add Server, select Local MCP, install uv, use uvx as the command, and pass mcp-proxy-for-aws@latest, https://aws-mcp.us-east-1.api.aws/mcp, --metadata, and AWS_REGION=<region> as arguments.

Setup steps

1. 01

   Install uv

   uv ships uvx: install with brew install uv or pipx install uv.

2. 02

   Set up AWS credentials

   For Cosmos cloud sessions: go to app.augmentcode.com/app/secrets and add AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY as string secrets (and AWS_SESSION_TOKEN if using temporary credentials). You will reference these as env vars in the next steps. For local CLI-only use: run aws configure sso, aws login, or aws configure instead: the server will pick up credentials from ~/.aws/credentials automatically.

3. 03

   Open Add Server

   Configuration → MCP Registry → Add Server in Cosmos.

4. 04

   Pick the Local MCP tab

5. 05

   Set the command

   Command

   uvx
6. 06

   Add the arguments

   Args

   mcp-proxy-for-aws@latest https://aws-mcp.us-east-1.api.aws/mcp --metadata AWS_REGION=<region>
7. 07

   Set environment variables (Cosmos cloud only)

   If using Cosmos cloud sessions, set these env vars to the secret values you created. The server will use them for SigV4 signing instead of the local credentials file.

   AWS_ACCESS_KEY_ID

   AWS_ACCESS_KEY_ID=your-access-key-id

   AWS_SECRET_ACCESS_KEY

   AWS_SECRET_ACCESS_KEY=your-secret-access-key

   AWS_SESSION_TOKEN

   AWS_SESSION_TOKEN=your-session-token
8. 08

   Click Add, then enable

   Toggle on Cosmos Agent or CLI.

Local command

Suggested name: aws-mcp

AWS MCP Server is in preview and uses SigV4 through MCP Proxy for AWS. For Cosmos cloud sessions, store AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY as string secrets at app.augmentcode.com/app/secrets and set them as env vars: the VM cannot access your local ~/.aws/credentials file. For local CLI use, credentials from aws configure or aws login are picked up automatically.

Authentication

AWS credentials via SigV4. For Cosmos cloud sessions, store AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY as string secrets at app.augmentcode.com/app/secrets and set them as env vars. For local CLI only, run aws login, aws configure sso, or aws configure: credentials are read from ~/.aws/credentials automatically.