Yaw Labs AWS MCP — Claude Code MCP server: how to install
A local MCP server routing AWS operations through your installed CLI, handling SSO device authentication and Cloud Control resources.
claude mcp add --env AWS_PROFILE=<AWS_PROFILE> --env AWS_REGION=<AWS_REGION> --transport stdio yaw-labs-aws-mcp -- npx -y @yawlabs/aws-mcpWhat Yaw Labs AWS MCP does
This server runs on your machine via npx without remote intermediaries. It wraps your local aws CLI binary directly through the aws_call tool, passing target operations and flags. New cloud capabilities become usable immediately whenever you upgrade your system command-line client.
Standard resource lifecycle actions go through AWS Cloud Control API. Seven aws_resource_* tools let the assistant inspect or modify over 1,300 CloudFormation resource types. It also provides aws_resource_diff for dry-run inspections. When AWS SSO credentials expire, the process initiates a device-code login flow. You get a direct link and verification code instead of dropped browser handoffs.
Running this server alongside the official AWS MCP package causes tool collisions. Pick one or the other. The local environment requires an existing aws CLI installation with configured profiles. Large responses hit a 5 MB boundary, so trim wide queries using JMESPath expressions.
What it helps with
- Execute AWS CLI calls directly from an assistant session
- Authenticate with AWS SSO using device codes when browser redirects fail
- Preview CloudFormation resource changes before applying updates
- Query multiple AWS regions in parallel via
aws_multi_region
Example prompts for the agent
- Check our current AWS SSO session and refresh it if needed
- Fetch active S3 buckets with
aws_callin regioneu-central-1 - Run
aws_resource_diffagainst the target SQS queue before modifying properties
How to install Yaw Labs AWS MCP
Platform CLI
claude mcp add --env AWS_PROFILE=<AWS_PROFILE> --env AWS_REGION=<AWS_REGION> --transport stdio yaw-labs-aws-mcp -- npx -y @yawlabs/aws-mcpReplace <…> with your own values
Platform CLI
codex mcp add yaw-labs-aws-mcp --env AWS_PROFILE=<AWS_PROFILE> --env AWS_REGION=<AWS_REGION> -- npx -y @yawlabs/aws-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"yaw-labs-aws-mcp": {
"command": "npx",
"args": [
"-y",
"@yawlabs/aws-mcp"
],
"env": {
"AWS_PROFILE": "<AWS_PROFILE>",
"AWS_REGION": "<AWS_REGION>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"yaw-labs-aws-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@yawlabs/aws-mcp"
],
"env": {
"AWS_PROFILE": "<AWS_PROFILE>",
"AWS_REGION": "<AWS_REGION>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e AWS_PROFILE=<AWS_PROFILE> -e AWS_REGION=<AWS_REGION> yaw-labs-aws-mcp npx -y @yawlabs/aws-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Yaw Labs AWS MCP
How to install Yaw Labs AWS MCP in Claude Code?
Run claude mcp add aws-mcp -- npx -y @yawlabs/aws-mcp. If you need custom environment variables right away, run claude mcp add --env AWS_PROFILE=<AWS_PROFILE> --env AWS_REGION=<AWS_REGION> --transport stdio yaw-labs-aws-mcp -- npx -y @yawlabs/aws-mcp.
What does Yaw Labs AWS MCP do?
It gives your coding agent direct access to your local AWS CLI. The tool exposes Cloud Control API primitives, documentation lookups, and a reliable device-code SSO re-authentication workflow.
Can I run this alongside the official AWS MCP server?
No, you should choose between them. Both handle general AWS API operations, so running both introduces overlapping tools that degrade model routing.
