← Explore all mcp servers

AWS DATA SERVICES / AWS Labs

AWS SNS and SQS MCP

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

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

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.

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 ↗

DOCUMENTED COMMAND

uvx awslabs.amazon-sns-sqs-mcp-server@latest

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

  1. 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.
  2. Start the uvx entrypoint without --allow-resource-creation and inspect the actual advertised tools.
  3. 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"
      }
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. 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

  2. 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

  3. 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

  4. https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/README.md

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

  5. Applicable licence ↗Checked

    https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE

    Supports: license

  6. 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

  7. 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

Evidence & Ask