F
licenseNot graded
qualityD
maintenanceEnables natural language queries for AWS CloudWatch logs, metrics, and alarms via an LLM agent with MCP tools.
-
mcp-aws-observability-server
Related Servers
Alternatives to mcp-aws-observability-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to autonomously query AWS CloudWatch Logs and perform structured root-cause analysis via natural language prompts, using MCP tools for log group listing and Insights queries.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query AWS CloudWatch metrics, alarms, and logs read-only via MCP, providing rapid health snapshots and triage without console navigation.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables an AI assistant to read and query Amazon CloudWatch metrics, logs, and alarms through read-only MCP tools.-
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that exposes tools to query Datadog monitors and logs, and AWS CloudWatch Logs, and to group recurring errors by fingerprint. Designed for use with Claude Code to diagnose issues and propose fixes.MIT
- FlicenseNot gradedqualityBmaintenanceEnables secure tool discovery and execution on AWS Lambda with role-based access control, command injection defense, and sensitive data redaction, allowing managed CloudWatch log queries and Terraform operations through a standard MCP interface.-
TDQS
A3.7/5.0
Scored across 3 tools
Disambiguation5/5
Each tool targets a distinct CloudWatch resource and action: listing log groups, searching within a log group, and listing active alarms. There is no meaningful overlap between them, so an agent can select correctly without hesitation.
Naming Consistency5/5
All three tools follow a strict verb_noun snake_case pattern (list_log_groups, search_logs, get_active_alarms). The convention is uniform and predictable.
Tool Count4/5
Three tools is on the thin side for an observability server, but each one is well-scoped and earns its place for log/alarm triage. It sits slightly under what the domain could support rather than being excessive.
Completeness3/5
Logs and alarms are covered, but the observability surface omits other core CloudWatch pillars such as metrics and traces, and there is no way to inspect alarm history or log stream metadata. Agents can triage common issues but will hit dead ends for metric-based investigations.
Maintenance
ActivityMaintained
ResponsivenessNo issues