Documentation

Quickstart

Bridge an MCP client to an AWS MCP endpoint in a couple of commands.

Run against a public endpoint

The public AWS documentation MCP endpoint can be queried without SigV4 signing. This is the fastest way to confirm the proxy works end to end:

The proxy speaks stdio to your MCP client and forwards signed (or, with --skip-auth, unsigned) traffic to the remote Streamable HTTP endpoint.

Run against a signed endpoint

Drop --skip-auth and point the proxy at an IAM-authenticated endpoint. Credentials load from the normal AWS chain — environment variables, shared config, profiles, and SSO:

aws-mcp-proxy https://<your-endpoint>.api.aws/mcp --profile <profile> --region us-east-1

Wire it into an MCP client

Register the proxy as an MCP server command in your client. For a client that reads a JSON config, the server entry runs the binary with the endpoint as its argument:

{
  "mcpServers": {
    "aws-docs": {
      "command": "aws-mcp-proxy",
      "args": ["https://aws-mcp.us-east-1.api.aws/mcp", "--skip-auth"]
    }
  }
}