← Explore all mcp servers

CLOUD OPERATIONS / Amazon Web Services

AWS CloudWatch Application Signals MCP Server

Reads CloudWatch Application Signals for an account you administer. It is not the general CloudWatch server.

“An MCP (Model Context Protocol) server that provides comprehensive tools for monitoring and analyzing AWS services using AWS Application Signals.”

01 / THE REASONING

Why this made the selection.

  • The README is an Application Signals audit and trace assistant for service health, SLOs, and canaries.
  • Trace search is incomplete unless Transaction Search is enabled, and the enablement tool returns a guide rather than applying the changes itself.

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/cloudwatch-applicationsignals-mcp-server/README.md
  • LICENSE

Our findings

  • README contains awslabs.cloudwatch-applicationsignals-mcp-server@latest.
  • README contains a uvx command.
  • The server monitors and analyzes services through Application Signals, including SLO, trace, canary, and change-event tools.
  • It authenticates with AWS profiles. The documented policy includes application-signals:ListServices and related read actions.
  • get_enablement_guide returns a curated guide for the agent to change code. It does not, in this README, apply that enablement itself. Without Transaction Search, trace access is the 5% X-Ray sample.

Not established by this review

  • No AWS API call was made.
  • 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.cloudwatch-applicationsignals-mcp-server@latest

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

  1. Register the uvx command.
  2. Use credentials for the account you mean.
  3. The one-line command above is the uvx launch in the README client block at this commit, not a separate installer. It was not run.

Before you start

  • uv
  • AWS credentials for the service

Documented configuration example

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

{
  "mcpServers": {
    "applicationsignals": {
      "command": "uvx",
      "args": [
        "awslabs.cloudwatch-applicationsignals-mcp-server@latest"
      ],
      "env": {
        "AWS_PROFILE": "[The AWS Profile Name to use for AWS access]",
        "AWS_REGION": "[AWS Region]",
        "FASTMCP_LOG_LEVEL": "ERROR"
      }
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. Server documentation ↗Checked

    https://github.com/awslabs/mcp/blob/49de7cc11ae064b9224f07ae050c612c3f92dd55/src/cloudwatch-applicationsignals-mcp-server/README.md

    Supports: Package name and uvx launch

  2. Repository licence ↗Checked

    https://github.com/awslabs/mcp/blob/49de7cc11ae064b9224f07ae050c612c3f92dd55/LICENSE

    Supports: Redistribution terms

Evidence & Ask