AWS Bedrock Logs MCP

Created By
dheerajorugantya year ago
Overview

what is AWS Bedrock Logs MCP?

AWS Bedrock Logs MCP is a command-line interface and API designed for analyzing AWS Bedrock usage and logs through Anthropic's Model Control Protocol (MCP). It allows users to interactively query and analyze their Bedrock usage data using natural language.

how to use AWS Bedrock Logs MCP?

To use the tool, install the necessary dependencies, configure your AWS credentials, and run the server. You can then connect to the server using Claude and issue queries about your Bedrock usage.

key features of AWS Bedrock Logs MCP?

  • Detailed model usage analysis and token consumption statistics
  • User-based analytics for tracking usage patterns and costs
  • Daily usage reports to monitor trends
  • Interactive querying through natural language with Claude

use cases of AWS Bedrock Logs MCP?

  1. Analyzing AWS Bedrock model invocation logs
  2. Monitoring token consumption across different models
  3. Generating daily usage reports for cost analysis

FAQ from AWS Bedrock Logs MCP?

  • What are the requirements to use this tool?

You need Python 3.13+, AWS credentials with CloudWatch Logs access, and Anthropic API access for Claude integration.

  • How do I start the server?

Run the command python cloudwatch_mcp_server.py to start the server.

  • Can I use this tool without Claude?

The tool is designed to work with Claude for natural language queries, but you can also access the API directly.

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

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