AWS MCP Server
Let Claude Code or Cursor call AWS APIs, read official docs, and follow SOP workflows without leaving the agent session.
Overview
AWS MCP Server is a MCP server for the Build phase that proxies your agent to AWS’s managed MCP endpoint for docs, API calls, and SOP workflows.
What is this MCP server?
- Stdio MCP proxy via PyPI `mcp-proxy-for-aws` (uvx) pointing at `https://aws-mcp.us-east-1.api.aws/mcp`
- Combines AWS documentation retrieval, authenticated API calls, and SOP-style operational workflows in one server
- Official AWS MCP catalog entry (preview 1.0.0) with documented install at docs.aws.amazon.com/aws-mcp
- No custom tool list in the snippet—capabilities are delivered through the managed AWS MCP endpoint behind the proxy
- Registry package version 1.1.4 via PyPI identifier mcp-proxy-for-aws
- Server schema version 1.0.0-preview.0
- Default MCP endpoint positional argument: https://aws-mcp.us-east-1.api.aws/mcp
What problem does it solve?
Agents cannot safely or consistently act on your real AWS estate without a vetted MCP bridge and your existing AWS credentials.
Who is it for?
Solo builders and small teams already on AWS who want agent-driven deploy, debug, and doc lookup with official AWS MCP rather than brittle shell one-liners.
Skip if: Builders with no AWS account, those who need only static markdown AWS cheatsheets, or environments that block outbound calls to `aws-mcp.us-east-1.api.aws`.
What do I get? / Deliverables
After you register the uvx stdio proxy, your agent can query AWS guidance and execute approved cloud actions from the same thread where you write infrastructure code.
- Registered stdio MCP server pointing at the official AWS MCP endpoint
- Agent-accessible AWS documentation and API workflow surface per AWS MCP product behavior
- Repeatable SOP-oriented cloud operations from the agent chat
Recommended MCP Servers
Journey fit
Solo builders wire cloud backends during the build phase; this MCP is the bridge between the coding agent and live AWS accounts. Integrations is the right shelf because the server is a transport proxy (uvx stdio) to the hosted AWS MCP endpoint, not a standalone app feature.
How it compares
Managed AWS MCP proxy over stdio—not a generic “run any boto3 script” skill or a third-party AWS console scraper.
Common Questions / FAQ
Who is AWS MCP Server for?
Indie and solo developers using Claude Code, Cursor, or Codex who deploy and operate on AWS and want protocol-native cloud access.
When should I use AWS MCP Server?
Use it when you are building or fixing AWS-backed apps and want the agent to read AWS docs, call APIs, or follow SOP workflows instead of manual console steps.
How do I add AWS MCP Server to my agent?
Add a stdio MCP server entry that runs `uvx mcp-proxy-for-aws` with the positional argument `https://aws-mcp.us-east-1.api.aws/mcp`, then configure AWS credentials the same way you would for the CLI.