Integration

Amazon SQS integration

AWS Simple Queue Service for reliable message queuing between distributed systems. Send, receive, and manage messages in standard and FIFO queues with configurable visibility timeout, dead-letter queues, and long polling.

Connect Amazon SQS How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Amazon SQS.Built from the 23 Amazon SQS tools below, on the connection you add once.

Common Amazon SQS use cases

automate queue management
automate message management
automate message batch management
automate queue attribute management
tag queue programmatically
list queue programmatically
stop an ongoing DLQ redrive
purge queue programmatically
untag queue programmatically
check DLQ redrive task status

What you can do with Amazon SQS

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.

Queue, 6 operations

create_queueCreate queuePOSTCreate a new SQS queue. Supports standard and FIFO queues with configurable attributes like visibility timeout, message retention, and dead-letter queue settings.
delete_queueDelete queuePOSTDelete an SQS queue and all messages in it. You must wait 60 seconds after deleting a queue before you can create another with the same name.
list_queuesList queuesPOSTList SQS queues in the account. Optionally filter by queue name prefix. Returns up to 1000 queues per call with pagination support.
purge_queuePurge queuePOSTDelete all messages from an SQS queue. This action cannot be undone. You can only purge a queue once every 60 seconds.
tag_queueTag queuePOSTAdd or update cost allocation tags on an SQS queue. Tags are key-value pairs for organizing resources and tracking costs.
untag_queueUntag queuePOSTRemove cost allocation tags from an SQS queue by specifying the tag keys to remove.

Message move task, 3 operations

cancel_message_move_taskCancel message move taskPOSTCancel an in-progress message move task. Only tasks with RUNNING status can be cancelled. Messages already moved are not reverted.
list_message_move_tasksList message move tasksPOSTList the most recent message move tasks for a given source queue. Returns up to 10 tasks.
start_message_move_taskStart message move taskPOSTStart an asynchronous task to move messages from a dead-letter queue back to the source queue or to a specified destination queue.

Message, 2 operations

delete_messageDelete messagePOSTDelete a message from an SQS queue using the receipt handle obtained from a receive call. Always delete messages after successful processing to prevent redelivery.
send_messageSend messagePOSTSend a message to an SQS queue. Supports optional delay, message attributes, and FIFO-specific parameters like message group ID and deduplication ID.

Message batch, 2 operations

delete_message_batchDelete message batchPOSTDelete up to 10 messages from an SQS queue in a single API call. Each entry requires a unique ID and the receipt handle from the receive call.
send_message_batchSend message batchPOSTSend up to 10 messages to an SQS queue in a single API call. Each entry can have its own delay, message body, attributes, and FIFO settings. Each message may be up to 1 MiB (1,048,576 bytes), subject to the queue's MaximumMessageSize attribute.

Permission, 2 operations

add_permissionAdd permissionPOSTAdd a permission to a queue for a specific principal (AWS account). This allows cross-account access to SQS queue operations.
remove_permissionRemove permissionPOSTRemove a permission from a queue by its label. This revokes previously granted cross-account access.

Queue attribute, 2 operations

get_queue_attributesGet queue attributesPOSTRetrieve attributes of an SQS queue including message counts, visibility timeout, creation timestamp, dead-letter queue configuration, and encryption settings.
set_queue_attributesSet queue attributesPOSTSet one or more attributes on an SQS queue such as visibility timeout, message retention period, delivery delay, access policy, or dead-letter queue configuration.

Change message visibility, 1 operation

change_message_visibilityChange message visibilityPOSTChange the visibility timeout of a received message. Use this to extend processing time or make a message immediately available for another consumer by setting timeout to 0.

Change message visibility batch, 1 operation

change_message_visibility_batchChange message visibility batchPOSTChange the visibility timeout for up to 10 messages in a single API call. Each entry specifies a receipt handle and a new visibility timeout value.

Dead letter source queue, 1 operation

list_dead_letter_source_queuesList dead letter source queuesPOSTList the queues that have the specified queue configured as their dead-letter queue. Useful for understanding which queues route failed messages to this DLQ.

Queue tag, 1 operation

list_queue_tagsList queue tagsPOSTList all cost allocation tags associated with an SQS queue.

Queue url, 1 operation

get_queue_urlGet queue urlPOSTGet the URL of an existing SQS queue by its name. The queue URL is required for most other SQS operations.

Receive message, 1 operation

receive_messageReceive messagePOSTReceive one or more messages from an SQS queue. Supports long polling to reduce empty responses and configurable visibility timeout for processing time.

Use Amazon SQS from Claude Code, Cursor or Codex

Connect Amazon SQS in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Amazon SQS 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 Amazon SQS

Create your workspace
Sign up free. Nothing to install.
Connect Amazon SQS once
Add your Amazon SQS 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.

Amazon SQS integration FAQ

What can you do with the Amazon SQS integration?

LiveContext exposes 23 operations on Amazon SQS, covering queue, message move task, message and message batch. Common uses include automate queue management, automate message management and automate message batch management.