AWS Incident Response with MCP Servers #1336
Open
+2,672
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a new server to this repository. This is a system that responds to incidents within your AWS accounts by analyzing cloudwatch logs for a given service, alarms, applies diagnosis and then creates a JIRA ticket for it. All of this is implemented using Claude Model Context Protocol (MCP).
Description
Server Details
Motivation and Context
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context
I have added another server that some of my customers are interested in using (I work at AWS). Having this be a part of the MCP repo would be helpful and be able to give customers the ability to use MCP from this repo. All information on this MCP solution is given in the readme file. See this: https://github.com/madhurprash/AWS_CloudGuardMCP