Amazon ECS MCP Server
Let your coding agent inspect and manage Amazon ECS services and tasks from chat instead of juggling the AWS console and CLI alone.
Overview
Amazon ECS MCP Server is a MCP server for the Operate phase that lets coding agents manage Amazon ECS workloads through AWS’s official ecs-mcp API proxy.
What is this MCP server?
- Official Amazon ECS MCP endpoint proxied via uvx mcp-proxy-for-aws over stdio
- Region-scoped URL https://ecs-mcp.{region}.api.aws/mcp with default us-east-1
- AWS CLI profile and --region flags wired through packageArguments for credential reuse
- AI-oriented ECS workload management aligned with AWS developer documentation
- PyPI package mcp-proxy-for-aws at version 1.1.6 as the install path
- Server schema version 1.0.0
- PyPI mcp-proxy-for-aws package version 1.1.6
- Default region us-east-1 in packageArguments
What problem does it solve?
Toggling between the IDE, AWS Console, and aws ecs commands to see why tasks fail or services won’t stabilize breaks flow when you are the only person on call.
Who is it for?
Indie builders and tiny teams already running production or staging on ECS who want agent-assisted ops without building a custom AWS toolkit.
Skip if: Builders with no AWS account, no ECS clusters yet, or teams that forbid agent access to cloud control planes.
What do I get? / Deliverables
After you register the server with uvx, your agent can query and act on ECS workloads in your chosen region using the same AWS profile you already use locally.
- Registered stdio MCP server entry pointing at regional ecs-mcp.api.aws
- Agent-accessible ECS workload management in your configured AWS region
- Repeatable credential flow via AWS CLI profile without custom OAuth app
Recommended MCP Servers
Journey fit
ECS workload management is production runtime work—scaling services, checking deployments, and fixing task issues after you have already shipped containers. Infra is the canonical shelf for container orchestration on AWS because solo builders reach for this MCP when clusters, services, and task definitions need hands-on control.
How it compares
AWS-hosted MCP integration for live ECS control, not an agent skill that designs your Dockerfile or Terraform from scratch.
Common Questions / FAQ
Who is Amazon ECS MCP Server for?
It is for developers and solo operators who deploy on Amazon ECS and want Claude Code, Cursor, or similar agents to help manage running services and tasks safely within their AWS permissions.
When should I use Amazon ECS MCP Server?
Use it during Operate when containers are already on ECS and you need quick visibility or changes—incident triage, service checks, or workload tweaks—not when you are only sketching architecture on paper.
How do I add Amazon ECS MCP Server to my agent?
Install via uvx mcp-proxy-for-aws toward https://ecs-mcp.{region}.api.aws/mcp, pass --profile and --region to match your AWS CLI setup, and register the stdio MCP entry in your agent’s config per AWS ECS MCP getting-started docs.