Summary
AWS's playbooks, current, at the moment you need them.
During an incident the last thing anyone wants is guidance a model half-remembers from a year ago; fetching from AWS's own repository means the steps you read are the steps AWS publishes today. The author states plainly that this packaging is unofficial — the content is AWS's, the server is not.
What it is
A Node MCP server that reads the AWS Customer Playbook Framework repository on demand, so security guidance comes from AWS's current published playbooks rather than from a model's recollection.
What you get
- `get_aws_playbook` — a playbook for a scenario keyword such as s3, iam or ransomware, with an optional specific playbook name
- `get_prevention_guidance` — preventive guidance for a named AWS service: S3, IAM, EC2, RDS, VPC, SES, SageMaker or Bedrock
- `list_available_playbooks` — everything currently available in the AWS repository
- Summaries and prevention sections extracted from the playbook rather than the whole document dumped in
- A 5-minute cache, so repeated questions during an incident do not re-fetch
- Public GitHub endpoints only, so there is no authentication to arrange
Requirements
Node.js 18 or newer and npm. Clone, `npm install`, `npm run build`, then point Claude Desktop at the built dist/index.js and restart it.