mcpField
A
AWS Instances MCP (Model Context Protocol) Server

AWS Instances MCP (Model Context Protocol) Server

Local
github.com/codewithdpkCloud & Infra2Updated 83w ago

About AWS Instances MCP (Model Context Protocol) Server

AWS Instances MCP Server uses the AWS SDK to list running EC2 instances in a specified region. It is for AWS users who need instance state and network details, and supports multiple availability zones.

Key features

  1. 01List running EC2 instances by region
  2. 02Support multiple availability zones
  3. 03Return instance IDs and types
  4. 04Provide public and private IPs
  5. 05Show instance states

Use cases

  1. 01Review running instances in an AWS region
  2. 02Check instance IPs and states

MCP support

As an MCP server, it exposes the `get-aws-instances` tool to MCP clients, returning running EC2 instance details for a specified region.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

AWS Instances MCP (Model Context Protocol) Server

Overview

This is a Model Context Protocol (MCP) server that retrieves and lists running AWS EC2 instances for a specified region using the AWS SDK.

Prerequisites

  • Node.js (version 18 or later)
  • AWS Account
  • AWS Access Key and Secret Access Key

Setup Instructions

1. Clone the Repository
git clone https://github.com/codewithdpk/aws-mcp-server.git
cd aws-mcp-server
2. Install Dependencies
npm install
3. Configure AWS Credentials

Create a .env file in the project root with your AWS credentials:

AWS_ACCESS_KEY_ID=your_access_key_id
AWS_ACCESS_SECRET_KEY=your_secret_access_key
4. Build the server

To build the server locally:

npm run build
5. Testing your server with Claude for Desktop

Claude for Desktop is not yet available on Linux. Linux users can proceed to the Building a client tutorial to build an MCP client that connects to the server we just built.

First, make sure you have Claude for Desktop installed. You can install the latest version here. If you already have Claude for Desktop, make sure it’s updated to the latest version.

We’ll need to configure Claude for Desktop for whichever MCP servers you want to use. To do this, open your Claude for Desktop App configuration at ~/Library/Application Support/Claude/claude_desktop_config.json in a text editor. Make sure to create the file if it doesn’t exist.

You’ll then add your servers in the mcpServers key. The MCP UI elements will only show up in Claude for Desktop if at least one server is properly configured.

In this case, we’ll add our single weather server like so:

{
    "mcpServers": {
        "aws-mcp-server": {
            "command": "node",
            "args": [
                "/ABSOLUTE/PATH/TO/PARENT/FOLDER/aws-mcp-server/build/index.js"
            ]
        }
    }
}
Troubleshooting
  • Verify AWS credentials have appropriate EC2 read permissions
  • Ensure you have the latest version of Claude Desktop App
  • Check that all dependencies are correctly installed

Features

  • Retrieve running EC2 instances for a specified AWS region
  • Support for multiple availability zones
  • Detailed instance information including:
    • Instance ID
    • Instance Type
    • Public IP
    • Private IP
    • Instance State

Tools

  • get-aws-instances: Retrieves list of running AWS instances for a given region

Example Usage

server.tool("get-aws-instances", {
  region: "ap-south-1"
})

Technologies

  • MCP
  • TypeScript
  • AWS SDK
  • Model Context Protocol (MCP)
  • Zod for type validation

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.