CloudWatch MCP Server

CloudWatch MCP Server is a Model Context Protocol server that exposes Amazon Web Services CloudWatch log groups, log queries, and alarms to AI assistants for…

  • AI
  • Monitoring & Logging
CloudWatch MCP Server is a Model Context Protocol server that exposes Amazon Web Services CloudWatch log groups, log queries, and alarms to AI assistants for conversational monitoring and troubleshooting.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

19/100 Low

Maintained
17last commit 563 days ago
Popular
165 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
2032 GB minimum RAM, runs on ARM
GitHub stars
5
Open issues
0
Last commit
2025-05-06
Activity
stale

Checked 15 days ago - source: GitHub (CharlieFng/cloudwatch-mcp)

Resources & Compatibility

Minimum requirements: 32 GB RAM, 8 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Fill in Azure and AWS values Before running the Azure setup script, replace the placeholders with your VM resource ID, the AWS role ARN (the AWS permission grant the VM will use), and your AWS region. If any are wrong, the VM can't authenticate and the agent won't start. source
  • Set a Node.js container start If you're running a Node.js app in a Docker container (a packaged app environment), set the start command to node index.mjs. Without it, the container may start and immediately exit. source
  • Instrument .NET only if needed If your app is .NET, run the AWS .NET installer, then load instrument.sh in your shell and set a service name. This adds monitoring without code changes; without it, .NET telemetry isn't collected. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What CloudWatch telemetry can AI agents access through the CloudWatch MCP Server?

It exposes metrics, logs, alarms, and Application Signals data to AI agents for troubleshooting and root cause analysis.

What deployment security pattern is recommended for MCP servers on AWS?

Use a containerized architecture with industry-standard OAuth 2.0 authentication and multiple security layers.

What external idle timeout can make an MCP server appear down?

A Cloudflare idle timeout can be the culprit when an MCP server is monitored with Route 53 health checks, CloudWatch alarms, and Lambda.

Answers sourced from anthonyapierre.com, docs.aws.amazon.com, growthengineer.ai

Community

Collected 47 days ago - public community threads