Amazon CloudWatch Logs MCP Server

Created By
hyorimitsua year ago
A Model Context Protocol (MCP) server that enables AI assistants to interact with Amazon CloudWatch Logs through a standardized interface using AWS SDK.
Overview

What is Amazon CloudWatch Logs MCP Server?

Amazon CloudWatch Logs MCP Server is a Model Context Protocol (MCP) server that allows AI assistants to interact with Amazon CloudWatch Logs through a standardized interface using the AWS SDK.

How to use Amazon CloudWatch Logs MCP Server?

To use the MCP server, clone the repository, install dependencies, and configure it with your AWS credentials. You can then run the server to manage CloudWatch logs.

Key features of Amazon CloudWatch Logs MCP Server?

  • Standardized interface for CloudWatch Logs operations
  • Tools for creating and managing log groups
  • Easy extensibility for additional CloudWatch Logs operations

Use cases of Amazon CloudWatch Logs MCP Server?

  1. Managing log data for AI applications
  2. Automating log group creation and management
  3. Integrating log monitoring into AI assistant workflows

FAQ from Amazon CloudWatch Logs MCP Server?

  • Is this project ready for production use?

No, the project is currently under active development and not yet ready for production use.

  • How can I contribute to the project?

You can contribute by cloning the repository and following the development setup instructions provided in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hyorimitsu
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago