Skip to main content
Glama

🎬 Demo

See it in action! Here's how easy it is to spin up a full-blown EC2 setup β€” VPC, subnets, security groups, this works β€” all through natural language prompts to an AI Model Context Protocol (MCP) server.


Related MCP server: AWS MCP Infrastructure

✨ Features

Currently supports

  1. RDS

  2. S3

  3. EC2

  4. VPC

  5. Subnet

  6. Internet Gateway

  7. Route Table

  8. Security Group

  9. Key Pair

  10. Instance Tag

  11. AMI

More AWS services (like Lambda, API Gateway, etc.) coming soon! Contributions welcome πŸš€


πŸ“‹ Prerequisites

For Development:

  • Node.js >= 18.0.0

  • pnpm >= 10.0.0

For Docker Deployment:

  • Docker and Docker Compose

For Both:

  • AWS Account with AWS credentials (Access Key ID and Secret Access Key)


βš™οΈ Developer Setup

1. Clone the repo

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

❗️Currently, the server reads credentials from MCP configuration headers. In future versions, we'll support AWS Role ARN.

2. Install dependencies

pnpm install

πŸ’‘ Make sure you have pnpm installed globally. If not:

npm install -g pnpm

3. Run the dev server

pnpm dev

🐳 Docker Deployment

Quick Start with Docker

Option 1: Using Docker Compose (Recommended)

docker-compose up -d

Option 2: Using Docker directly

# Build the image
docker build -t aws-mcp .

# Run with port mapping
docker run -d --name aws-mcp-server -p 8080:8080 aws-mcp

The server will be available at:

  • MCP HTTP Stream: http://localhost:8080/mcp

  • MCP SSE: http://localhost:8080/sse

Managing Docker Containers

# View logs
docker-compose logs -f

# Stop container
docker-compose down

# Rebuild and restart
docker-compose build --no-cache && docker-compose up -d

# Stop aws-mcp-server and remove container
docker stop aws-mcp-server && docker rm aws-mcp-server

πŸ’‘ AWS credentials are still passed via HTTP headers (same as development setup). No container configuration needed.


πŸ§ͺ Example: Cursor Configuration

To use this server with Cursor, add the following to your ~/.cursor/mcp.json:

{
  "mcpServers": {
    "aws": {
      "serverUrl": "http://localhost:8080/mcp",
      "headers": {
        "AWS_ACCESS_KEY_ID": "YOUR_AWS_ACCESS_KEY_ID",
        "AWS_SECRET_ACCESS_KEY": "YOUR_AWS_SECRET_ACCESS_KEY",
        "AWS_SESSION_TOKEN": "YOUR_AWS_SESSION_TOKEN"
      }
    }
  }
}

❗️ Use http://localhost:8080/mcp if your client supports HTTP streamable(For eg: Cursor). Use http://localhost:8080/sse if your client supports only SSE(For eg: Windsurf).

MCP HTTP streamable endpoint: http://localhost:8080/mcp

MCP SSE endpoint: http://localhost:8080/sse


πŸ“ Project Structure

.
β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ server.ts             # AWS MCP server setup - Entry point
β”‚   β”œβ”€β”€ aws-clients.ts        # AWS SDK client setup
β”‚   β”œβ”€β”€ config/               # App configuration
β”‚   β”œβ”€β”€ tools/                # Tools definitions
β”‚   β”‚   β”œβ”€β”€ rds/              # RDS operations
β”‚   β”‚   β”œβ”€β”€ s3/               # S3 operations
β”‚   β”‚   β”œβ”€β”€ ec2/              # EC2 operations
β”‚   β”‚   β”œβ”€β”€ vpc/              # VPC operations
β”‚   β”‚   β”œβ”€β”€ subnet/           # Subnet operations
β”‚   β”‚   β”œβ”€β”€ internet-gateway/ # Internet Gateway operations
β”‚   β”‚   β”œβ”€β”€ route-table/      # Route Table operations
β”‚   β”‚   β”œβ”€β”€ security-group/   # Security Group operations
β”‚   β”‚   β”œβ”€β”€ key-pair/         # Key Pair operations
β”‚   β”‚   β”œβ”€β”€ instance-tag/     # Instance Tag operations
β”‚   β”‚   β”œβ”€β”€ ami/              # AMI operations
β”‚   β”œβ”€β”€ schema/               # Tool input schemas
β”‚   β”œβ”€β”€ types/                # TypeScript definitions
β”‚   └── utils/                # Helper functions
β”œβ”€β”€ package.json              # Dependencies and scripts
└── README.md                 # This file

