Skip to main content
Glama

MCP Server: Analyze & Debug MCP Logs

🎯 Overview

MCP Log Reader is a specialized MCP server that helps you analyze and debug Model Context Protocol logs. It provides Claude with direct access to log files, making it easy to troubleshoot MCP integrations and understand how Claude interacts with your tools.

  • Multi-platform Support: Works on macOS, Windows, and Linux with platform-specific log paths

  • Smart Filtering: Find specific log entries with case-insensitive text search

  • Paginated Browsing: Navigate large log collections efficiently

  • Size Management: Handles large log files with intelligent truncation

  • Seamless Claude Integration: Works directly with Claude Desktop

Related MCP server: Log Analyzer MCP

🚀 Quick Start

Installing via Smithery

To install MCP Log Reader for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @klara-research/MCP-Analyzer --client claude

Installing Manually

Install directly from GitHub:

# Clone the repository
git clone https://github.com/klara-research/MCP-Analyzer.git
cd MCP-Analyzer

# Install dependencies
npm i

Build and run:

# Compile TypeScript
npx tsc

🔌 Connecting to Claude

Add the server to your Claude Desktop configuration:

{
  "mcpServers": {
    "log-reader": {
      "command": "node",
      "args": [
        "/absolute/path/MCP-Analyzer/build"
      ]
    }
  }
}

Then restart Claude Desktop.

📋 Available Parameters

The log reader supports these parameters:

Parameter

Description

Default

lines

Number of lines to read from each log file

100

filter

Text to filter log entries by (case-insensitive)

""

customPath

Custom path to log directory

OS-specific

fileLimit

Maximum number of files to read per page

5

page

Page number for pagination

1

💡 Example Usage

Ask Claude to use the log reader tool:

Can you check my MCP logs for any connection errors in the last day?

Or with specific parameters:

Can you look through MCP logs with filter="error" and lines=50 to find initialization issues?

⚙️ How It Works

  1. The server automatically detects your OS and finds the appropriate log directory

  2. It locates all MCP log files and sorts them by modification time (newest first)

  3. The requested page of log files is retrieved based on pagination settings

  4. Files are processed with size limits to prevent overwhelming responses

  5. Filtered content is returned in a structured format with pagination details

📄 License

MIT License

Available Tools

1 tool
read_mcp_logsC

Read MCP logs from the standard location

Inputs: customPath, fileLimit, filter, lines, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools, making disambiguation perfect. The tool's purpose is clearly defined as reading MCP logs from a standard location, leaving no room for confusion with other tools.

    Naming Consistency5/5

    The single tool name 'read_mcp_logs' follows a clear verb_noun pattern, which is inherently consistent as there are no other tools to compare it against. This naming convention is straightforward and predictable for any potential future tools.

    Tool Count2/5

    A single tool is too few for a server named 'MCP Log Reader', as it suggests a limited scope that may not cover common log-related operations like filtering, searching, or managing logs. This minimal count feels thin and inadequate for the apparent domain of log reading.

    Completeness2/5

    The tool surface is severely incomplete for log reading; it only provides a basic read function without essential operations such as filtering by date, searching for specific entries, or handling different log levels. This gap will likely cause agent failures when more complex log interactions are needed.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A customizable Model Context Protocol server built with mcp-framework that enables Claude to access external tools and capabilities through a standardized interface.
      85 npm
      -
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for AI-powered log analysis that enables parsing, searching, and debugging across nine log formats directly within Claude. It features automated error extraction, sensitive data scanning, and streaming support for large log files.
      14
      39 PyPI
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that connects Claude (or any MCP compatible client) to your existing log infrastructure. Query, summarize, and trace logs in plain English across GCP Cloud Logging, AWS CloudWatch, Azure Log Analytics, Grafana Loki, and Elasticsearch without writing filter expressions or leaving your editor.
      49 npm
      5
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for log file analysis. Gives LLMs the ability to efficiently analyze large log files without loading them into context.
      7
      101
      MIT