AWS MCP Server

tl;dr: Anthropic never shipped a general-purpose AWS MCP. Their archived modelcontextprotocol/servers-archived only has the AWS Knowledge Base Retrieval server, which is now also deprecated — AWS Labs’ open-source awslabs/mcp (9.7k stars, Apache-2.0) replaced it, and AWS now also runs a managed remote AWS MCP at https://aws-mcp.us-east-1.api.aws/mcp (preview) with IAM-scoped permissions, validated API calls, and CloudTrail audit.

Two ways to use AWS with MCP

1. Managed remote MCP (recommended for production agents)

AWS runs a hosted MCP at https://aws-mcp.us-east-1.api.aws/mcp. Access is through mcp-proxy-for-aws, which forwards local stdio to the managed endpoint. It uses your IAM identity, never your long-lived keys, and logs every call to CloudTrail. Region: us-east-1 at time of writing.

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

Docs: docs.aws.amazon.com/aws-mcp. This server is “in preview” per the AWS announcement.

2. AWS Labs’ open-source suite (stdIO only)

The awslabs/mcp repo holds ~30 specialized Python MCP servers, all uvx/awslabs.<name>@latest. AWS now describes the Agent Toolkit for AWS as the successor with IAM condition keys, CloudTrail visibility, and evaluated skills. The MCP servers remain supported.

Common picks (with install commands):

Set AWS_PROFILE and AWS_REGION in env, or use AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY for explicit credentials. --allow-write is required for mutating tools.

What you set in env

Common to most awslabs.* servers:

• AWS_PROFILE — named profile from ~/.aws/credentials
• AWS_REGION — defaults to us-east-1 if omitted
• FASTMCP_LOG_LEVEL — ERROR for production, INFO for debugging
• Per-server: --allow-write / --allow-sensitive-data-access flags unlock mutations

Gotchas

• awslabs.* servers are stdio only — there is no streamable HTTP transport in the open-source suite.
• On 2025-05-26, SSE support was removed from all servers in their latest major versions; this aligns with the MCP spec’s backward-compatibility rules.
• The old Anthropic AWS Knowledge Base Retrieval server (@modelcontextprotocol/server-aws-kb-retrieval) is fully archived. The new awslabs.bedrock-kb-retrieval-mcp-server is the replacement if you self-host.

Related

• Docker MCP — for local containers
• Supabase MCP — managed Postgres
• MCP Servers Explained