$npx -y skills add aws-samples/sample-agent-skills-for-builders --skill aws-mcp-setupConfigure AWS MCP servers for documentation search and API access. Use when setting up AWS MCP, configuring AWS documentation tools, troubleshooting MCP connectivity, or when user mentions aws-mcp, awsdocs, uvx setup, or MCP server configuration. Covers both Full AWS MCP Server (
| 1 | # AWS MCP Server Configuration Guide |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | This guide helps you configure AWS MCP tools for AI agents. Two options are available: |
| 6 | |
| 7 | | Option | Requirements | Capabilities | |
| 8 | |--------|--------------|--------------| |
| 9 | | **Full AWS MCP Server** | Python 3.10+, uvx, AWS credentials | Execute AWS API calls + documentation search | |
| 10 | | **AWS Documentation MCP** | None | Documentation search only | |
| 11 | |
| 12 | ## Step 1: Check Existing Configuration |
| 13 | |
| 14 | Before configuring, check if AWS MCP tools are already available using either method: |
| 15 | |
| 16 | ### Method A: Check Available Tools (Recommended) |
| 17 | |
| 18 | Look for these tool name patterns in your agent's available tools: |
| 19 | - `mcp__aws-mcp__*` or `mcp__aws__*` → Full AWS MCP Server configured |
| 20 | - `mcp__*awsdocs*__aws___*` → AWS Documentation MCP configured |
| 21 | |
| 22 | **How to check**: Run `/mcp` command to list all active MCP servers. |
| 23 | |
| 24 | ### Method B: Check Configuration Files |
| 25 | |
| 26 | Agent tools use hierarchical configuration (precedence: local → project → user → enterprise): |
| 27 | |
| 28 | | Scope | File Location | Use Case | |
| 29 | |-------|---------------|----------| |
| 30 | | Local | `.claude.json` (in project) | Personal/experimental | |
| 31 | | Project | `.mcp.json` (project root) | Team-shared | |
| 32 | | User | `~/.claude.json` | Cross-project personal | |
| 33 | | Enterprise | System managed directories | Organization-wide | |
| 34 | |
| 35 | Check these files for `mcpServers` containing `aws-mcp`, `aws`, or `awsdocs` keys: |
| 36 | |
| 37 | ```bash |
| 38 | # Check project config |
| 39 | cat .mcp.json 2>/dev/null | grep -E '"(aws-mcp|aws|awsdocs)"' |
| 40 | |
| 41 | # Check user config |
| 42 | cat ~/.claude.json 2>/dev/null | grep -E '"(aws-mcp|aws|awsdocs)"' |
| 43 | |
| 44 | # Or use Claude CLI |
| 45 | claude mcp list |
| 46 | ``` |
| 47 | |
| 48 | If AWS MCP is already configured, no further setup needed. |
| 49 | |
| 50 | ## Step 2: Choose Configuration Method |
| 51 | |
| 52 | ### Automatic Detection |
| 53 | |
| 54 | Run these commands to determine which option to use: |
| 55 | |
| 56 | ```bash |
| 57 | # Check for uvx (requires Python 3.10+) |
| 58 | which uvx || echo "uvx not available" |
| 59 | |
| 60 | # Check for valid AWS credentials |
| 61 | aws sts get-caller-identity || echo "AWS credentials not configured" |
| 62 | ``` |
| 63 | |
| 64 | ### Option A: Full AWS MCP Server (Recommended) |
| 65 | |
| 66 | **Use when**: uvx available AND AWS credentials valid |
| 67 | |
| 68 | **Prerequisites**: |
| 69 | - Python 3.10+ with `uv` package manager |
| 70 | - AWS credentials configured (via profile, environment variables, or IAM role) |
| 71 | |
| 72 | **Required IAM Permissions**: |
| 73 | ```json |
| 74 | { |
| 75 | "Version": "2012-10-17", |
| 76 | "Statement": [{ |
| 77 | "Effect": "Allow", |
| 78 | "Action": [ |
| 79 | "aws-mcp:InvokeMCP", |
| 80 | "aws-mcp:CallReadOnlyTool", |
| 81 | "aws-mcp:CallReadWriteTool" |
| 82 | ], |
| 83 | "Resource": "*" |
| 84 | }] |
| 85 | } |
| 86 | ``` |
| 87 | |
| 88 | **Configuration** (add to your MCP settings): |
| 89 | ```json |
| 90 | { |
| 91 | "mcpServers": { |
| 92 | "aws-mcp": { |
| 93 | "command": "uvx", |
| 94 | "args": [ |
| 95 | "mcp-proxy-for-aws@latest", |
| 96 | "https://aws-mcp.us-east-1.api.aws/mcp", |
| 97 | "--metadata", "AWS_REGION=us-west-2" |
| 98 | ] |
| 99 | } |
| 100 | } |
| 101 | } |
| 102 | ``` |
| 103 | |
| 104 | **Credential Configuration Options**: |
| 105 | |
| 106 | 1. **AWS Profile** (recommended for development): |
| 107 | ```json |
| 108 | "args": [ |
| 109 | "mcp-proxy-for-aws@latest", |
| 110 | "https://aws-mcp.us-east-1.api.aws/mcp", |
| 111 | "--profile", "my-profile", |
| 112 | "--metadata", "AWS_REGION=us-west-2" |
| 113 | ] |
| 114 | ``` |
| 115 | |
| 116 | 2. **Environment Variables**: |
| 117 | ```json |
| 118 | "env": { |
| 119 | "AWS_ACCESS_KEY_ID": "...", |
| 120 | "AWS_SECRET_ACCESS_KEY": "...", |
| 121 | "AWS_REGION": "us-west-2" |
| 122 | } |
| 123 | ``` |
| 124 | |
| 125 | 3. **IAM Role** (for EC2/ECS/Lambda): No additional config needed - uses instance credentials |
| 126 | |
| 127 | **Additional Options**: |
| 128 | - `--region <region>`: Override AWS region |
| 129 | - `--read-only`: Restrict to read-only tools |
| 130 | - `--log-level <level>`: Set logging level (debug, info, warning, error) |
| 131 | |
| 132 | **Reference**: https://github.com/aws/mcp-proxy-for-aws |
| 133 | |
| 134 | ### Option B: AWS Documentation MCP Server (No Auth) |
| 135 | |
| 136 | **Use when**: |
| 137 | - No Python/uvx environment |
| 138 | - No AWS credentials |
| 139 | - Only need documentation search (no API execution) |
| 140 | |
| 141 | **Configuration**: |
| 142 | ```json |
| 143 | { |
| 144 | "mcpServers": { |
| 145 | "awsdocs": { |
| 146 | "type": "http", |
| 147 | "url": "https://knowledge-mcp.global.api.aws" |
| 148 | } |
| 149 | } |
| 150 | } |
| 151 | ``` |
| 152 | |
| 153 | ## Step 3: Verification |
| 154 | |
| 155 | After configuration, verify tools are available: |
| 156 | |
| 157 | **For Full AWS MCP**: |
| 158 | - Look for tools: `mcp__aws-mcp__aws___search_documentation`, `mcp__aws-mcp__aws___call_aws` |
| 159 | |
| 160 | **For Documentation MCP**: |
| 161 | - Look for tools: `mcp__awsdocs__aws___search_documentation`, `mcp__awsdocs__aws___read_documentation` |
| 162 | |
| 163 | ## Troubleshooting |
| 164 | |
| 165 | | Issue | Cause | Solution | |
| 166 | |-------|-------|----------| |
| 167 | | `uvx: command not found` | uv not installed | Install with `pip install uv` or use Option B | |
| 168 | | `AccessDenied` error | Missing IAM permissions | Add aws-mcp:* permissions to IA |