Skip to content
cccskills
FreePublished on GitHub

aws-mcp-setup

Configure 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 (with uvx + credentials) and lightweight Documentation MCP (no auth required).

The English summary is being prepared. Showing the original description.

Works withAWS
See how to install

Files included (1)

  • SKILL.md5.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

AWS MCP Server Configuration Guide

Overview

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

OptionRequirementsCapabilities
Full AWS MCP ServerPython 3.10+, uvx, AWS credentialsExecute AWS API calls + documentation search
AWS Documentation MCPNoneDocumentation 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):

ScopeFile LocationUse Case
Local.claude.json (in project)Personal/experimental
Project.mcp.json (project root)Team-shared
User~/.claude.jsonCross-project personal
EnterpriseSystem managed directoriesOrganization-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:

  1. 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"
    ]
    
  2. Environment Variables:

    "env": {
      "AWS_ACCESS_KEY_ID": "...",
      "AWS_SECRET_ACCESS_KEY": "...",
      "AWS_REGION": "us-west-2"
    }
    
  3. 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

IssueCauseSolution
uvx: command not founduv not installedInstall with pip install uv or use Option B
AccessDenied errorMissing IAM permissionsAdd aws-mcp:* permissions to IAM policy
InvalidSignatureExceptionCredential issueCheck aws sts get-caller-identity
Tools not appearingMCP not startedRestart your agent after config change

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

AWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale. Use when working with any AgentCore service including Gateway, Runtime, Memory, Identity, Code Interpreter, Browser, Observability, Agent Registry, or Evaluations. Covers agent deployment, MCP tool integration, credential management, agent discovery, governance workflows, and automated quality assessment. Essential when user mentions AgentCore, agent runtime, agent registry, agent evaluation, MCP gateway, deploy agent, register MCP server, discover agents, evaluate agent quality, agent credentials, or wants to build, deploy, catalog, or monitor AI agents on AWS.

The English summary is being prepared. Showing the original description.

zxkane/aws-skills370Updated Jun 15, 2026

AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python. Use when creating CDK stacks, defining CDK constructs, implementing infrastructure as code, or when the user mentions CDK, CloudFormation, IaC, cdk synth, cdk deploy, or wants to define AWS infrastructure programmatically. Covers CDK app structure, construct patterns, stack composition, and deployment workflows.

The English summary is being prepared. Showing the original description.

zxkane/aws-skills370Updated Jun 15, 2026

AWS cost optimization, monitoring, and operational excellence expert. Use when analyzing AWS bills, estimating costs, setting up CloudWatch alarms, querying logs, auditing CloudTrail activity, or assessing security posture. Essential when user mentions AWS costs, spending, billing, budget, pricing, CloudWatch, observability, monitoring, alerting, CloudTrail, audit, or wants to optimize AWS infrastructure costs and operational efficiency.

The English summary is being prepared. Showing the original description.

zxkane/aws-skills370Updated Jun 15, 2026

AWS serverless and event-driven architecture expert based on Well-Architected Framework. Use when building serverless APIs, Lambda functions, REST APIs, microservices, or async workflows. Covers Lambda with TypeScript/Python, API Gateway (REST/HTTP), DynamoDB, Step Functions, EventBridge, SQS, SNS, and serverless patterns. Essential when user mentions serverless, Lambda, API Gateway, event-driven, async processing, queues, pub/sub, or wants to build scalable serverless applications with AWS best practices.

The English summary is being prepared. Showing the original description.

zxkane/aws-skills370Updated Jun 15, 2026

SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework. Use when writing or editing sst.config.ts, building infra/ modules (sst.aws.Function/Bucket/Dynamo/Cron/Service/Router, sst.Secret, sst.Linkable, raw aws.* Pulumi resources), wiring resource links, scoping IAM, or running sst deploy/dev/diff/remove. Essential when the user mentions SST, sst.config.ts, $config, $transform, $interpolate, sst.aws.*, sst.Secret, Pulumi/Ion, "sst deploy", a failed SST deploy (ConflictException on a resource-type change, "Identifier '__filename' has already been declared", MalformedPolicyDocument on an Output<T>), or wants to scaffold/troubleshoot AWS infrastructure with SST. Also use when a request to "deploy my AWS stack" or "add a Lambda/bucket/table" is made in a repo that already contains an sst.config.ts (using $config) or an sst dependency. Do NOT use when the task is primarily AWS CDK, Terraform, raw CloudFormation, or SAM with no SST present — those have their own tooling.

The English summary is being prepared. Showing the original description.

zxkane/aws-skills370Updated Jun 15, 2026

See all skills by zxkane

Report a problem with this skill