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 community link to AWS MCP server #219

Conversation

rishikavikondala
Copy link
Contributor

Description

This PR adds a link to a community MCP server for AWS. The server currently supports interacting with S3 and DynamoDB (demo video here). Making this PR to add a link after originally creating #154.

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 documentation change 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

@rishikavikondala rishikavikondala marked this pull request as draft December 4, 2024 03:53
@rishikavikondala rishikavikondala force-pushed the rkavikondala/add-link-to-aws-mcp-server branch from 19c6a80 to 67e0f1f Compare December 4, 2024 05:48
@rishikavikondala rishikavikondala marked this pull request as ready for review December 4, 2024 05:49
@rishikavikondala rishikavikondala mentioned this pull request Dec 4, 2024
13 tasks
Copy link
Member

@jspahrsummers jspahrsummers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thank you!

@jspahrsummers jspahrsummers merged commit eae16c5 into modelcontextprotocol:main Dec 4, 2024
laith-abood pushed a commit to laith-abood/mcp-claude that referenced this pull request Jan 13, 2025
…vikondala/add-link-to-aws-mcp-server

Add community link to AWS MCP server
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