aws

This MCP server enables natural language interaction with your AWS environment directly from Claude or other compatible clients. It leverages your local AWS credentials and supports multiple AWS profiles and SSO, allowing you to query and manage resources across regions without exposing credentials to external services. Once running, you can initiate conversations like asking for your EC2 instances, S3 bucket sizes, Lambda functions in a region, or ECS clusters, and the MCP server will translate those requests into AWS API calls and return structured results.

To use it with Claude Desktop, configure Claude to connect to the AWS MCP using the provided CLI entry. The server exposes a set of AWS-related Capabilities (e.g., listing resources, filtering by tags, or performing actions) that you can invoke via natural language prompts. You can switch profiles within AWS locally, and the server will execute against the chosen profile, with multi-region support enabled by your AWS configuration. Start by selecting an AWS profile or asking for a specific action, such as listing EC2 instances or showing S3 bucket sizes across regions.

Prerequisites:

• Node.js installed on your machine
• Claude Desktop installed (for testing the integration)
• AWS credentials configured locally (in ~/.aws/), including profiles and/or SSO setup

Installation steps:

1. Clone the repository and navigate to the project folder:

git clone https://github.com/RafalWilinski/aws-mcp
cd aws-mcp

2. Install dependencies with npm or pnpm:

npm install
# or
pnpm install

3. Start the MCP server:

npm start

4. In Claude Desktop, add the MCP server configuration under Settings -> Developer -> Edit Config, using the following example:

{
  "mcpServers": {
    "aws": {
      "command": "npm", // OR pnpm
      "args": [
        "--silent",
        "--prefix",
        "/Users/<YOUR USERNAME>/aws-mcp",
        "start"
      ]
    }
  }
}

5. Restart Claude and verify the connection. You can now issue natural language queries like: "List available AWS profiles", "Show me EC2 instances in us-west-2", or "What Lambda functions are deployed in us-east-1?"

Tips and troubleshooting:

• Ensure your AWS credentials are properly configured in ~/.aws/ and that you have the necessary permissions for the resources you query.
• If you switch profiles or regions, the MCP will use the AWS CLI/SDK configuration on your machine; ensure the correct profile is selected before a request.
• Logs can help diagnose issues: check Claude logs at ~/Library/Logs/Claude/mcp-server-aws.log or similar locations on your system.
• If you use nvm or a custom Node.js path, you can configure the start command to point to the exact node binary as shown in the 'Using with nvm' guidance within the README.
• This server runs locally and uses your credentials; do not expose it publicly. Consider firewalling or restricting access if running in a shared environment.
• For troubleshooting credentials exposure, verify that no credentials are sent to external services by inspecting the AWS SDK configuration and ensuring environment isolation.
• If you modify AWS permissions or enable new services, re-check that the MCP has the necessary permissions to access them.