Log Analyzer
About
Debugging tool that retrieves, filters, and displays MCP logs from Claude desktop applications across macOS, Windows, and Linux for troubleshooting integration issues.
Details
- Author
- klara-research
- Repository
- klara-research/MCP-Analyzer
- GitHub stars
- 8
- Downloads
- 208
- License
- MIT License
- Categories
- Design, Developer Tools, AI, Infrastructure, Frontend
- Tags
- #integration
Jump to
- Multi-platform support: macOS, Windows, and Linux
- Smart filtering with case-insensitive text search
- Paginated browsing of large log collections
- Intelligent truncation for large log files
- Seamless Claude Desktop integration
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Log AnalyzerCommand (node, npx, python, etc.)nodeArguments-
Argument 1
/absolute/path/MCP-Analyzer/build
Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
-
Argument 1
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
To install MCP Log Reader for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @klara-research/MCP-Analyzer --client claude
Install directly from GitHub:
npm i
Build and run:
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?
```
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"log analyzer": {
"cwd": "string",
"env": {},
"args": [
"/absolute/path/MCP-Analyzer/build"
],
"shell": false,
"command": "node"
}
}
}
Linux
{
"cwd": "string",
"env": [],
"args": [
"/absolute/path/MCP-Analyzer/build"
],
"shell": false,
"command": "node"
}
Macos
{
"cwd": "string",
"env": [],
"args": [
"/absolute/path/MCP-Analyzer/build"
],
"shell": false,
"command": "node"
}
Windows
{
"cwd": "string",
"env": [],
"args": [
"/absolute/path/MCP-Analyzer/build"
],
"shell": false,
"command": "node"
}
MCP Server: Analyze & Debug MCP Logs
<div align="center">

<br>
<br>
<br>
🔍 <b>Read logs from standard locations across all platforms</b>
<br>
<br>
🔎 <b>Filter, paginate, and analyze large log collections</b>
<br>
<br>
</div>
🎯 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
🚀 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
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.




