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 로그 리더는 모델 컨텍스트 프로토콜(MCP) 로그를 분석하고 디버깅하는 데 도움이 되는 전문 MCP 서버입니다. 클로드가 로그 파일에 직접 접근할 수 있도록 하여 MCP 통합 문제를 쉽게 해결하고 클로드가 도구와 상호 작용하는 방식을 이해할 수 있도록 지원합니다.
다중 플랫폼 지원 : 플랫폼별 로그 경로를 사용하여 macOS, Windows 및 Linux에서 작동합니다.
스마트 필터링 : 대소문자 구분 없이 텍스트 검색으로 특정 로그 항목 찾기
페이지별 검색 : 대규모 로그 컬렉션을 효율적으로 탐색
크기 관리 : 지능형 잘라내기 기능을 통해 대용량 로그 파일을 처리합니다.
원활한 Claude 통합 : Claude Desktop과 직접 연동
Related MCP server: Log Analyzer MCP
🚀 빠른 시작
GitHub에서 직접 설치:
지엑스피1
빌드하고 실행:
# 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