---
title: "AWS SNS and SQS MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/awslabs-sns-sqs/
description: "Inspect messaging resources and deliberately enable management of tagged queues and topics."
---

# AWS SNS and SQS MCP: review, setup & limitations · Undominated.ai

> Inspect messaging resources and deliberately enable management of tagged queues and topics.

[← Explore all mcp servers](/mcp-servers/)

AWS DATA SERVICES / AWS Labs

# AWS SNS and SQS MCP

Inspect messaging resources and deliberately enable management of tagged queues and topics.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/awslabs/mcp)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 7 linked sources
 Publisher AWS Labs
 Licence [Apache-2.0 ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE)
 Revision 8840003820a7
 [Read what was—and wasn’t—checked ↓](#review)

“AWS Labs MCP bridge to Amazon SNS and SQS operations.”

 [AWS Labs · upstream description ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-sns-sqs-mcp-server/README.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Specialized publisher integration with documented IAM and data access boundaries.
- Inspect topic/queue configuration and message-flow infrastructure under a dedicated AWS role.
- The README manages SNS topics and SQS queues, and it hides creation tools unless a flag is enabled.
- Mutations are limited to resources tagged by this server, and person-to-person messaging mutations stay off by default.

### A good fit for

 - Inspect topic/queue configuration and message-flow infrastructure under a dedicated AWS role.
- Exercise an approved development messaging workflow on explicitly tagged resources.
- Inspecting SNS and SQS resources while creation tools stay hidden
- Changing only brokers or queues this server created and tagged, after the creation flag is actually enabled

### Weigh up before choosing

 - Omitting --allow-resource-creation hides topic/queue creation and deletion, but does not make every remaining operation read-only. Publish, send, receive, purge and other mutations can remain registered behind tag validation.
- The mcp_server_version tag is a server check, not proof of ownership or an IAM boundary. Other principals may be able to create or change tags.
- Receiving SQS messages can alter message visibility; classify it as a stateful operation when investigating live queues.
- The README includes a --disallow-resource-creation example that is not accepted by the inspected parser. Use the default omission of --allow-resource-creation instead.
- The monorepo now recommends Agent Toolkit for AWS for production. This specialized local server remains documented; its leaf and root documentation were checked for deprecation.
- The heading is --allow-resource-creation, but the example command passes --disallow-resource-creation.
- Resources without the mcp_server_version tag are rejected for update and delete.
- Application-to-Person mutative operations are not enabled by default.
- A pin does not verify transitive dependencies. Documented uvx examples use a floating package tag, not the reviewed commit.
- This review did not execute the resource.
- The server was not started and its tools were not called.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - src/amazon-sns-sqs-mcp-server/README.md
- src/amazon-sns-sqs-mcp-server/pyproject.toml
- src/amazon-sns-sqs-mcp-server/awslabs/amazon_sns_sqs_mcp_server/server.py
- Root README.md and LICENSE
- src/amazon-sns-sqs-mcp-server/awslabs/amazon_sns_sqs_mcp_server/sns.py
- src/amazon-sns-sqs-mcp-server/awslabs/amazon_sns_sqs_mcp_server/sqs.py
- LICENSE

### Our findings

 - The parser exposes only --allow-resource-creation. sns.py/sqs.py hide creation/deletion selectively while retaining validators on other mutating tools.
- Source inspection prevents conflating a resource-creation toggle with a global read-only mode.
- The server is a bridge for creating and managing SNS topics and SQS queues, using the host AWS profile.
- Creation tools are hidden unless the resource-creation flag is enabled, and the README says that also prevents deletion of topics and queues. The default is False.
- Updates and deletes are rejected when the mcp_server_version tag is missing. A2P messaging mutations are not enabled by default. The sample command under the allow flag is --disallow-resource-creation.

### Not established by this review

 - Server startup, authentication, live tool execution and security isolation were not tested.
- Published package/container parity with a source revision and hosted implementation internals were not tested.
- The server was not started and its tools were not called.
- A pin does not verify transitive dependencies.
- No tools/list or tool call was made.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-sns-sqs-mcp-server/README.md)

DOCUMENTED COMMAND

 uvx awslabs.amazon-sns-sqs-mcp-server@latest Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - Configure an AWS role limited to the intended SNS/SQS resources and operations. For an inspection-only session, grant read/list actions rather than relying on the creation flag.
- Start the uvx entrypoint without --allow-resource-creation and inspect the actual advertised tools.
- Enable creation only for an agreed development workflow; review target tags and downstream effects before message publication, receipt or purge.

### Before you start

 - Python 3.10 or newer, uv/uvx and an MCP client that can launch a local stdio process.
- An AWS account, configured credentials and access to the intended region and service resources.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "awslabs-sns-sqs": {
 "command": "uvx",
 "args": [
 "awslabs.amazon-sns-sqs-mcp-server@latest"
 ],
 "env": {
 "AWS_PROFILE": "messaging-review",
 "AWS_REGION": "us-east-1"
 }
 }
 }
} Copy configuration ↗

### Compatibility

Python 3.10 or newer, uv/uvx and an MCP client that can launch a local stdio process. · An AWS account, configured credentials and access to the intended region and service resources.

### Implementation

Python

### Transports

stdio

### AWS data services

 - Discovers SNS/SQS resources and exposes permitted API operations under the configured AWS identity.
- Tag-validated mutation tools can publish/send messages or change queues/topics even when creation tools are hidden.

### Cost model

AWS service, model, query and storage charges apply; running the MCP process does not include those services.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Publisher setup, capabilities and operating boundaries ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-sns-sqs-mcp-server/README.md) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-sns-sqs-mcp-server/README.md Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
- [Pinned package and implementation ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-sns-sqs-mcp-server/pyproject.toml) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-sns-sqs-mcp-server/pyproject.toml Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
- [Pinned package and implementation ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-sns-sqs-mcp-server/awslabs/amazon_sns_sqs_mcp_server/server.py) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-sns-sqs-mcp-server/awslabs/amazon_sns_sqs_mcp_server/server.py Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
- [Pinned package and implementation ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/README.md) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/README.md Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
- [Applicable licence ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE Supports: license
- [Inspected tool registration and mutation validators ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-sns-sqs-mcp-server/awslabs/amazon_sns_sqs_mcp_server/sns.py) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-sns-sqs-mcp-server/awslabs/amazon_sns_sqs_mcp_server/sns.py Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
- [Inspected tool registration and mutation validators ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-sns-sqs-mcp-server/awslabs/amazon_sns_sqs_mcp_server/sqs.py) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-sns-sqs-mcp-server/awslabs/amazon_sns_sqs_mcp_server/sqs.py Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### AWS Keyspaces MCP ↗ Inspect Cassandra-compatible schemas and run SELECT queries with dedicated database credentials.](/mcp-servers/awslabs-keyspaces/)[### AWS Labs Amazon Kendra Index ↗ Queries an existing Kendra index and returns document excerpts, source URIs and confidence labels for retrieval workflows.](/mcp-servers/awslabs-kendra-index/)[### AWS Labs Amazon MQ ↗ Inspects and manages Amazon MQ brokers, with additional RabbitMQ management operations.](/mcp-servers/awslabs-amazon-mq/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
