A Claude Code plugin marketplace tailored to startup building on AWS.
Add the marketplace once, then install any plugin from it.
# Add the marketplace
/plugin marketplace add aws-samples/sample-claude-code-plugins-for-startupsA comprehensive AWS development toolkit — 34 skills, 11 sub-agents, 3 MCP servers, and hooks for building, migrating, and reviewing well-architected applications on AWS.
/plugin install aws-dev-toolkit@aws-samplesOr load locally during development:
claude --plugin-dir ./plugins/aws-dev-toolkitNote:
--plugin-dirloads the plugin from disk at session start. File changes are picked up on the next session — not live./plugin updatedoes not work for local plugins (it requires a marketplace source). Restart Claude Code to pick up changes. See Plugins Guide for details.
Once installed, the plugin's skills, agents, and MCP servers are available automatically in Claude Code. Here's how each piece works:
Skills (Automatic)
Skills activate automatically based on context — no special commands needed. Just ask naturally:
"Review this architecture for Well-Architected best practices" → aws-architect
"Why is my CloudFormation stack failing?" → aws-debug
"How much is this infrastructure costing me?" → cost-check
"Are there security issues in my Terraform?" → security-review
"Estimate Bedrock costs for 50k daily invocations" → bedrock
"I want to build a serverless API for processing images" → aws-plan
"Compare ECS vs EKS for my workload" → aws-compare
"Show me a diagram of this architecture" → aws-diagram
"We're moving from GCP to AWS" → aws-migrate
Slash Commands
Some skills are invoked explicitly via slash commands:
/aws-dev-toolkit:iac-scaffold terraform "VPC with public/private subnets and NAT"
/aws-dev-toolkit:iac-scaffold cdk "Serverless API with Lambda and DynamoDB"
/aws-dev-toolkit:aws-health-check us-east-1
/aws-dev-toolkit:aws-diagram from-iac
/aws-dev-toolkit:aws-migrate gcp
Sub-Agents (Automatic)
Sub-agents are spun up automatically when Claude determines a specialist is needed. You can also invoke them directly:
"Explore my AWS environment and summarize what's deployed" → aws-explorer
"Run a Well-Architected review on my production workload" → well-architected-reviewer
"Review my IaC changes before I deploy" → iac-reviewer
"Help me plan a migration from Azure to AWS" → migration-advisor
"Help me pick the right Bedrock model for classification" → bedrock-sme
"I have a PoC agent, help me productionize it" → agentcore-sme
"Should I use ECS or EKS for this workload?" → container-sme
"Help me optimize my AWS bill" → cost-optimizer
MCP Servers
The plugin ships 3 MCP servers that are used behind the scenes by skills and agents — you don't need to invoke them directly.
| Server | Type | Package / URL | Description |
|---|---|---|---|
awsiac |
stdio | awslabs.aws-iac-mcp-server |
CDK/Terraform/CloudFormation development with security scanning |
awsknowledge |
http | https://knowledge-mcp.global.api.aws |
AWS documentation search, service recommendations, and regional availability |
awspricing |
stdio | awslabs.aws-pricing-mcp-server |
AWS service pricing data, cost reports, and IaC cost analysis |
Using MCP servers outside Claude Code (e.g. Kiro)
Add to ~/.kiro/settings/mcp.json (user-level) or .kiro/settings/mcp.json (workspace-level):
Hooks
- After editing an IaC file (
.tf,template.yaml,*-stack.ts, etc.), Claude reminds you to validate before deploying
"I need a new service on AWS"
- Describe what you're building —
aws-plankicks in automatically - Answer 3-5 discovery questions (it won't overwhelm you)
- Review the proposed architecture, security findings, and cost estimate
- Scaffold it —
/iac-scaffold cdk "your description" - Edit the generated code — the hook reminds you to
cdk synth && cdk diff
"Should I use Lambda or Fargate?"
- Describe your workload —
aws-compareevaluates both side-by-side - Get a comparison table across cost, complexity, performance, and team fit
- Receive an opinionated recommendation tied to your constraints
"What does this architecture look like?"
- Ask for a diagram —
/aws-diagram from-iacreverse-engineers your IaC files - Or describe the architecture — it generates Mermaid + ASCII diagrams
"Is my AWS account in good shape?"
- Run
/aws-health-check us-east-1 - Get a quick score with critical findings, warnings, and quick wins
- See SCP recommendations if baseline guardrails are missing
"My Bedrock agent is too expensive"
- Ask about your Bedrock usage —
bedrock-smeanalyzes your patterns - Get model selection guidance — it'll steer you toward the cheapest model that works
- Ask
cost-checkto look at your overall AWS bill for context
"I built a PoC agent, now what?"
- Share your agent code —
agentcore-smereviews it against the production checklist - Get guidance on adding DeepEval for model evaluation
- Choose between AgentCore native observability or Langfuse
- Walk through the PoC-to-production migration path
"Run a Well-Architected review on my workload"
- The
well-architected-revieweragent scans your AWS environment - Evaluates each of the six pillars with real CLI evidence
- Rates findings as HRI (high risk), MRI (medium risk), or LRI (low risk)
- Produces a structured report with prioritized remediation steps
"We're moving from GCP to AWS"
- Describe your GCP environment —
gcp-to-awsmaps services to AWS equivalents - Run the assessment commands to inventory what's deployed
- Review the gotchas for your specific services (global VPCs, Spanner, BigQuery)
- Use
iac-scaffoldto generate the target AWS infrastructure - Ask
migration-advisorfor wave planning and cutover strategy
"We're moving from Azure to AWS"
- Describe your Azure environment —
azure-to-awsmaps services to AWS equivalents - Run az CLI discovery commands to inventory resources
- Pay special attention to identity migration (Azure AD to IAM Identity Center)
- Review Cosmos DB and Synapse migration paths (these are complex)
- Use
iac-scaffoldto generate the target AWS infrastructure
"I have an idea for something on AWS"
- Describe your idea —
customer-ideationguides you through discovery - Answer the structured questions about requirements and constraints
- Review the proposed architecture with Well-Architected checklist
- Use
/iac-scaffoldto generate starter infrastructure code - Ask for a cost estimate before committing
Skills (34):
| Skill | Trigger | Description |
|---|---|---|
| Workflows & Planning | ||
aws-plan |
Auto | End-to-end architecture planning — discovery, design, security review, cost estimate |
aws-architect |
Auto | Design & review AWS architectures against Well-Architected Framework |
well-architected |
Auto | Formal Well-Architected Framework reviews with pillar-by-pillar assessment |
customer-ideation |
Auto | Guided ideation from concept to AWS architecture with service selection |
aws-compare |
Auto | Compare 2-3 architecture options side-by-side across cost, complexity, and trade-offs |
aws-diagram |
Auto / /aws-diagram |
Generate Mermaid/ASCII architecture diagrams from descriptions or existing IaC |
aws-health-check |
/aws-health-check [region] |
Quick account health scan — security, cost waste, reliability gaps |
aws-migrate |
Auto | Guided migration assessment — discover source, map services, plan waves, estimate cost |
| Scaffolding | ||
iac-scaffold |
/iac-scaffold <framework> <desc> |
Scaffold CDK, Terraform, SAM, or CloudFormation projects |
strands-agent |
/strands-agent <description> |
Scaffold Strands Agents SDK projects on Bedrock AgentCore (TS/Python) |
| Debugging & Review | ||
aws-debug |
Auto | Debug AWS deployment failures, Lambda errors, permission issues |
security-review |
Auto | Audit IaC and AWS configs for security issues |
cost-check |
Auto | Analyze and optimize AWS costs |
bedrock |
Auto | Bedrock model selection, agents, knowledge bases, guardrails, and cost modeling |
challenger |
Auto | Adversarial reviewer that stress-tests architecture recommendations |
| AWS Services | ||
lambda |
Auto | Design, build, and optimize Lambda functions — runtimes, cold starts, concurrency |
ec2 |
Auto | Design, configure, and optimize EC2 workloads — instance selection, AMIs, ASGs |
ecs |
Auto | Deploy and troubleshoot ECS workloads — task definitions, services, Fargate |
eks |
Auto | Deploy and troubleshoot EKS clusters — Kubernetes on AWS, Karpenter, IRSA |
s3 |
Auto | S3 bucket configuration, storage optimization, and access patterns |
dynamodb |
Auto | DynamoDB table design, access patterns, single-table design, GSIs |
api-gateway |
Auto | Design and configure API Gateway — REST vs HTTP APIs, authorizers, throttling |
cloudfront |
Auto | CloudFront distributions — caching, origins, Lambda@Edge, Functions |
iam |
Auto | IAM policies, roles, permission boundaries, and least-privilege design |
networking |
Auto | VPC architecture, subnets, security groups, Transit Gateway, VPC endpoints |
messaging |
Auto | SQS, SNS, and EventBridge — queue design, fan-out, event routing |
observability |
Auto | CloudWatch, X-Ray, and OpenTelemetry — dashboards, alarms, tracing |
step-functions |
Auto | Step Functions workflows — state machines, error handling, service integrations |
rds-aurora |
Auto | RDS and Aurora database design, engine selection, HA, and operations |
iot |
Auto | AWS IoT architecture — device connectivity, Greengrass, fleet management |
mlops |
Auto | End-to-end MLOps — SageMaker, training, inference, pipelines, monitoring |
agentcore |
Auto | Amazon Bedrock AgentCore platform design, deployment, and production ops |
| Migration | ||
gcp-to-aws |
Auto | GCP to AWS migration service mapping, gotchas, and environment assessment |
azure-to-aws |
Auto | Azure to AWS migration service mapping, gotchas, and environment assessment |
Sub-Agents (11):
| Agent | Model | Description |
|---|---|---|
aws-explorer |
Opus | Read-only AWS environment exploration and context gathering |
well-architected-reviewer |
Opus | Deep Well-Architected Framework reviews with evidence-based assessment |
iac-reviewer |
Opus | Reviews IaC changes for correctness, security, and best practices |
migration-advisor |
Opus | Cloud migration expert — 6Rs framework, wave planning, cutover strategy |
bedrock-sme |
Opus | Bedrock subject matter expert emphasizing cost-efficient usage patterns |
agentcore-sme |
Opus | AgentCore expert for PoC-to-production agent development |
container-sme |
Opus | Container expert for ECS, EKS, and Fargate architecture decisions |
serverless-sme |
Opus | Serverless architecture expert for Lambda, API Gateway, Step Functions |
networking-sme |
Opus | AWS networking expert — VPC design, hybrid connectivity, DNS, CDN |
observability-sme |
Opus | CloudWatch, X-Ray, and OpenTelemetry observability expert |
cost-optimizer |
Opus | Deep AWS cost optimization — rightsizing, Savings Plans, waste elimination |
MCP Servers (3):
| Server | Type | Package / URL | Description |
|---|---|---|---|
awsiac |
stdio | awslabs.aws-iac-mcp-server |
CDK/Terraform/CloudFormation development with security scanning |
awsknowledge |
http | https://knowledge-mcp.global.api.aws |
AWS documentation search, service recommendations, and regional availability |
awspricing |
stdio | awslabs.aws-pricing-mcp-server |
AWS service pricing data, cost reports, and IaC cost analysis |
Hooks:
- Post-edit reminder to validate IaC files before deploying
- Claude Code v1.0.33+
- uv (for MCP servers via
uvx) - AWS CLI configured with appropriate credentials
- (Optional)
checkov,cfn-nag,tfsecfor security scanning
sample-claude-code-plugins-for-startups/
├── .claude-plugin/
│ └── marketplace.json # Marketplace catalog
├── plugins/
│ └── aws-dev-toolkit/ # Plugin
│ ├── .claude-plugin/
│ │ └── plugin.json # Plugin manifest
│ ├── .mcp.json # MCP server configs (3 servers)
│ ├── skills/ # 34 skills
│ ├── agents/ # 11 sub-agents
│ └── hooks/
│ └── hooks.json # PostToolUse IaC validation
└── README.md
This marketplace can host multiple plugins. To add a new one:
- Create a directory under
plugins/<your-plugin-name>/ - Add
.claude-plugin/plugin.jsonwith the manifest - Add your skills, agents, hooks, and MCP configs
- Register it in
.claude-plugin/marketplace.json
The awslabs/mcp project provides 60+ official MCP servers. Some notable ones to consider adding:
| Server | Use Case |
|---|---|
awslabs.aws-api-mcp-server |
Direct AWS API access via CLI |
awslabs.cdk-mcp-server |
CDK-specific development |
awslabs.terraform-mcp-server |
Terraform-specific workflows |
awslabs.lambda-mcp-server |
Lambda function management |
awslabs.s3-mcp-server |
S3 operations |
awslabs.cloudformation-mcp-server |
CloudFormation resource management |
awslabs.bedrock-mcp-server |
Bedrock AI model integration |
awslabs.cloudwatch-mcp-server |
Metrics, alarms, and log analysis |
awslabs.iam-mcp-server |
IAM user, role, and policy management |
awslabs.cost-analysis-mcp-server |
Cost analysis and optimization |
See CONTRIBUTING for more information.
This library is licensed under the MIT-0 License. See the LICENSE file.
{ "mcpServers": { "awsiac": { "command": "uvx", "args": ["awslabs.aws-iac-mcp-server@latest"], "env": { "FASTMCP_LOG_LEVEL": "ERROR" }, "disabled": false }, "awsknowledge": { "type": "http", "url": "https://knowledge-mcp.global.api.aws", "disabled": false }, "awspricing": { "command": "uvx", "args": ["awslabs.aws-pricing-mcp-server@latest"], "env": { "FASTMCP_LOG_LEVEL": "ERROR" }, "timeout": 120000, "disabled": false } } }