Creativity · MCP — server

MCP AWS Server

AWS ships multiple official MCP servers (under the awslabs GitHub org) rather than a single monolith. There are dedicated servers for CloudWatch logs, S3, CDK, Bedrock Knowledge Bases, cost explorer, and a general 'aws-api' server that wraps the SDK. You typically install the ones you need individually in Claude Desktop and scope each to a least-privilege IAM role. This page is the orientation hub for the AWS MCP suite.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: Python / TypeScript
Transports: stdio, http, sse

Capabilities

Servers for CloudWatch Logs, S3, DynamoDB, Lambda, CDK, Bedrock KB, Cost Explorer
Resources: AWS account/region metadata; per-service entity URIs
Auth: AWS_PROFILE, IAM role, or short-lived STS credentials

Install

uvx awslabs.core-mcp-server

Configuration

{
  "mcpServers": {
    "aws-core": {
      "command": "uvx",
      "args": ["awslabs.core-mcp-server"],
      "env": {
        "AWS_PROFILE": "mcp-dev",
        "AWS_REGION": "us-east-1"
      }
    }
  }
}

Frequently asked questions

Is there a single AWS MCP server?

No. AWS splits functionality across many focused servers (S3, CloudWatch, Bedrock KB, CDK, cost explorer, etc.), all hosted under github.com/awslabs. Pick the ones relevant to your task and install them individually.

How should I handle IAM?

Create a dedicated role per MCP server with only the IAM actions that server needs (e.g. logs:StartQuery, logs:GetQueryResults for the CloudWatch server). Rotate credentials via SSO or STS rather than long-lived access keys.

Can Bedrock agents talk to these servers?

Yes — Amazon Bedrock supports MCP servers as tool providers, so you can reuse the same awslabs servers inside Bedrock agents and the Amazon Q Developer CLI.

Sources

AWS Labs MCP servers — accessed 2026-04-20
Model Context Protocol — accessed 2026-04-20