F
licenseNot graded
qualityD
maintenanceA customizable Model Context Protocol server built with mcp-framework that enables Claude to access external tools and capabilities through a standardized interface.
38 npm
-
MCP Log Reader
MCP サーバー: MCP ログの分析とデバッグ
🎯 概要
MCP Log Readerは、モデルコンテキストプロトコル（MCP）のログ分析とデバッグを支援する専用のMCPサーバーです。Claudeはログファイルに直接アクセスできるため、MCPの統合に関するトラブルシューティングや、Claudeとツールの連携方法の理解が容易になります。
マルチプラットフォームサポート: プラットフォーム固有のログパスを使用して、macOS、Windows、Linuxで動作します。
スマートフィルタリング: 大文字と小文字を区別しないテキスト検索で特定のログエントリを検索
ページ区切りブラウジング: 大規模なログコレクションを効率的にナビゲート
サイズ管理: インテリジェントな切り捨てにより大きなログファイルを処理します
シームレスなClaude統合：Claudeデスクトップと直接連携
Related MCP server: Log Analyzer MCP
🚀 クイックスタート
GitHub から直接インストールします。
# Clone the repository
git clone https://github.com/klara-research/MCP-Analyzer.git
cd MCP-Analyzer
# Install dependencies
npm iビルドして実行:
# Compile TypeScript
npx tsc🔌 クロードとの接続
Claude Desktop 構成にサーバーを追加します。
{
"mcpServers": {
"log-reader": {
"command": "node",
"args": [
"/absolute/path/MCP-Analyzer/build"
]
}
}
}次に、Claude Desktop を再起動します。
📋 利用可能なパラメータ
ログ リーダーは次のパラメータをサポートします。
パラメータ | 説明 | デフォルト |
| 各ログファイルから読み取る行数 | 100 |
| ログエントリをフィルタリングするテキスト（大文字と小文字は区別されません） | 「」 |
| ログディレクトリへのカスタムパス | OS固有 |
| ページごとに読み取るファイルの最大数 | 5 |
| ページ番号 | 1 |
💡 使用例
Claude にログ リーダー ツールを使用するように依頼します。
Can you check my MCP logs for any connection errors in the last day?または特定のパラメータを使用します:
Can you look through MCP logs with filter="error" and lines=50 to find initialization issues?⚙️ 仕組み
サーバーは自動的にOSを検出し、適切なログディレクトリを見つけます
すべての MCP ログファイルを検索し、変更時刻（新しい順）で並べ替えます。
要求されたログファイルのページは、ページ区切り設定に基づいて取得されます。
ファイルは、応答が多すぎるのを防ぐためにサイズ制限付きで処理されます。
フィルタリングされたコンテンツは、ページ区切りの詳細を含む構造化された形式で返されます。
📄 ライセンス
MITライセンス
Available Tools
1 toolread_mcp_logsC
Read MCP logs from the standard location
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| customPath | No | Optional custom path to log directory (default is system-specific) | |
| fileLimit | No | Maximum number of files to read per page (default: 5) | |
| filter | No | Optional text to filter log entries by (case-insensitive) | |
| lines | No | Number of lines to read from the end of each log file (default: 100) | |
| page | No | Page 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 tool update
v1.0.0- First observed
read_mcp_logs
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
Related MCP Connectors
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
MCP server for building and testing AI agents with multi-model experimentation and insights.
- AgentCatOAuthcom.agentcat
Analytics and debugging for your MCP server — explore usage and sessions, then root-cause errors.
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
Related MCP Servers
- AlicenseAqualityCmaintenanceAn 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.145MIT
- AlicenseNot gradedqualityBmaintenanceAn 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 npm4MIT
- AlicenseAqualityDmaintenanceMCP server for log file analysis. Gives LLMs the ability to efficiently analyze large log files without loading them into context.7101MIT