Claude MCP Server for Observability Demo

Created By
agardnerITa year ago
Overview

what is Claude MCP Server for Observability?

Claude MCP Server for Observability is a demo project that allows users to set up a server for monitoring and analyzing logs through the Claude Desktop application.

how to use Claude MCP Server for Observability?

To use the server, clone the repository, install the required dependencies, and configure Claude Desktop to recognize the MCP server. Then, you can start a chat with Claude to investigate log errors.

key features of Claude MCP Server for Observability?

  • Integration with Claude Desktop for log analysis
  • Ability to monitor and troubleshoot server logs
  • User-friendly setup process with clear instructions

use cases of Claude MCP Server for Observability?

  1. Monitoring application logs for errors and performance issues.
  2. Assisting developers in troubleshooting log-related queries.
  3. Providing insights into server operations through log data.

FAQ from Claude MCP Server for Observability?

  • What do I need to run this project?

You need Claude Desktop and a free account to get started.

  • How do I start the server?

Clone the repository, install dependencies, and run the logreader script.

  • Can I customize the log monitoring?

Yes, you can modify the configuration file to suit your monitoring needs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
agardnerIT
Star
0
Language
Python
License
Apache-2.0 license
Category
monitoring

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
Crevio

2 days ago