cloudwatch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | Yes | AWS region (e.g., eu-west-2) | |
| AWS_PROFILE | No | AWS profile name for authentication | |
| AWS_ACCESS_KEY_ID | No | AWS access key ID for temporary credentials | |
| AWS_SESSION_TOKEN | No | AWS session token for temporary credentials (optional) | |
| CLOUDWATCH_LOG_GROUP | No | Default log group path | |
| AWS_SECRET_ACCESS_KEY | No | AWS secret access key for temporary credentials | |
| CLOUDWATCH_LOG_STREAM_PREFIX | No | Default stream prefix filter |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_log_groupsB | List available CloudWatch log groups with optional prefix filter |
| list_log_streamsA | List log streams in a log group with optional filtering by prefix and date (useful for service-based streams like "sprive-backend-2026-02-20") |
| search_logsB | Search CloudWatch logs with filter patterns and time-based queries. Supports relative times (30m, 1h, 2d) and CloudWatch filter patterns. |
| query_logs_insightsB | Execute CloudWatch Logs Insights queries for advanced log analysis. Supports the full Logs Insights query syntax. |
| get_log_group_infoA | Get detailed information about a specific CloudWatch log group including retention settings and storage |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: getting details, listing groups, listing streams, advanced querying, and simple searching. However, `query_logs_insights` and `search_logs` could be confused for basic searches, though descriptions clarify their different syntaxes.
All tool names follow a consistent verb_noun pattern using snake_case, e.g., `get_log_group_info`, `list_log_groups`, `search_logs`. No mixing of conventions.
With 5 tools, the server covers essential log operations (listing, details, searching, advanced querying) without being bloated. The count is appropriate for a focused CloudWatch Logs interaction.
Core read and query operations are covered, but write operations (create/delete log groups, update retention) are missing. Agents can still work with existing resources, but cannot manage them fully.