AWS MCP 服务器配置指南：为AI代理快速集成AWS工具与文档搜索

aws-mcp-setup by zxkane/aws-skills

136 周安装量

218 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/zxkane/aws-skills --skill aws-mcp-setup

AI/机器学习自动化云服务

🇨🇳中文介绍

AWS MCP 服务器配置指南

概述

本指南帮助您为 AI 代理配置 AWS MCP 工具。提供两种可选方案：

选项	要求	功能
完整 AWS MCP 服务器	Python 3.10+、uvx、AWS 凭证	执行 AWS API 调用 + 文档搜索
AWS 文档 MCP	无	仅文档搜索

步骤 1：检查现有配置

在配置之前，请使用以下任一方法检查 AWS MCP 工具是否已可用：

方法 A：检查可用工具（推荐）

在您代理的可用工具中查找以下工具名称模式：

mcp__aws-mcp__* 或 mcp__aws__* → 已配置完整 AWS MCP 服务器
mcp__*awsdocs*__aws___* → 已配置 AWS 文档 MCP

如何检查：运行命令列出所有活动的 MCP 服务器。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

方法 B：检查配置文件

代理工具使用分层配置（优先级：本地 → 项目 → 用户 → 企业）：

范围	文件位置	使用场景
本地	`.claude.json`（在项目中）	个人/实验性
项目	`.mcp.json`（项目根目录）	团队共享
用户	`~/.claude.json`	跨项目个人
企业	系统管理目录	组织范围

检查这些文件中是否包含带有 aws-mcp、aws 或 awsdocs 键的 mcpServers：

# 检查项目配置
cat .mcp.json 2>/dev/null | grep -E '"(aws-mcp|aws|awsdocs)"'

# 检查用户配置
cat ~/.claude.json 2>/dev/null | grep -E '"(aws-mcp|aws|awsdocs)"'

# 或使用 Claude CLI
claude mcp list

如果 AWS MCP 已配置，则无需进一步设置。

步骤 2：选择配置方法

运行以下命令以确定使用哪个选项：

# 检查 uvx（需要 Python 3.10+）
which uvx || echo "uvx not available"

# 检查有效的 AWS 凭证
aws sts get-caller-identity || echo "AWS credentials not configured"

选项 A：完整 AWS MCP 服务器（推荐）

使用场景：uvx 可用且 AWS 凭证有效

Python 3.10+ 及 uv 包管理器
已配置 AWS 凭证（通过配置文件、环境变量或 IAM 角色）

所需 IAM 权限：

{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Action": [
      "aws-mcp:InvokeMCP",
      "aws-mcp:CallReadOnlyTool",
      "aws-mcp:CallReadWriteTool"
    ],
    "Resource": "*"
  }]
}

配置（添加到您的 MCP 设置中）：

{
  "mcpServers": {
    "aws-mcp": {
      "command": "uvx",
      "args": [
        "mcp-proxy-for-aws@latest",
        "https://aws-mcp.us-east-1.api.aws/mcp",
        "--metadata", "AWS_REGION=us-west-2"
      ]
    }
  }
}

凭证配置选项：

AWS 配置文件（推荐用于开发）：

"args": [
  "mcp-proxy-for-aws@latest",
  "https://aws-mcp.us-east-1.api.aws/mcp",
  "--profile", "my-profile",
  "--metadata", "AWS_REGION=us-west-2"
]

环境变量：

"env": {
  "AWS_ACCESS_KEY_ID": "...",
  "AWS_SECRET_ACCESS_KEY": "...",
  "AWS_REGION": "us-west-2"
}

IAM 角色（用于 EC2/ECS/Lambda）：无需额外配置 - 使用实例凭证

--region <region>：覆盖 AWS 区域
--read-only：限制为只读工具
--log-level <level>：设置日志级别（debug、info、warning、error）

选项 B：AWS 文档 MCP 服务器（无需认证）

没有 Python/uvx 环境
没有 AWS 凭证
仅需文档搜索（无需 API 执行）

{
  "mcpServers": {
    "awsdocs": {
      "type": "http",
      "url": "https://knowledge-mcp.global.api.aws"
    }
  }
}

配置后，验证工具是否可用：

对于完整 AWS MCP：

查找工具：mcp__aws-mcp__aws___search_documentation、mcp__aws-mcp__aws___call_aws

对于文档 MCP：

查找工具：mcp__awsdocs__aws___search_documentation、mcp__awsdocs__aws___read_documentation

问题	原因	解决方案
`uvx: command not found`	uv 未安装	使用 `pip install uv` 安装或使用选项 B
`AccessDenied` 错误	缺少 IAM 权限	将 aws-mcp:* 权限添加到 IAM 策略
`InvalidSignatureException`	凭证问题	检查 `aws sts get-caller-identity`
工具未出现	MCP 未启动	配置更改后重启您的代理

2026 年 1 月 22 日

