Best for
- Developers and operators who want AI assistance across the whole AWS containerization deployment flow
- Scenarios that need to quickly root-cause an ECS deployment issue
A
Amazon ECS MCP Server
Official
AWS's official server for managing and troubleshooting Amazon ECS container deployments
GitHub source repository ↗
70FMRS · B
Maintained by the official AWS Labs team; the ALLOW_WRITE=false safe-by-default design is a real positive. It involves creating and deleting real cloud resources, so risk is higher than a typical local tool — all write-related tools are clearly listed here. This review is a static check of source and docs, not an actual deployment test.
An MCP server officially maintained by AWS Labs (the ECS sub-project within the awslabs/mcp monorepo), covering the full lifecycle from containerizing an app to ECS deployment and troubleshooting: containerization best-practice guidance, ECR image build/push, one-click ECS Express Mode deployment (auto-configured load balancer, auto-scaling, CloudFormation infrastructure), resource listing, and deployment diagnostics. AWS also offers a fully managed remote ECS MCP service; this entry covers the locally-runnable open-source implementation.
Tools
containerize_app
Provide best-practice guidance for containerizing an application
build_and_push_image_to_ecr
Create ECR infrastructure and build/push a Docker image
validate_ecs_express_mode_prerequisites
Validate required IAM roles and images exist before deployment
ecs_resource_management
List/view/create ECS resources (clusters, services, tasks, task definitions) and ECR images
wait_for_service_ready
Track ECS deployment progress and wait for the service to become ready
delete_app
Clean up all resources created by an Express Mode deployment
ecs_troubleshooting_tool
Diagnose and troubleshoot common ECS deployment problems
Setup
Recommended: uvx --from awslabs-ecs-mcp-server ecs-mcp-server (requires an AWS CLI profile with appropriate permissions configured beforehand). ALLOW_WRITE=false and ALLOW_SENSITIVE_DATA=false by default — a deliberate safe default requiring explicit opt-in for write access and sensitive data. AWS also offers a fully managed remote version; see docs.aws.amazon.com.
claude_desktop_config.json
{
"mcpServers": {
"awslabs.ecs-mcp-server": {
"command": "uvx",
"args": ["--from", "awslabs-ecs-mcp-server", "ecs-mcp-server"],
"env": {
"AWS_PROFILE": "<your-aws-profile>",
"AWS_REGION": "<your-aws-region>",
"FASTMCP_LOG_LEVEL": "ERROR",
"ALLOW_WRITE": "false",
"ALLOW_SENSITIVE_DATA": "false"
}
}
}
}
Fit and risk
Not for
- Teams without an AWS account or not using ECS
- Teams highly cautious about automated production deployments that don't want an AI directly creating cloud resources (keep ALLOW_WRITE=false for read-only troubleshooting)
Required permissions
- Requires valid AWS credentials (an AWS CLI profile); actual scope depends on what that IAM identity is granted
- With ALLOW_WRITE=true it can create/modify/delete ECS services, ECR repos, and other cloud resources; ALLOW_SENSITIVE_DATA gates access to logs and other sensitive data
Risks and side effects
- With write access enabled, the assistant's actions can directly incur cloud costs or accidentally delete production resources — test in a non-production account or with an approval workflow first
- delete_app removes all resources created by an Express Mode deployment and is irreversible — confirm the target application carefully
Troubleshooting
- Permission errors: check that the IAM identity behind the AWS CLI profile has the required ECS/ECR/IAM permissions
- Express Mode deployment fails: run validate_ecs_express_mode_prerequisites first to check prerequisites are met
- Service stays not-ready: use wait_for_service_ready or ecs_troubleshooting_tool to find the specific blocker
Use cases
Containerize a web app and deploy it to ECS without hand-writing a Dockerfile or CloudFormation template
Have an AI assistant diagnose why an ECS service deployment failed or is unhealthy
List the ECS clusters, services, and task definitions in the current account
Clean up an ECS Express Mode deployment and its associated resources that are no longer needed
Supported clients
Claude DesktopFull support
Claude CodeFull support
VS CodeFull support
CursorFull support
WindsurfFull support
KiroFull support
ClineFull support