
Log Analyzer Mcp
io.github.Fato07Published by GitHub account Fato07v0.4.2Updated Oct 25, 2026
AI-powered log analysis - parse, search, extract errors across 9+ formats
Overview
A local MCP server that lets an assistant parse, search, summarize and debug log files across 9+ formats without copy-pasting them.
- What you can do
- Parse log files, auto-detect their format and extract metadata and timestamps across 9+ formats such as syslog, Apache/Nginx, JSON Lines, Docker, Python, Java/Log4j and Kubernetes logs, streaming large files instead of loading them fully into memory. Search logs with pattern matching, regex, context lines and time filters. Extract and group similar errors, capture stack traces and generate debugging summaries. Correlate related events across multiple files and monitor files for new entries. Answer natural-language questions about logs and scan them for PII, credentials and secrets.
- When to use it
- Useful when debugging applications or servers from log files and you want the assistant to read the files directly rather than pasting chunks, especially for large or multi-file logs, error grouping, time-based correlation, or checking logs for accidentally leaked secrets.
- Requirements
- Runs as a local process over stdio on the user's desktop. Requires Python with uv or pip to install the codesdevs-log-analyzer package; the README recommends a one-line uvx install or a manual entry in the Claude Code settings file. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open Log Analyzer Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Log Analyzer MCP
[MCP Registry] [PyPI version] [PyPI Downloads] [License: MIT] [Python 3.10+] [GitHub stars]
🔍 Stop copy-pasting logs into AI. Let Claude read them directly.
An MCP server for AI-powered log analysis. Parse, search, and debug log files across 9+ formats — right from Claude Code.
📊 At a Glance
🎬 Demo
Analyzing logs with 14 specialized tools
🤔 Why?
✨ Features
- Auto-Detection — Identifies format from 9+ common log types
- Smart Search — Pattern matching with context, regex, and time filtering
- Error Extraction — Groups similar errors, captures stack traces
- Natural Language — Ask questions like "what errors happened today?"
- Sensitive Data Scan — Detect PII, credentials, and secrets
- Multi-File Analysis — Correlate events across distributed systems
- Streaming — Handles 1GB+ files without memory issues
🚀 Quick Start
Then in Claude Code:
📦 Installation
One-liner (Recommended)
Manual
pip / uv / Claude Code config
Add to ~/.claude/settings.json:
📋 Supported Formats
⚡ Performance
🛠️ Available Tools
💡 Examples
Find errors:
Search with context:
Correlate events:
Scan for secrets:
🔧 Development
📈 Star History
📄 License
MIT License - see LICENSE for details.
Found this useful? Give it a ⭐ on GitHub!
Report bugs ·
Request features ·
Discussions ·
Full docs
Source: README.md at commit bcf0b38
Tools
0Version history
1- v0.4.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts