get_aws_playbookLABSCO 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 nameget_prevention_guidance— preventive guidance for a named AWS service: S3, IAM, EC2, RDS, VPC, SES, SageMaker or Bedrocklist_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.
Setup effort
Build from source — git clone https://github.com/eisuke000111/aws-customer-playbook-advisor-mcp.git
USE CASES
01
Responding to an incident in progress
Ask for the playbook by scenario keyword and work through the steps it returns.
02
Hardening a service before anything happens
Ask for prevention guidance for the specific service and apply what it lists.
03
Finding out what guidance exists
List the available playbooks rather than guessing whether AWS has published one for your case.
3 tools
Listed in project docs. Your client may show a different list.
get_prevention_guidancelist_available_playbooksBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
Node.js 18 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/eisuke000111/aws-customer-playbook-advisor-mcp.git
cd aws-customer-playbook-advisor-mcp
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"aws-security-advisor": {
"command": "node",
"args": [
"<YOUR_PATH_TO_AWS_CUSTOMER_PLAYBOOK_ADVISOR>/dist/index.js"
]
}
}
}
