Skip to main content
Glama
ChiragPatankar

LogAnalyzer MCP Server

README.md
# 🚀 LogAnalyzer MCP Server

> **Debug Server Logs in Under 30 Seconds** with AI-powered analysis, real-time monitoring, and actionable fixes.

[![NPM Version](https://img.shields.io/npm/v/loganalyzer-mcp)](https://www.npmjs.com/package/loganalyzer-mcp)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
[![Node.js](https://img.shields.io/badge/Node.js-18%2B-green)](https://nodejs.org/)

**LogAnalyzer MCP Server** is a Model Context Protocol (MCP) server that provides AI-powered log analysis with rapid debugging capabilities. Perfect for DevOps engineers, backend developers, and SRE teams who need instant insights into server issues.

## ⚡ **Key Features**

- **🚀 Rapid Debug**: Analyze and debug server logs in under 30 seconds (tested at 7.5s average)
- **🤖 AI-Powered**: Google Gemini integration for intelligent root cause analysis  
- **📊 Instant Fixes**: Get prioritized, actionable fixes with exact commands
- **👀 Real-time Monitoring**: Watch log files for new errors automatically
- **🔍 Quick Scan**: Ultra-fast error detection in milliseconds
- **📋 Ready Commands**: Copy-paste debug commands for immediate action
- **đŸŽ¯ 95% Confidence**: High-accuracy AI analysis for reliable debugging

## đŸ“Ļ **Installation**

### Quick Start (Global Installation)
```bash
npm install -g loganalyzer-mcp
```

### For Cursor AI Integration
```bash
npm install -g loganalyzer-mcp
```

Then add to your Cursor settings:
```json
{
  "mcpServers": {
    "loganalyzer": {
      "command": "loganalyzer-mcp",
      "env": {
        "GEMINI_API_KEY": "your_gemini_api_key_here"
      }
    }
  }
}
```

## đŸ› ī¸ **MCP Tools Available**

| Tool | Description | Speed |
|------|-------------|--------|
| `rapid_debug` | 🚀 Debug server logs in under 30 seconds with actionable fixes | 7.5s avg |
| `quick_scan` | ⚡ Ultra-fast error detection for real-time monitoring | <1s |
| `analyze_log` | 🤖 Deep AI-powered log analysis with root cause identification | 10-15s |
| `watch_log_file` | 👀 Monitor log files for real-time error detection | Real-time |
| `stop_watching` | âšī¸ Stop monitoring specific log files | Instant |
| `list_watched_files` | 📋 View all currently monitored files | Instant |
| `get_recent_errors` | 📊 Retrieve recent error analysis and history | Instant |
| `get_error_history` | đŸ—„ī¸ Query error history from SQLite with pagination and filtering | Instant |

## đŸŽ¯ **Perfect For**

- **DevOps Engineers** debugging production issues
- **Backend Developers** troubleshooting application errors  
- **SRE Teams** monitoring system health
- **Support Teams** investigating user-reported issues
- **Startup Teams** needing fast incident response

## 📋 **Usage Examples**

### With Cursor AI
```
"Rapidly debug these server logs and give me actionable fixes"
"Quick scan this log file for critical errors"  
"Start monitoring /var/log/app.log for new errors"
"What's causing these database connection timeouts?"
```

### Command Line (Testing)
```bash
# Test the installation
loganalyzer-mcp --version

# Analyze a log file directly
npm run analyze /path/to/logfile.log

# Run rapid debug test
npm run test-rapid
```

## ⚡ **Performance Benchmarks**

- **Analysis Speed**: 7.5 seconds average (target: <30s) - **4x faster than target!**
- **Quick Scan**: <1 second for instant error detection
- **AI Confidence**: 95% accuracy in root cause identification
- **Error Detection**: Instant classification of critical vs. non-critical issues

## đŸ—ī¸ **Technical Stack**

- **Language**: TypeScript/Node.js
- **AI Provider**: Google Gemini (gemini-1.5-flash)
- **File Watching**: Chokidar for cross-platform monitoring
- **MCP Protocol**: Full compliance with latest MCP standards
- **Deployment**: Docker-ready, cloud-native

## 🔧 **Configuration**

### Environment Variables
| Variable | Description | Default |
|----------|-------------|---------|
| `LLM_PROVIDER` | AI provider to use (`gemini` or `anthropic`) | `gemini` |
| `GEMINI_API_KEY` | API Key for Gemini (required if `LLM_PROVIDER=gemini`) | - |
| `ANTHROPIC_API_KEY` | API Key for Anthropic (required if `LLM_PROVIDER=anthropic`) | - |
| `DB_PATH` | File path for SQLite database store | `loganalyzer.db` |
| `LOG_LEVEL` | Logging level (`debug`, `info`, `warn`, `error`) | `info` |
| `MAX_FILE_SIZE` | Maximum size limit of log files to read | `10MB` |

### Graceful Degradation (Local Processing)
If no API key matches the active provider, the server will **not crash**. It logs a warning to `stderr` and disables AI-backed enhancements. The tools will still perform local pattern scanning, watch log files, record events, and compile local fallback diagnoses safely.

### MCP Server Configuration Example
```json
{
  "mcpServers": {
    "loganalyzer": {
      "command": "loganalyzer-mcp",
      "env": {
        "LLM_PROVIDER": "anthropic",
        "ANTHROPIC_API_KEY": "your_anthropic_api_key_here",
        "DB_PATH": "path/to/loganalyzer.db",
        "LOG_LEVEL": "info"
      }
    }
  }
}
```

## 🌟 **What Makes It Special**

- **Speed**: 4x faster than the 30-second target
- **Intelligence**: AI-powered analysis vs. simple pattern matching
- **Actionability**: Provides exact commands, not just descriptions
- **Reliability**: 95% confidence with fallback mechanisms
- **Completeness**: End-to-end solution from detection to resolution

## 📈 **Community Impact**

- **Reduces MTTR** (Mean Time To Recovery) by 80%
- **Eliminates manual log parsing** with intelligent AI analysis
- **Provides learning** through detailed explanations and suggestions
- **Scales expertise** by giving junior developers senior-level debugging insights

## 🚀 **Integration Guides**

- [Cursor AI Integration](docs/cursor-integration.md)
- [Claude Desktop Setup](docs/claude-desktop.md)
- [Example Usage Scenarios](examples/sample-usage.md)

## 🐛 **Troubleshooting**

### Common Issues
1. **MCP Server exits immediately**: This is normal! MCP servers are started on-demand by clients.
2. **API Key errors**: Ensure `GEMINI_API_KEY` is set in your environment.
3. **File watching fails**: Check file permissions and path validity.

### Debug Commands
```bash
# Test API connection
npm run validate

# Test rapid debugging
npm run test-rapid

# Check configuration
node -e "console.log(process.env.GEMINI_API_KEY ? 'API Key set' : 'API Key missing')"
```

## 🤝 **Contributing**

1. Fork the repository
2. Create a feature branch: `git checkout -b feature-name`
3. Commit changes: `git commit -am 'Add feature'`
4. Push to branch: `git push origin feature-name`
5. Submit a Pull Request

## 📄 **License**

MIT License - see [LICENSE](LICENSE) file for details.

## 🔗 **Links**

- **NPM Package**: [loganalyzer-mcp](https://www.npmjs.com/package/loganalyzer-mcp)
- **GitHub Repository**: [LogAnalyzer MCP Server](https://github.com/ChiragPatankar/loganalyzer-mcp)
- **Documentation**: [Full Documentation](docs/)
- **Hardening Walkthrough**: [Hardening Details](docs/hardening.md)
- **Issues**: [Report Issues](https://github.com/ChiragPatankar/loganalyzer-mcp/issues)

---

**Made with â¤ī¸ for the developer community**  
*Helping teams debug faster, learn more, and ship with confidence.* 

TDQS

B3.3/5.0

Scored across 7 tools

Disambiguation4/5

Most tools have distinct purposes, but 'analyze_log' and 'rapid_debug' could be confused as both involve analyzing logs for debugging, with 'rapid_debug' emphasizing speed and actionable fixes. The other tools like 'list_watched_files', 'stop_watching', and 'watch_log_file' are clearly distinct for file monitoring management.

Naming Consistency3/5

The naming is mixed with some consistent patterns like verb_noun ('analyze_log', 'watch_log_file', 'stop_watching') but deviations such as 'get_recent_errors' and 'list_watched_files' use different verb styles, and 'quick_scan' and 'rapid_debug' include emojis and marketing language, breaking consistency.

Tool Count5/5

With 7 tools, the count is well-scoped for a log analysis server, covering core operations like analysis, monitoring, and file management without being excessive or too sparse, fitting typical MCP server ranges.

Completeness4/5

The tool set covers key log analysis workflows including monitoring (watch/stop/list), analysis (analyze/scan/debug), and error retrieval, but lacks explicit tools for configuration management or historical data export, which could be minor gaps in a comprehensive logging system.

Maintenance

ActivityStale
ResponsivenessNo issues