Skip to main content

AWS Labs cloudwatch MCP Server

This AWS Labs Model Context Protocol (MCP) server for CloudWatch enables your troubleshooting agents to use CloudWatch data to do AI-powered root cause analysis and provide recommendations. It offers comprehensive observability tools that simplify monitoring, reduce context switching, and help teams quickly diagnose and resolve service issues. This server will provide AI agents with seamless access to CloudWatch telemetry data through standardized MCP interfaces, eliminating the need for custom API integrations and reducing context switching during troubleshooting workflows. By consolidating access to all CloudWatch capabilities, we enable powerful cross-service correlations and insights that accelerate incident resolution and improve operational visibility.

Instructions

The CloudWatch MCP Server provides specialized tools to address common operational scenarios including alarm troubleshooting, understand metrics definitions, alarm recommendations and log analysis. Each tool encapsulates one or multiple CloudWatch APIs into task-oriented operations.

Features

Alarm Based Troubleshooting - Identifies active alarms, retrieves related metrics and logs, and analyzes historical alarm patterns to determine root causes of triggered alerts. Provides context-aware recommendations for remediation.

Log Analyzer - Analyzes a CloudWatch log group for anomalies, message patterns, and error patterns within a specified time window.

Metric Definition Analyzer - Provides comprehensive descriptions of what metrics represent, how they're calculated, recommended statistics to use for metric data retrieval

Alarm Recommendations - Suggests recommended alarm configurations for CloudWatch metrics, including thresholds, evaluation periods, and other alarm settings.

Prerequisites

  1. An AWS account with CloudWatch Telemetry
  2. This MCP server can only be run locally on the same host as your LLM client.
  3. Set up AWS credentials with access to AWS services
    • You need an AWS account with appropriate permissions (See required permissions below)
    • Configure AWS credentials with aws configure or environment variables

Available Tools

Tools for CloudWatch Metrics

  • get_metric_data - Retrieves detailed CloudWatch metric data for any CloudWatch metric. Use this for general CloudWatch metrics that aren't specific to Application Signals. Provides ability to query any metric namespace, dimension, and statistic
  • get_metric_metadata - Retrieves comprehensive metadata about a specific CloudWatch metric
  • get_recommended_metric_alarms - Gets recommended alarms for a CloudWatch metric based on best practice, and trend, seasonality and statistical analysis.
  • analyze_metric - Analyzes CloudWatch metric data to determine trend, seasonality, and statistical properties

Tools for CloudWatch Alarms

  • get_active_alarms - Identifies currently active CloudWatch alarms across the account
  • get_alarm_history - Retrieves historical state changes and patterns for a given CloudWatch alarm

Tools for CloudWatch Logs

  • describe_log_groups - Finds metadata about CloudWatch log groups
  • analyze_log_group - Analyzes CloudWatch logs for anomalies, message patterns, and error patterns
  • execute_log_insights_query - Executes CloudWatch Logs insights query on CloudWatch log group(s) with specified time range and query syntax, returns a unique ID used to retrieve results
  • get_logs_insight_query_results - Retrieves the results of an executed CloudWatch insights query using the query ID. It is used after execute_log_insights_query has been called
  • cancel_logs_insight_query - Cancels in progress CloudWatch logs insights query

Required IAM Permissions

  • cloudwatch:DescribeAlarms

  • cloudwatch:DescribeAlarmHistory

  • cloudwatch:GetMetricData

  • cloudwatch:ListMetrics

  • logs:DescribeLogGroups

  • logs:DescribeQueryDefinitions

  • logs:ListLogAnomalyDetectors

  • logs:ListAnomalies

  • logs:StartQuery

  • logs:GetQueryResults

  • logs:StopQuery

Installation

Option 1: Python (UVX)

Prerequisites

  1. Install uv from Astral or the GitHub README
  2. Install Python using uv python install 3.10

One Click Install

Cursor VS Code
Install MCP Server Install on VS Code

