AWS MCP Server logo

AWS MCP Server

Bridges MCP clients to IAM-authenticated AWS MCP endpoints with SigV4 signing and dynamic tool discovery.

Install AWS MCP Server

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "aws-mcp-server-2": {
      "command": "uvx",
      "args": [
        "mcp-proxy-for-aws-cli@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

AWS MCP Server bridges MCP clients and MCP servers hosted on AWS, signing requests with AWS IAM credentials through SigV4. It can run as a command-line proxy or be imported as a Python library for agent frameworks such as LangChain, LlamaIndex, and Strands Agents. Use the proxy when your MCP client cannot authenticate to AWS IAM endpoints directly; use the library when you need programmatic session control. The proxy also supports upstream tool discovery, AWS profile selection, metadata, custom headers, retries, and read-only filtering.

Use cases

  • Connect Claude Desktop to an IAM-secured MCP endpoint on AWS
  • Route MCP requests through AWS SigV4 signing
  • Build LangChain, LlamaIndex, or Strands Agents applications against AWS MCP servers
  • Switch AWS profiles for individual MCP calls

Key features

  • AWS SigV4 request signing
  • Dynamic upstream tool discovery
  • Multiple AWS profile support
  • Read-only tool filtering
  • Metadata and custom header injection
  • CLI proxy and Python library distributions

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

26/30 checks healthy over the last 95d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · mcp-proxy-for-aws-cli@latest (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars371Stargazers on the source repository.
Last commit2d agoMost recent push to the default branch.
Directory activity1 installsConfig copies, upvotes, and views on AllMCPs.

How AWS MCP Server works

What AWS MCP Server does

AWS MCP Server connects MCP clients and agent applications to MCP servers on AWS that require AWS IAM authentication. It addresses clients and frameworks that support MCP but do not natively sign requests with AWS Signature Version 4 (SigV4).

The package has two distributions for different uses. mcp-proxy-for-aws-cli provides the command-line proxy, while mcp-proxy-for-aws is the library package for importing mcp_proxy_for_aws into Python applications. Both are intended for connecting to AWS-hosted MCP endpoints rather than providing a fixed collection of AWS service tools themselves.

How it works

In proxy mode, the process runs as a client-side bridge between an MCP client and a specified MCP endpoint. It obtains credentials through the local AWS credential chain, including AWS CLI configuration, environment variables, or IAM roles, and signs requests with SigV4 before sending them to the upstream server.

The proxy can discover tools exposed by the upstream MCP server and pass those capabilities to the connected MCP client. Multiple AWS profiles can be configured, allowing calls to select a profile through the aws_profile tool parameter. Library mode exposes the connection flow to Python-based agent applications and gives application code control over the MCP session lifecycle.

Setup and configuration

The runtime prerequisites are Python 3.11 or newer, the uv package manager, and configured AWS credentials. Docker can be used instead when a container-based deployment is preferred.

Run the pinned CLI distribution with an endpoint URL:

bash
uvx mcp-proxy-for-aws-cli@latest <SigV4 MCP endpoint URL>

A local checkout can be started with uv run, and prebuilt container images are available from the public AWS ECR registry. The endpoint is required. Optional settings include the AWS service name, one or more AWS profiles, region, injected metadata, additional HTTP headers, read-only mode, and retry count.

The service name can be inferred from the endpoint URL. Region selection uses the command-line value first and otherwise the AWS_REGION environment variable. If no explicit profile options are supplied, the proxy falls back to AWS_PROFILE or the configured AWS credential chain. Custom headers are included in the SigV4-covered request and are redacted from logs; signing-related headers cannot be supplied manually.

Tools and capabilities

  • Signs upstream MCP requests with AWS SigV4.
  • Discovers tools exposed by the connected MCP server.
  • Connects clients such as Claude Desktop and Kiro CLI to IAM-secured AWS endpoints.
  • Selects among configured AWS profiles using the aws_profile parameter.
  • Injects request metadata and signed custom HTTP headers.
  • Disables tools that are not marked with readOnlyHint=true when read-only mode is enabled.
  • Retries upstream calls when a retry count is configured.
  • Provides a Python library for LangChain, LlamaIndex, Strands Agents, and similar frameworks.

Limitations and notes

The proxy requires a reachable MCP endpoint and AWS credentials with permission to access it. The upstream server determines which tools are available; the proxy does not define a universal AWS tool catalog.

The CLI distribution is intended for uvx and command-line use and pins its dependency tree. The library distribution uses flexible dependency ranges so it can resolve alongside application dependencies. The first uvx launch may take longer while dependencies are downloaded and cached; later launches use the cache. Setting retries to zero disables retry attempts.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about AWS MCP Server

AWS MCP Server is an MCP server that connects MCP clients and Python agent frameworks to IAM-authenticated MCP servers on AWS. It signs requests with AWS SigV4, discovers upstream tools, supports AWS profile selection, and can run as a command-line proxy or a library for frameworks such as LangChain, LlamaIndex, and Strands Agents.

Install the CLI distribution by running `uvx mcp-proxy-for-aws-cli@latest <SigV4 MCP endpoint URL>`. Python 3.11+, `uv`, and configured AWS credentials are required. You can also run it from a local repository or use the published Docker image.

AWS MCP Server authenticates requests with AWS SigV4 using credentials available through the AWS CLI, environment variables, or IAM roles. The proxy signs requests before forwarding them to the configured MCP endpoint.

Yes, AWS MCP Server accepts multiple profiles through repeated `--profile` options. The first profile is the default, and additional profiles can be selected per call with the `aws_profile` tool parameter.

Start the proxy with `--read-only` to disable tools that may require write permissions. Tools annotated with `readOnlyHint=true` remain available in this mode.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAWS MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aws-mcp-server-2?style=directory)](https://allmcps.com/mcp/aws-mcp-server-2)
HTML Embed
<a href="https://allmcps.com/mcp/aws-mcp-server-2"><img src="https://allmcps.com/api/badge/aws-mcp-server-2?style=directory" alt="AWS MCP Server on AllMCPs" /></a>