🇺🇸English

AWS MCP Server Configuration Guide

Overview

This guide helps you configure AWS MCP tools for AI agents. Two options are available:

Option	Requirements	Capabilities
Full AWS MCP Server	Python 3.10+, uvx, AWS credentials	Execute AWS API calls + documentation search
AWS Documentation MCP	None	Documentation search only

Step 1: Check Existing Configuration

Before configuring, check if AWS MCP tools are already available using either method:

Method A: Check Available Tools (Recommended)

Look for these tool name patterns in your agent's available tools:

mcp__aws-mcp__* or mcp__aws__* → Full AWS MCP Server configured
mcp__*awsdocs*__aws___* → AWS Documentation MCP configured

How to check : Run /mcp command to list all active MCP servers.

Method B: Check Configuration Files

Agent tools use hierarchical configuration (precedence: local → project → user → enterprise):

Scope	File Location	Use Case
Local	`.claude.json` (in project)	Personal/experimental
Project	`.mcp.json` (project root)	Team-shared
User	`~/.claude.json`	Cross-project personal
Enterprise	System managed directories	Organization-wide

Check these files for mcpServers containing aws-mcp, aws, or awsdocs keys:

# Check project config
cat .mcp.json 2>/dev/null | grep -E '"(aws-mcp|aws|awsdocs)"'

# Check user config
cat ~/.claude.json 2>/dev/null | grep -E '"(aws-mcp|aws|awsdocs)"'

# Or use Claude CLI
claude mcp list

If AWS MCP is already configured, no further setup needed.

Step 2: Choose Configuration Method

Automatic Detection

Run these commands to determine which option to use:

# Check for uvx (requires Python 3.10+)
which uvx || echo "uvx not available"

# Check for valid AWS credentials
aws sts get-caller-identity || echo "AWS credentials not configured"

Option A: Full AWS MCP Server (Recommended)

Use when : uvx available AND AWS credentials valid

Prerequisites :

Python 3.10+ with uv package manager
AWS credentials configured (via profile, environment variables, or IAM role)

Required IAM Permissions :

{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Action": [
      "aws-mcp:InvokeMCP",
      "aws-mcp:CallReadOnlyTool",
      "aws-mcp:CallReadWriteTool"
    ],
    "Resource": "*"
  }]
}

Configuration (add to your MCP settings):

{
  "mcpServers": {
    "aws-mcp": {
      "command": "uvx",
      "args": [
        "mcp-proxy-for-aws@latest",
        "https://aws-mcp.us-east-1.api.aws/mcp",
        "--metadata", "AWS_REGION=us-west-2"
      ]
    }
  }
}

Credential Configuration Options :

AWS Profile (recommended for development):

"args": [
  "mcp-proxy-for-aws@latest",
  "https://aws-mcp.us-east-1.api.aws/mcp",
  "--profile", "my-profile",
  "--metadata", "AWS_REGION=us-west-2"
]

Environment Variables :

"env": {
  "AWS_ACCESS_KEY_ID": "...",
  "AWS_SECRET_ACCESS_KEY": "...",
  "AWS_REGION": "us-west-2"
}

IAM Role (for EC2/ECS/Lambda): No additional config needed - uses instance credentials

Additional Options :

--region <region>: Override AWS region
--read-only: Restrict to read-only tools
--log-level <level>: Set logging level (debug, info, warning, error)

Reference : https://github.com/aws/mcp-proxy-for-aws

Option B: AWS Documentation MCP Server (No Auth)

Use when :

No Python/uvx environment
No AWS credentials
Only need documentation search (no API execution)

Configuration :

{
  "mcpServers": {
    "awsdocs": {
      "type": "http",
      "url": "https://knowledge-mcp.global.api.aws"
    }
  }
}

Step 3: Verification

After configuration, verify tools are available:

For Full AWS MCP :

Look for tools: mcp__aws-mcp__aws___search_documentation, mcp__aws-mcp__aws___call_aws

For Documentation MCP :

Look for tools: mcp__awsdocs__aws___search_documentation, mcp__awsdocs__aws___read_documentation

Troubleshooting

Issue	Cause	Solution
`uvx: command not found`	uv not installed	Install with `pip install uv` or use Option B
`AccessDenied` error	Missing IAM permissions	Add aws-mcp:* permissions to IAM policy
`InvalidSignatureException`	Credential issue	Check `aws sts get-caller-identity`
Tools not appearing	MCP not started	Restart your agent after config change

Weekly Installs

136

Repository

zxkane/aws-skills

GitHub Stars

218

First Seen

Jan 22, 2026

Security Audits

Gen Agent Trust HubPass SocketWarn SnykWarn

Installed on

opencode108

codex108

gemini-cli103

github-copilot102

claude-code102

cursor98

React 组合模式指南：Vercel 组件架构最佳实践，提升代码可维护性

115,300 周安装