mcp-cloudwatch-tracker

Name: mcp-cloudwatch-tracker
Author: Juri-Dev-Lab

@Juri-Dev-Lab

Repository

About mcp-cloudwatch-tracker

No overview available yet

#mcp-cloudwatch-tracker #log-tracking #aws-cloudwatch

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-cloudwatch-tracker": {
      "command": "npx",
      "args": [
        "-y",
        "@juri-dev-lab/mcp-cloudwatch-tracker@latest",
        "\\"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is mcp-cloudwatch-tracker?

mcp-cloudwatch-tracker is an MCP (Model Context Protocol) server for analyzing and debugging AWS CloudWatch logs. It searches for specific strings, retrieves surrounding context, summarizes analysis, and identifies error patterns. The server is intended for developers and DevOps engineers who need to investigate CloudWatch log data programmatically.

How to use mcp-cloudwatch-tracker?

You can run the server via npx (recommended) or Docker. Both methods require an AWS access key, secret key, and region. For npx, execute:
npx -y @juri-dev-lab/mcp-cloudwatch-tracker@latest --aws-access-key-id YOUR_KEY --aws-secret-access-key YOUR_SECRET --aws-region YOUR_REGION
Alternatively, use environment variables with the Docker image: docker pull juridevlab/mcp-cloudwatch-tracker then run with -e flags. The server provides CLI commands such as search (to search logs) and recent (to fetch recent log events).

Key features of mcp-cloudwatch-tracker

Search CloudWatch log groups for specific strings
Retrieve log context before and after matching events
Summarize log analysis results
Analyze error logs and identify root causes
Flexible AWS credential configuration (.env, environment variables, AWS CLI)

Use cases of mcp-cloudwatch-tracker

Debugging production issues by searching error logs across multiple streams
Monitoring application behavior by extracting recent log events
Analyzing recurring error patterns in CloudWatch log groups
Integrating log investigation into automated workflows via MCP

FAQ from mcp-cloudwatch-tracker

How do I set up AWS credentials for mcp-cloudwatch-tracker?

You can provide credentials via a .env file, system environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION), or by running aws configure to use AWS CLI credentials. Never commit credentials to version control.

What IAM permissions are required for mcp-cloudwatch-tracker?

The server needs the following minimum permissions: logs:GetLogEvents, logs:FilterLogEvents, logs:DescribeLogGroups, and logs:DescribeLogStreams. A sample IAM policy is provided in the README.

Can I run mcp-cloudwatch-tracker with Docker?

Yes. Pull the image from Docker Hub (juridevlab/mcp-cloudwatch-tracker) and run it with the required environment variables set. A Docker build script is also included in the repository.

How do I search for logs using mcp-cloudwatch-tracker?

Use the search command with the log group, stream, and search term. For example: cloudwatch-log-tracker search -g your-log-group -s your-stream -t "search-term". Optional flags allow you to set the search window in days, context line count, and enable error analysis.