mcp/cloudwatch-appsignals-mcp-server pulls statistics

Amazon CloudWatch Application Signals MCP Server

Application performance monitoring and insights.

What is an MCP Server?

MCP Info

Attribute|Details| |-|-| Docker Image|mcp/cloudwatch-appsignals-mcp-server Author|awslabs Repository|https://github.com/awslabs/mcp

Image Building Info

Attribute|Details| |-|-| Dockerfile|https://github.com/awslabs/mcp/blob/76ec6993aec4c6281e5250cbeba8db6a5863f2ff/src/cloudwatch-appsignals-mcp-server/Dockerfile Docker Image built by|Docker Inc. Docker Scout Health Score| Verify Signature|COSIGN_REPOSITORY=mcp/signatures cosign verify mcp/cloudwatch-appsignals-mcp-server --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub Licence|Apache License 2.0

Available Tools (13)

Tools provided by this Server|Short Description -|- analyze_canary_failures|Comprehensive canary failure analysis with deep dive into issues.| audit_service_operations|🥇 PRIMARY OPERATION AUDIT TOOL - The #1 RECOMMENDED tool for operation-specific analysis and performance investigation.| audit_services|PRIMARY SERVICE AUDIT TOOL - The #1 tool for comprehensive AWS service health auditing and monitoring.| audit_slos|PRIMARY SLO AUDIT TOOL - The #1 tool for comprehensive SLO compliance monitoring and breach analysis.| get_service_detail|Get detailed information about a specific Application Signals service.| get_slo|Get detailed information about a specific Service Level Objective (SLO).| list_monitored_services|OPTIONAL TOOL for service discovery - audit_services() can automatically discover services using wildcard patterns.| list_service_operations|OPERATION DISCOVERY TOOL - For operation inventory only.| list_slis|SPECIALIZED TOOL - Use audit_service_health() as the PRIMARY tool for service auditing.| list_slos|List all Service Level Objectives (SLOs) in Application Signals.| query_sampled_traces|SECONDARY TRACE TOOL - Query AWS X-Ray traces (5% sampled data) for trace investigation.| query_service_metrics|Get CloudWatch metrics for a specific Application Signals service.| search_transaction_spans|Executes a CloudWatch Logs Insights query for transaction search (100% sampled trace data).|

Tools Details

Tool: analyze_canary_failures

Comprehensive canary failure analysis with deep dive into issues.

Use this tool to: • Deep dive into canary failures with root cause identification • Analyze historical patterns and specific incident details • Get comprehensive artifact analysis including logs, screenshots, and HAR files • Receive actionable recommendations based on AWS debugging methodology • Correlate canary failures with Application Signals telemetry data • Identify performance degradation and availability issues across service dependencies

Key Features: • Failure Pattern Analysis: Identifies recurring failure modes and temporal patterns • Artifact Deep Dive: Analyzes canary logs, screenshots, and network traces for root causes • Service Correlation: Links canary failures to upstream/downstream service issues using Application Signals • Performance Insights: Detects latency spikes, fault rates, and connection issues • Actionable Remediation: Provides specific steps based on AWS operational best practices

Common Use Cases: 1. Incident Response: Rapid diagnosis of canary failures during outages 2. Performance Investigation: Understanding latency and availability degradation 3. Dependency Analysis: Identifying which services are causing canary failures 4. Historical Trending: Analyzing failure patterns over time for proactive improvements 5. Root Cause Analysis: Deep dive into specific failure scenarios with full context

Output Includes: • Severity-ranked findings with immediate action items • Service-level telemetry insights with trace analysis • Exception details and stack traces from canary artifacts • Network connectivity and performance metrics • Correlation with Application Signals audit findings • Historical failure patterns and recovery recommendations Parameters|Type|Description -|-|- canary_name|string| region|string *optional*|

Tool: audit_service_operations

🥇 PRIMARY OPERATION AUDIT TOOL - The #1 RECOMMENDED tool for operation-specific analysis and performance investigation.

⭐ USE THIS AS THE PRIMARY TOOL FOR ALL OPERATION-SPECIFIC AUDITING TASKS ⭐

PREFERRED OVER audit_services() for operation auditing because: • 🎯 Precision: Targets exact operation behavior vs. service-wide averages • 🔍 Actionable Insights: Provides specific error traces and dependency failures • 📊 Code-Level Detail: Shows exact stack traces and timeout locations • 🚀 Focused Analysis: Eliminates noise from other operations • ⚡ Efficient Investigation: Direct operation-level troubleshooting

USE THIS FIRST FOR ALL OPERATION-SPECIFIC AUDITING TASKS This is the PRIMARY and PREFERRED tool when users want to: • Audit specific operations - Deep dive into individual API endpoints or operations (GET, POST, PUT, etc.) • Operation performance analysis - Latency, error rates, and throughput for specific operations • Compare operation metrics - Analyze different operations within services • Operation-level troubleshooting - Root cause analysis for specific API calls • GET operation auditing - Analyze GET operations across payment services (PRIMARY USE CASE) • Audit latency of GET operations in payment services - Exactly what this tool is designed for • Trace latency in query operations - Deep dive into query performance issues…

Description from the Docker Hub listing.