What can you do with the AWS ECS integration?

LiveContext exposes 28 operations on AWS ECS, covering cluster, service, task and task definition. Common uses include automate task management, automate cluster management and automate service management.

LiveContext

All integrations

AWS ECS integration

Amazon Elastic Container Service API for managing containerized applications. Create and manage clusters, services, task definitions, and tasks for running Docker containers on AWS infrastructure.

28 toolsCustom authAPI docs

Connect AWS ECS How integrations work

Common AWS ECS use cases

automate task management
automate cluster management
automate service management
automate task definition management
automate resource management
automate container instance management
run task programmatically
list task programmatically
stop task programmatically
start task programmatically

What you can do with AWS ECS

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Cluster, 7 operations

POSTcreate_cluster
Creates a new Amazon ECS cluster. By default, your account receives a default cluster when you launch your first container instance.
POSTdelete_cluster
Deletes the specified cluster. The cluster transitions to the INACTIVE state. Clusters with running tasks, services, or container instances cannot be deleted.
POSTdescribe_clusters
Describes one or more of your clusters. Returns a list of cluster descriptions.
POSTlist_clusters
Returns a list of existing clusters.
POSTput_cluster_capacity_providers
Modifies the available capacity providers and the default capacity provider strategy for a cluster.
POSTupdate_cluster
Updates the cluster with the specified settings.
POSTupdate_cluster_settings
Updates the settings for a cluster. Use this action to enable or disable CloudWatch Container Insights for a cluster.

Service, 5 operations

POSTcreate_service
Runs and maintains a desired number of tasks from a specified task definition. If the number of running tasks falls below the desired count, ECS runs another copy of the task.
POSTdelete_service
Deletes a specified service within a cluster. You can delete a service if you have no running tasks in it and the desired task count is zero.
POSTdescribe_services
Describes the specified services running in your cluster.
POSTlist_services
Lists the services that are running in a specified cluster.
POSTupdate_service
Modifies the parameters of a service. For services using a rolling update deployment, the desired count, deployment configuration, network configuration, task placement, or task definition can be updated.

Task, 5 operations

POSTdescribe_tasks
Describes a specified task or tasks.
POSTlist_tasks
Returns a list of tasks. You can filter the results by cluster, task definition family, container instance, launch type, what IAM principal started the task, or by the desired status of the task.
POSTrun_task
Starts a new task using the specified task definition. You can allow Amazon ECS to place tasks for you, or you can customize how Amazon ECS places tasks using placement constraints and placement strategies.
POSTstart_task
Starts a new task from the specified task definition on the specified container instance or instances. Use RunTask instead of StartTask if you want Amazon ECS to use its built-in task placement logic to pick the best container instance for you.
POSTstop_task
Stops a running task. Any tags associated with the task will be deleted. When StopTask is called on a task, the equivalent of docker stop is issued to the containers running in the task.

Task definition, 5 operations

POSTdelete_task_definitions
Deletes one or more task definitions. You must deregister task definitions before deleting them. Up to 10 task definitions can be deleted per call.
POSTderegister_task_definition
Deregisters the specified task definition by family and revision. Upon deregistration, the task definition is marked as INACTIVE. Existing tasks and services that reference an INACTIVE task definition continue to run without disruption.
POSTdescribe_task_definition
Describes a task definition. You can specify a family and revision to find information about a specific task definition, or you can simply specify the family to find the latest ACTIVE revision in that family.
POSTlist_task_definitions
Returns a list of task definitions that are registered to your account. You can filter the results by family name with the familyPrefix parameter or by status with the status parameter.
POSTregister_task_definition
Registers a new task definition from the supplied family and containerDefinitions. Optionally, you can add data volumes to your containers with the volumes parameter.

Resource, 3 operations

POSTlist_tags_for_resource
Lists the tags for the specified Amazon ECS resource. Supports clusters, services, task definitions, container instances, and tasks.
POSTtag_resource
Associates the specified tags to a resource with the specified resourceArn. If existing tags on a resource are not specified in the request parameters, they are not changed.
POSTuntag_resource
Deletes specified tags from a resource.

Container instance, 2 operations

POSTdescribe_container_instances
Describes Amazon Elastic Container Service container instances. Returns metadata about registered and remaining resources on each container instance requested.
POSTlist_container_instances
Returns a list of container instances in a specified cluster. You can filter the results of a ListContainerInstances operation with cluster query language statements inside the filter parameter.

Task definition family, 1 operation

POSTlist_task_definition_families
Returns a list of task definition families that are registered to your account. This list includes task definition families that no longer have any ACTIVE task definition revisions.

Use AWS ECS from Claude Code, Cursor or Codex

Connect AWS ECS in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its AWS ECS operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect AWS ECS

Create your workspace
Sign up free. Nothing to install.
Connect AWS ECS once
Add your AWS ECS connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

AWS ECS integration FAQ

What can you do with the AWS ECS integration?: LiveContext exposes 28 operations on AWS ECS, covering cluster, service, task and task definition. Common uses include automate task management, automate cluster management and automate service management.