MCP Config (Q CLI, Cline)

  • For Q CLI, update MCP Config Amazon Q Developer CLI (~/.aws/amazonq/mcp.json)
  • For Cline click on "Configure MCP Servers" option from MCP tab
{
  "mcpServers": {
    "awslabs.cloudwatch-mcp-server": {
      "autoApprove": [],
      "disabled": false,
      "command": "uvx",
      "args": [
        "awslabs.cloudwatch-mcp-server@latest"
      ],
      "env": {
        "AWS_PROFILE": "[The AWS Profile Name to use for AWS access]",
        "FASTMCP_LOG_LEVEL": "ERROR"
      },
      "transportType": "stdio"
    }
  }
}

Windows Installation

For Windows users, the MCP server configuration format is slightly different:

{
  "mcpServers": {
    "awslabs.cloudwatch-mcp-server": {
      "disabled": false,
      "timeout": 60,
      "type": "stdio",
      "command": "uv",
      "args": [
        "tool",
        "run",
        "--from",
        "awslabs.cloudwatch-mcp-server@latest",
        "awslabs.cloudwatch-mcp-server.exe"
      ],
      "env": {
        "FASTMCP_LOG_LEVEL": "ERROR",
        "AWS_PROFILE": "your-aws-profile",
        "AWS_REGION": "us-east-1"
      }
    }
  }
}

Please reference AWS documentation to create and manage your credentials profile

Option 2: Docker Image

Prerequisites

Build and install docker image locally on the same host of your LLM client

  1. Install Docker
  2. git clone https://github.com/awslabs/mcp.git
  3. Go to sub-directory cd src/cloudwatch-mcp-server/
  4. Run docker build -t awslabs/cloudwatch-mcp-server:latest .

One Click Cursor Install

Install CloudWatch MCP Server

MCP Config using Docker image(Q CLI, Cline)

  {
    "mcpServers": {
      "awslabs.cloudwatch-mcp-server": {
        "command": "docker",
        "args": [
          "run",
          "--rm",
          "--interactive",
          "-v ~/.aws:/root/.aws",
          "-e AWS_PROFILE=[The AWS Profile Name to use for AWS access]",
          "awslabs/cloudwatch-mcp-server:latest"
        ],
        "env": {},
        "disabled": false,
        "autoApprove": []
      }
    }
  }

Please reference AWS documentation to create and manage your credentials profile

Contributing

Contributions are welcome! Please see the CONTRIBUTING.md in the monorepo root for guidelines.

Feedback and Issues

We value your feedback! Submit your feedback, feature requests and any bugs at GitHub issues with prefix cloudwatch-mcp-server in title.

Metadata

Release files for cloudwatch-mcp-multiprofile 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cloudwatch-mcp-multiprofile 0.1.0
File Size Uploaded Provenance
cloudwatch_mcp_multiprofile-0.1.0.tar.gz 51.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for cloudwatch-mcp-multiprofile 0.1.0
File Interpreter ABI Platform
cloudwatch_mcp_multiprofile-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 106.3 kB

Release files / cloudwatch_mcp_multiprofile-0.1.0.tar.gz

Download URL cloudwatch_mcp_multiprofile-0.1.0.tar.gz
Size 51.2 kB
Tags Source
SHA-256 checksum
How to use checksums
ef3e7bbd02a9bef25b886c80f5991bb3d209e8883dfee23075bc0982e2a0f545
BLAKE2b-256 checksum
How to use checksums
2aef0e7be82d9aa1e893a12026993e51f073861124d02eda982edb5068fbd4bc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.9

Release files / cloudwatch_mcp_multiprofile-0.1.0-py3-none-any.whl

Download URL cloudwatch_mcp_multiprofile-0.1.0-py3-none-any.whl
Size 55.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6f735ee51f1e37c0c61e18591dbab349d30db9925910dc1f873037993a341cb3
BLAKE2b-256 checksum
How to use checksums
d9bb6c069a2bcaca1b2229d7a77a291a5cbee55e72621543d154d59bf9a11a34
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.9

Security for cloudwatch-mcp-multiprofile 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page