Skip to main content
Yanked

This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: Superceeded by awslabs.cloudwatch-mcp-server

AWS Labs cloudwatch-logs MCP Server (DEPRECATED)

An AWS Labs Model Context Protocol (MCP) server for cloudwatch-logs. (DEPRECATED). Please use CloudWatch MCP Server for unified CloudWatch Telemetry related tools.

Instructions

Use this MCP server to run read-only commands and analyze CloudWatchLogs. Supports discovering logs groups as well as running CloudWatch Log Insight Queries. With CloudWatch Logs Insights, you can interactively search and analyze your log data in Amazon CloudWatch Logs and perform queries to help you more efficiently and effectively respond to operational issues.

Features

  • Discovering log groups and metadata about them within your AWS account or accounts connected by CloudWatch Cross Account Observability
  • Converting human-readable questions and commands into CloudWatch Log Insight queries and executing them against the discovered log groups.

Prerequisites

  1. Install uv from Astral or the GitHub README
  2. Install Python using uv python install 3.10
  3. An AWS account with CloudWatch Log Groups
  4. This MCP server can only be run locally on the same host as your LLM client.
  5. Set up AWS credentials with access to AWS services
    • You need an AWS account with appropriate permissions
    • Configure AWS credentials with aws configure or environment variables

Available Tools

  • describe_log_groups - Describe log groups in the account and region, including user saved queries applicable to them. Supports Cross Account Observability.
  • analyze_log_group - Analyzes a CloudWatch log group for anomalies, top message patterns, and top error patterns within a specified time window. Log group must have at least one CloudWatch Log Anomaly Detector configured to search for anomalies.
  • execute_log_insights_query - Execute a Log Insights query against one or more log groups. Will wait for the query to complete for a configurable timeout.
  • get_query_results - Get the results of a query previously started by execute_log_insights_query.
  • cancel_query - Cancel an ongoing query that was previously started by execute_log_insights_query.

Required IAM Permissions

  • logs:Describe*
  • logs:Get*
  • logs:List*
  • logs:StartQuery
  • logs:StopQuery

Installation

(DEPRECATED). Please use CloudWatch MCP Server for unified CloudWatch Telemetry related tools.

Cursor VS Code
Install MCP Server Install on VS Code

Example for Amazon Q Developer CLI (~/.aws/amazonq/mcp.json):

{
  "mcpServers": {
    "awslabs.cloudwatch-logs-mcp-server": {
      "autoApprove": [],
      "disabled": false,
      "timeout": 60,
      "command": "uvx",
      "args": [
        "awslabs.cloudwatch-logs-mcp-server@latest"
      ],
      "env": {
        "AWS_PROFILE": "[The AWS Profile Name to use for AWS access]",
        "AWS_REGION": "[The AWS region to run in]",
        "FASTMCP_LOG_LEVEL": "ERROR"
      },
      "transportType": "stdio"
    }
  }
}

Windows Installation

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

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

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

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

Add or update your LLM client's config with following:

{
  "mcpServers": {
    "awslabs.cloudwatch-logs-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e", "AWS_PROFILE=[your data]",
        "-e", "AWS_REGION=[your data]",
        "awslabs/cloudwatch-logs-mcp-server:latest"
      ]
    }
  }
}

Contributing

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

Release files for awslabs.cloudwatch-logs-mcp-server 0.0.8

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

Source distribution (sdist)

Source distribution for awslabs.cloudwatch-logs-mcp-server 0.0.8
File Size Uploaded
awslabs_cloudwatch_logs_mcp_server-0.0.8.tar.gz 96.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for awslabs.cloudwatch-logs-mcp-server 0.0.8
File Interpreter ABI Platform
awslabs_cloudwatch_logs_mcp_server-0.0.8-py3-none-any.whl Python 3 none any Details

Total release size: 115.7 kB

Release files / awslabs_cloudwatch_logs_mcp_server-0.0.8.tar.gz

Download URL awslabs_cloudwatch_logs_mcp_server-0.0.8.tar.gz
Size 96.2 kB
Tags Source
SHA-256 checksum
How to use checksums
bbc1489efa939b2a91e0ffee4029e17dd8c46ebd50decf1dbbd9c7b9dbeeb6e3
BLAKE2b-256 checksum
How to use checksums
ddd1191804d2a78ebdfb4968917524ef163666d3ddbe38f0422e2e3a83cda1dd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 13, 2025.

Transparency log

Release files / awslabs_cloudwatch_logs_mcp_server-0.0.8-py3-none-any.whl

Download URL awslabs_cloudwatch_logs_mcp_server-0.0.8-py3-none-any.whl
Size 19.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
67ae83758bee69f8237e8d098bccf384150250376fff540856a35ea60e740922
BLAKE2b-256 checksum
How to use checksums
daba54c21269848e733a33b4b7ade4fb0129cde571505c5dc324ea4eeab42acc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 13, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.0.8 This release

2 release files

0.0.7

2 release files

0.0.5

2 release files

0.0.4

2 release files

0.0.3

2 release files

0.0.2

2 release files

0.0.1

2 release files

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