AWS CLI MCP Server: Setup Guide, Use Cases & Limitations

What Is AWS CLI MCP Server?

AWS CLI MCP Server exposes AWS CLI functionality to Claude, allowing you to run AWS service commands directly through the Claude Code interface. It is maintained by rishikavikondala and targets developers who manage AWS infrastructure and want to interact with it conversationally.

Quick Facts

What You Can Do With It

• S3 management: List buckets, upload or retrieve objects, and inspect bucket configurations without leaving your Claude session.
• EC2 inspection: Query running instances, check instance state, and retrieve metadata for your EC2 fleet.
• Lambda deployment: Invoke functions, update function code, and inspect Lambda configuration and runtime details.
• CloudWatch logs: Retrieve log groups, tail log streams, and filter log events to troubleshoot running services.

How to Set It Up

Prerequisites: You must have the AWS CLI installed and configured locally (aws configure or equivalent environment variables). The server delegates actual API calls to your local AWS CLI binary, so valid credentials are required before starting.

1. Install the package

npx mcp-server-aws
Running via `npx` fetches the latest published version of `mcp-server-aws` from npm without a global install.

**2. Add it to Claude Code**

In your Claude Code MCP configuration file (`.claude/mcp.json`), add the following entry:

```json
{
  "mcpServers": {
    "aws": {
      "command": "npx",
      "args": ["mcp-server-aws"]
    }
  }
}

Save the file and restart Claude Code. The server will appear as an available MCP tool in your session.

3. Verify credentials

Before issuing any commands, confirm your AWS credentials are active:

aws sts get-caller-identity

If this command fails locally, the MCP server will also fail — it uses the same credential chain.

Works Best With

AWS CLI MCP Server is documented as compatible with Claude Code. It has not been tested against other MCP clients such as Claude Desktop or third-party hosts based on available documentation. If you are running a different MCP client, check the GitHub repository for any updates on broader compatibility before integrating.

Known Limitations

• Credential dependency: The server relies entirely on your local AWS CLI credential configuration. It does not manage authentication itself. Expired tokens, missing profiles, or misconfigured regions will cause commands to fail silently or return errors.
• AWS rate limits: All commands are subject to standard AWS API rate limits and quotas for your account. Repeated or bulk commands can trigger throttling.
• No write guardrails: The server does not appear to enforce read-only mode. Destructive operations (e.g., deleting S3 objects or terminating EC2 instances) are technically possible if Claude constructs those commands. Review prompts carefully before confirming actions.
• CLI version dependency: Behavior may vary depending on the version of the AWS CLI installed on your machine. Commands valid in AWS CLI v2 may not work with v1.
• Scope: Only services reachable via the AWS CLI are supported. SDK-only features or console-exclusive actions are out of scope.

Community Resources

• GitHub Repository — primary source for installation notes and code
• GitHub Issues — report bugs or check known problems
• r/aws on Reddit — general AWS tooling discussions where MCP integrations occasionally surface
• Anthropic Discord — #claude-code channel for MCP server setup questions