mcp-cloudwatch-tracker

Created By
Juri-Dev-Laba year ago
MCP Server for tracking logs with AWS CloudWatch
Overview

what is mcp-cloudwatch-tracker?

MCP CloudWatch Tracker is a server application designed to track logs using AWS CloudWatch, providing users with insights into their log data.

how to use mcp-cloudwatch-tracker?

To use the MCP CloudWatch Tracker, set up the server and configure it to connect to your AWS CloudWatch account. Once configured, it will automatically track and log data.

key features of mcp-cloudwatch-tracker?

  • Real-time log tracking with AWS CloudWatch integration
  • Easy setup and configuration
  • User-friendly interface for monitoring logs

use cases of mcp-cloudwatch-tracker?

  1. Monitoring application logs for performance issues
  2. Tracking user activity logs for security audits
  3. Analyzing system logs for troubleshooting

FAQ from mcp-cloudwatch-tracker?

  • What is AWS CloudWatch?

AWS CloudWatch is a monitoring and management service for AWS cloud resources and applications.

  • Is mcp-cloudwatch-tracker free to use?

The repository is open-source, but check the AWS pricing for CloudWatch usage.

  • How do I configure the tracker?

Follow the setup instructions in the GitHub repository to configure the tracker with your AWS account.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Juri-Dev-Lab
Star
0
Language
-
License
-
Category
monitoring

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

5 hours ago