πŸ“Œ Roadmap

  • Support RDS (Create, List, Update, Delete)

  • Add S3 tools

  • Add Network tools

  • Add EC2 tools

  • Add Lambda tools

  • Add API Gateway tools

  • Add IAM tools

  • Add ECS tools


🀝 Contributing

Want to help make AWS infra chat-native? Pull requests, feedback, and feature suggestions are welcome!

  • Clone and fork the repo

  • Create your feature branch (git checkout -b feat/add-ec2)

  • Commit and push

  • Open a PR πŸ™Œ


πŸ“„ License

MIT β€” do what you want, just give credit where it's due. ✌️


⚑ Powered by

Available Tools

54 tools
associate-route-tableB
Idempotent

Associate a route table with a subnet or internet gateway or virtual private gateway

Inputs: RouteTableArgs (required), region.

attach-internet-gatewayB
Idempotent

Attach an internet gateway to a VPC

Inputs: InternetGatewayArgs (required), region.

authorize-security-group-egressC

Authorize a security group egress in the given region

Inputs: SecurityGroupArgs (required), region.

authorize-security-group-ingressB

Authorize a security group ingress in the given region

Inputs: SecurityGroupArgs (required), region.

create-amiC

Create an AMI

Inputs: AmiArgs (required), region.

create-bucketB
Idempotent

Create a new S3 bucket in the given region

Inputs: S3Args (required), region.

create-db-instanceB
Destructive

Create a new RDS DB instance in the given region

Inputs: DBInstanceArgs (required), region.

create-instance-tagC

Create instance tag

Inputs: InstanceArgs (required), region.

create-internet-gatewayB

Create a new internet gateway in the given region

Inputs: InternetGatewayArgs (required), region.

create-key-pairC

Create a key pair in the given region

Inputs: KeyPairArgs (required), region.

create-route-tableB

Create a route table in the given region

Inputs: RouteTableArgs (required), region.

create-security-groupB

Create a security group in the given region

Inputs: SecurityGroupArgs (required), region.

create-subnetB
Idempotent

Create a subnet in the given region

Inputs: SubnetArgs (required), region.

create-vpcB
Idempotent

Create a new VPC in the given region

Inputs: VpcArgs (required), region.

delete-amiC
DestructiveIdempotent

Delete an AMI

Inputs: AmiArgs (required), region.

delete-bucketA
DestructiveIdempotent

Delete an S3 bucket in the given region

Inputs: S3Args (required), region.

delete-db-instanceB
Destructive

Delete a given RDS DB instance in the given region

Inputs: DBInstanceArgs (required), region.

delete-instance-tagC
DestructiveIdempotent

Delete instance tag

Inputs: InstanceArgs (required), region.

delete-internet-gatewayB
DestructiveIdempotent

Delete an internet gateway by ID in the given region

Inputs: InternetGatewayArgs (required), region.

delete-key-pairB
DestructiveIdempotent

Delete a key pair in the given region

Inputs: KeyPairArgs (required), region.

delete-route-tableA
DestructiveIdempotent

Delete a route table in the given region

Inputs: RouteTableArgs (required), region.

delete-security-groupB
DestructiveIdempotent

Delete a security group in the given region

Inputs: SecurityGroupArgs (required), region.

delete-subnetB
DestructiveIdempotent

Delete a subnet by subnet ID in the given region

Inputs: SubnetArgs (required), region.

delete-vpcB
DestructiveIdempotent

Delete a VPC by VPC ID in the given region

Inputs: VpcArgs (required), region.

detach-internet-gatewayB
Idempotent

Detach an internet gateway from a VPC

Inputs: InternetGatewayArgs (required), region.

disassociate-route-tableB
Idempotent

Disassociate a route table from a subnet or internet gateway or virtual private gateway

Inputs: RouteTableArgs (required), region.

import-key-pairC

Import a key pair in the given region

Inputs: KeyPairArgs (required), region.

launch-ec2-instanceB

Launch an EC2 instance in a given region

Inputs: Ec2Args (required), region.

list-amisC
Read-onlyIdempotent

List AMIs

Inputs: AmiArgs (required), region.

list-bucketsB
Read-onlyIdempotent

List all the S3 buckets in the given region

Inputs: S3Args (required), region.

list-db-instancesB
Read-onlyIdempotent

List all the RDS DB instances in the given region

Inputs: DBInstanceArgs (required), region.

list-ec2-instancesB
Read-onlyIdempotent

List EC2 instances in a given region

Inputs: Ec2Args (required), region.

list-instance-tagsC
Read-onlyIdempotent

List instance tags

Inputs: InstanceArgs (required), region.

list-internet-gatewaysB
Read-onlyIdempotent

List all internet gateways in the given region

Inputs: InternetGatewayArgs (required), region.

list-key-pairsB
Read-onlyIdempotent

List key pairs in the given region

Inputs: KeyPairArgs (required), region.

list-route-tablesA
Read-onlyIdempotent

List route tables in the given region

Inputs: RouteTableArgs (required), region.

list-security-group-rulesB
Read-onlyIdempotent

List all security group rules in the given region

Inputs: SecurityGroupRuleArgs (required), region.

list-security-groupsB
Read-onlyIdempotent

List all security groups in the given region

Inputs: SecurityGroupArgs (required), region.

list-subnetsB
Read-onlyIdempotent

List all the subnets in the given region

Inputs: SubnetArgs (required), region.

list-vpcsB
Read-onlyIdempotent

List all the VPCs in the given region

Inputs: VpcArgs (required), region.

modify-security-group-rulesB
Idempotent

Modify a security group rule in the given region

Inputs: SecurityGroupArgs (required), region.

reboot-ec2-instanceB
Idempotent

Reboot an EC2 instance in a given region

Inputs: Ec2Args (required), region.

replace-route-table-associationA
Idempotent

Replace the route table association for a subnet or internet gateway or virtual private gateway

Inputs: RouteTableArgs (required), region.

revoke-security-group-egressB
DestructiveIdempotent

Revoke a security group egress in the given region

Inputs: SecurityGroupArgs (required), region.

revoke-security-group-ingressB
DestructiveIdempotent

Revoke a security group ingress in the given region

Inputs: SecurityGroupArgs (required), region.

start-ec2-instanceB
Idempotent

Start an EC2 instance in a given region

Inputs: Ec2Args (required), region.

stop-ec2-instanceB
Idempotent

Stop an EC2 instance in a given region

Inputs: Ec2Args (required), region.

terminate-ec2-instanceB
DestructiveIdempotent

Terminate an EC2 instance in a given region

Inputs: Ec2Args (required), region.

update-db-instanceB
Destructive

Update a given RDS DB instance in the given region

Inputs: DBInstanceArgs (required), region.

update-security-group-rule-descriptions-egressB
Idempotent

Update the description of a security group rule egress in the given region

Inputs: SecurityGroupArgs (required), region.

update-security-group-rule-descriptions-ingressC
Idempotent

Update the description of a security group rule ingress in the given region

Inputs: SecurityGroupArgs (required), region.

update-subnet-attributeB
Idempotent

Update a subnet attributes by subnet ID in the given region

Inputs: SubnetArgs (required), region.

update-vpc-attributeB
Idempotent

Update a VPC attribute(EnableDnsHostnames, EnableDnsSupport, EnableNetworkAddressUsageMetrics) by VPC ID in the given region

Inputs: VpcArgs (required), region.

update-vpc-endpointB
Idempotent

Update a VPC endpoint(Gateway endpoint, Interface endpoint) by VPC endpoint ID in the given region

Inputs: VpcArgs (required), region.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 54 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific AWS resources and actions, with clear boundaries (e.g., create-vpc vs. update-vpc-attribute). However, some overlap exists in security group operations (authorize/revoke egress/ingress vs. modify-security-group-rules), which could cause minor confusion for agents.

    Naming Consistency5/5

    Tool names follow a highly consistent verb-noun pattern with hyphens throughout (e.g., create-vpc, list-subnets, delete-ami). All 54 tools adhere to this convention, making them predictable and easy to parse.

    Tool Count2/5

    With 54 tools, the count is excessive for a single server, likely overwhelming for agents. While AWS is a broad domain, this feels heavy and could be better scoped into multiple servers (e.g., separate EC2, VPC, S3 servers) for improved usability.

    Completeness5/5

    The tool set provides comprehensive CRUD and lifecycle coverage across AWS services like EC2, VPC, S3, and RDS. It includes creation, listing, updating, and deletion for most resources, with no obvious gaps for core operations, ensuring agents can handle full workflows.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server allowing Claude AI to interact with AWS resources through natural language, enabling users to query and manage AWS services without using the traditional AWS Console or CLI.
      3
      6
      ISC
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to execute AWS CLI commands and retrieve service documentation through the Model Context Protocol. It supports Unix pipes for output filtering and provides pre-defined prompt templates for common cloud management tasks.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a comprehensive suite of tools for interacting with AWS services like S3, EC2, and Lambda using natural language commands. It enables AI assistants to inspect, manage, and operate AWS resources directly through the Model Context Protocol using your local credentials.
      1
      Apache 2.0