alexei-led/aws-mcp-server

Give Claude access to all 200+ AWS services through the AWS CLI.
Demo
Demo
What It Does
This MCP server lets Claude run AWS CLI commands on your behalf. Instead of wrapping each AWS API individually, it wraps the CLI itself—giving Claude complete AWS access through just two tools:
| Tool | Purpose |
| ------------------ | ----------------------------------------------------------------- |
| aws_cli_help | Get documentation for any AWS command |
| aws_cli_pipeline | Execute AWS CLI commands with optional pipes (jq, grep, etc.) |
Claude learns commands on-demand using --help, then executes them. Your IAM policy controls what it can actually do.
What's New
- **Streamable HTTP transport** — New streamable-http transport for web-based MCP clients, replacing the deprecated sse transport (#33)
- **Input validation error handling** — Validation errors now return proper MCP tool errors (isError: true) instead of regular results (#34)
- **Server description** — Server advertises its purpose to MCP clients via the instructions field (#35)
- **Server icons** — Server provides icon metadata for MCP client display (#36)
- **Graceful shutdown** — Server disconnects cleanly when the MCP client disconnects (#16)
Quick Start
Prerequisites
- AWS CLI installed
- AWS credentials configured (see AWS Credentials)
- uv installed (for uvx)
Claude Code
Add to your MCP settings (Cmd+Shift+P → "Claude: Open MCP Config"):
Claude Desktop
Add to your Claude Desktop config file:
**macOS**: ~/Library/Application Support/Claude/claude_desktop_config.json
**Windows**: %APPDATA%\Claude\claude_desktop_config.json
Docker (More Secure)
Docker provides stronger isolation by running commands in a container:
> **Note**: Replace ~/.aws with the full path on Windows (e.g., C:\Users\YOU\.aws).
Docker with Streamable HTTP Transport
For web-based MCP clients, use the streamable-http transport:
The server will be available at http://localhost:8000/mcp.
> **Note**: The sse transport is deprecated. Use streamable-http instead.
AWS Credentials
The server uses the standard AWS credential chain. Your credentials are discovered automatically from:
1. **Environment variables**: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY
2. **Credentials file**: ~/.aws/credentials
3. **Config file**: ~/.aws/config (for profiles and region)
4. **IAM role**: When running on EC2, ECS, or Lambda
To use a specific profile:
Configuration
AWS Settings
| Environment Variable | Description | Default |
| ----------------------------- | ---------------------------------------------- | -------------------- |
| AWS_PROFILE | AWS profile to use | default |
| AWS_REGION | AWS region (also accepts AWS_DEFAULT_REGION) | us-east-1 |
| AWS_CONFIG_FILE | Custom path to AWS config file | ~/.aws/config |
| AWS_SHARED_CREDENTIALS_FILE | Custom path to credentials file | ~/.aws/credentials |
Server Settings