Skip to main content
Glama
deenesjakoruzh
klara-research

MCP Log Reader

by klara-research
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

MCP-Server: MCP-Protokolle analysieren und debuggen

Schmiedeabzeichen

🎯 Übersicht

MCP Log Reader ist ein spezialisierter MCP-Server, der Sie bei der Analyse und Fehlerbehebung von Model Context Protocol-Protokollen unterstützt. Er bietet Claude direkten Zugriff auf Protokolldateien, wodurch die Fehlerbehebung bei MCP-Integrationen vereinfacht und die Interaktion von Claude mit Ihren Tools nachvollziehbar wird.

  • Multiplattform-Unterstützung : Funktioniert unter macOS, Windows und Linux mit plattformspezifischen Protokollpfaden

  • Intelligente Filterung : Finden Sie bestimmte Protokolleinträge mit einer Textsuche ohne Berücksichtigung der Groß- und Kleinschreibung

  • Paginiertes Browsen : Effizientes Navigieren durch große Protokollsammlungen

  • Größenverwaltung : Verarbeitet große Protokolldateien mit intelligenter Kürzung

  • Nahtlose Claude-Integration : Funktioniert direkt mit Claude Desktop

Related MCP server: Log Analyzer MCP

🚀 Schnellstart

Installation über Smithery

So installieren Sie MCP Log Reader für Claude Desktop automatisch über Smithery :

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

Manuelle Installation

Direkt von GitHub installieren:

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

# Install dependencies
npm i

Erstellen und ausführen:

# Compile TypeScript
npx tsc

🔌 Verbindung zu Claude

Fügen Sie den Server zu Ihrer Claude Desktop-Konfiguration hinzu:

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

Starten Sie dann Claude Desktop neu.

📋 Verfügbare Parameter

Der Protokollleser unterstützt diese Parameter:

Parameter

Beschreibung

Standard

lines

Anzahl der aus jeder Protokolldatei zu lesenden Zeilen

100

filter

Text zum Filtern von Protokolleinträgen (ohne Berücksichtigung der Groß- und Kleinschreibung)

""

customPath

Benutzerdefinierter Pfad zum Protokollverzeichnis

Betriebssystemspezifisch

fileLimit

Maximale Anzahl der pro Seite zu lesenden Dateien

5

page

Seitenzahl für die Paginierung

1

💡 Beispielverwendung

Bitten Sie Claude, das Protokolllesetool zu verwenden:

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

Oder mit bestimmten Parametern:

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

⚙️ So funktioniert es

  1. Der Server erkennt automatisch Ihr Betriebssystem und findet das entsprechende Protokollverzeichnis

  2. Es findet alle MCP-Protokolldateien und sortiert sie nach Änderungszeit (neueste zuerst).

  3. Die angeforderte Seite mit den Protokolldateien wird basierend auf den Paginierungseinstellungen abgerufen.

  4. Dateien werden mit Größenbeschränkungen verarbeitet, um überwältigende Antworten zu vermeiden

  5. Gefilterter Inhalt wird in einem strukturierten Format mit Paginierungsdetails zurückgegeben

📄 Lizenz

MIT-Lizenz

Available Tools

1 tool
read_mcp_logsC

Read MCP logs from the standard location

ParametersJSON Schema
NameRequiredDescriptionDefault
customPathNoOptional custom path to log directory (default is system-specific)
fileLimitNoMaximum number of files to read per page (default: 5)
filterNoOptional text to filter log entries by (case-insensitive)
linesNoNumber of lines to read from the end of each log file (default: 100)
pageNoPage number for pagination (default: 1)

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions reading logs but fails to describe key behaviors like whether this is a safe read operation, what the output format looks like, or any limitations (e.g., file size constraints, error handling). This leaves significant gaps for a tool with multiple parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 5 parameters, no annotations, and no output schema, the description is incomplete. It does not address what the tool returns, how results are structured, or behavioral aspects like pagination details or error conditions, which are crucial for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, meaning all parameters are documented in the input schema. The description does not add any additional meaning or context beyond what the schema provides, such as explaining interactions between parameters or typical use cases. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Read') and resource ('MCP logs from the standard location'), providing a specific verb+resource combination. However, with no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, so it falls short of a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It simply states what the tool does without context for its application, leaving the agent to infer usage scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool updatev1.0.0
    • First observedread_mcp_logs
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • My MCP Server

    goodafternoonoo
    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.
    38 npm
    -

  • Log Analyzer MCP

    Fato07
    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
    5
    MIT

  • mcp-server-logs-sieve

    Oluwatunmise-olat
    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.
    204 npm
    4
    MIT

  • log-mcp

    ascii766164696D
    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

Appeared in Searches