CloudWatch Logs MCP Server for accessing AWS CloudWatch logs
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-cloudwatch-logs-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# CloudWatch Logs MCP Server An MCP (Model Context Protocol) server that provides tools for accessing AWS CloudWatch logs. This server allows AI assistants to list log groups and read log entries from AWS CloudWatch. ## Available Tools ### list_groups Lists available CloudWatch log groups. **Parameters:** - `prefix` (optional): Log group name prefix - `region` (optional): AWS region - `accessKeyId` (optional): AWS access key ID - `secretAccessKey` (optional): AWS secret access key - `sessionToken` (optional): AWS session token **Returns:** JSON string with the list of log groups, including `logGroupName`, `creationTime`, and `storedBytes`. ### get_logs Gets CloudWatch logs from a specific log group. **Parameters:** - `logGroupName` (required): The name of the log group - `logStreamName` (optional): The name of the log stream - `startTime` (optional): Start time in ISO format or relative time (e.g., "5m", "1h", "1d") - `endTime` (optional): End time in ISO format - `filterPattern` (optional): Filter pattern for the logs - `region` (optional): AWS region - `accessKeyId` (optional): AWS access key ID - `secretAccessKey` (optional): AWS secret access key - `sessionToken` (optional): AWS session token **Returns:** JSON string with the log events, including `timestamp`, `message`, and `logStreamName`. ## Setup ### AWS Credentials Ensure you have AWS credentials configured. You can set them up using the AWS CLI or by setting environment variables: - `AWS_ACCESS_KEY_ID` - `AWS_SECRET_ACCESS_KEY` ### Usage with Claude Desktop Add the following to your `claude_desktop_config.json`: ```json { "mcpServers": { "cloudwatch-logs": { "command": "python3", "args": ["/path/to/cloudwatch-logs-mcp/main.py"], "env": { "AWS_ACCESS_KEY_ID": "<YOUR_ACCESS_KEY_ID>", "AWS_SECRET_ACCESS_KEY": "<YOUR_SECRET_ACCESS_KEY>", }, "disabled": false, "autoApprove": [] } } } ``` ### Docker If you prefer to run the ser…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.