Aws Mcp
Let your coding agent invoke AWS APIs (IAM, S3, Lambda, etc.) from the IDE without writing one-off SDK scripts for every task.
Overview
io.github.YawLabs/aws-mcp is a Build-phase MCP server that lets AI assistants call AWS APIs with SSO-friendly re-login over stdio.
What is this MCP server?
- stdio MCP server (@yawlabs/aws-mcp v1.4.1) for Claude Code, Cursor, and compatible hosts
- Broad AWS API access from natural-language prompts instead of hand-rolled CLI one-liners
- First-class SSO re-login flow when sessions expire mid-task
- npm install path with standard Model Context Protocol stdio transport
- Fits solo builders who already use AWS SSO or IAM profiles locally
- Published server version 1.4.1
- npm package @yawlabs/aws-mcp
- stdio transport per MCP server schema
What problem does it solve?
Switching between the IDE, AWS Console, and CLI breaks flow when you only need a quick API call or resource check.
Who is it for?
Solo builders on AWS who want agent-driven cloud tasks during integration and occasional infra tweaks.
Skip if: Teams that forbid agent-initiated cloud changes or anyone who needs a curated, least-privilege tool surface only.
What do I get? / Deliverables
Your agent can run AWS operations from chat with a clearer path to recover when SSO sessions expire.
- Registered AWS MCP server in your agent config
- Agent-executable AWS API operations subject to your IAM permissions
- Repeatable SSO recovery during long agent sessions
Recommended MCP Servers
Journey fit
How it compares
MCP integration for raw AWS API access, not an opinionated IaC or deploy pipeline skill.
Common Questions / FAQ
Who is io.github.YawLabs/aws-mcp for?
Indie and solo developers who already use AWS and want their coding agent to call AWS APIs from the editor via MCP.
When should I use io.github.YawLabs/aws-mcp?
Use it while wiring cloud integrations, debugging AWS resources, or running exploratory API calls during build or light operate work.
How do I add io.github.YawLabs/aws-mcp to my agent?
Install @yawlabs/aws-mcp from npm, register the server in your host’s MCP config with stdio transport, and ensure AWS credentials or SSO profiles are available on the machine.