Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add MCP Server for AWS #154

Conversation

rishikavikondala
Copy link
Contributor

@rishikavikondala rishikavikondala commented Dec 1, 2024

Description

This is an MCP server for AWS that currently supports interacting with S3 and DynamoDB (demo video here). I've added these products as a starting point, but in theory we could extend this MCP server to any other AWS products.

Server Details

  • Server: mcp-server-aws
  • Tools:
    • Creating/listing/deleting S3 buckets
    • Adding, reading, and deleting data from S3 buckets
    • Creating and deleting DynamoDB tables
    • Adding, reading, and deleting data from DynamoDB tables
  • Resources:
    • An audit log of all actions taken via the MCP client
  • Environment variables -- if the access key id and secret access key are not set, the server will use the credentials in the ~/.aws/credentials file by default.
    • AWS_ACCESS_KEY_ID
    • AWS_SECRET_ACCESS_KEY
    • AWS_REGION (defaults to us-east-1)

Motivation and Context

The goal of this MCP server is to be used as a control plane for AWS so that users can view and modify their cloud resources in natural language.

How Has This Been Tested?

I've tested this MCP server using the Claude Desktop app as my MCP client. Tested the following scenarios:

  • Creating a DynamoDB table and reading/writing data within it
  • Creating S3 buckets and uploading/reading data from them
  • Deleting S3 buckets and DynamoDB tables

Breaking Changes

This is a net-new server so there are no breaking changes.

Types of changes

  • New MCP Server
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My server follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Note that this server requires an IAM user with RW permissions for your AWS account for S3 and DynamoDB.

@rishikavikondala rishikavikondala changed the title Add MCP Server for AWS [WIP] Add MCP Server for AWS Dec 1, 2024
@rishikavikondala rishikavikondala force-pushed the rkavikondala/mcp-server-aws branch from 43e2d10 to 552bd28 Compare December 1, 2024 20:59
@rishikavikondala rishikavikondala marked this pull request as ready for review December 1, 2024 23:21
@rishikavikondala rishikavikondala changed the title [WIP] Add MCP Server for AWS Add MCP Server for AWS Dec 1, 2024
@jspahrsummers
Copy link
Member

Thank you for taking the time to build this! We've now made some changes to how we'll manage the servers repo going forward.

TLDR: We're restructuring the MCP servers repository to focus on reference implementations only. New server implementations should be developed in separate repositories and can be added as links to our README, rather than submitted as PRs to this repository.

In line with that new approach, I'll close out this PR, but we would love to include a link to this server once it's in its own repo. Please do submit a new PR when it's ready!

@rishikavikondala
Copy link
Contributor Author

rishikavikondala commented Dec 4, 2024

@jspahrsummers thank you for the update -- I'll make a separate PR to add a link to my own repo! (Update: created #219)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants