mcp-log-analyzer
Allows analyzing log files and automatically filing GitHub Issues with root cause analysis and suggested fixes, leveraging GitHub's Issues API to create, manage, and deduplicate issues.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-log-analyzeranalyze /var/log/app.log for errors and file issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🔍 NFT Log Analyzer
AI-powered log analysis that automatically files GitHub Issues — 100% local via Ollama, zero data leaves your machine.
What It Does
Point it at any log file and it will:
Scan 500MB+ files in seconds using ripgrep
Parse error patterns, deduplicate repeated events
Analyse using local LLM (Ollama + deepseek-r1:14b) via CrewAI agents
Compose structured GitHub Issues with root cause and suggested fixes
File Issues automatically to your repo — skipping duplicates
All processing happens locally on your machine. Raw log content never leaves your system.
Architecture
Claude Desktop / Cursor / LangChain
↓ MCP (stdio or HTTP+SSE)
MCP Log Analyzer Server
↓
ripgrep pre-filter (2-4s on 500MB)
↓
mmap streaming parser + deduplicator
↓
CrewAI agents → Ollama (local LLM)
↓
GitHub Issues APIRequirements
Requirement | Version | Notes |
Python | 3.11+ | 3.14 not supported |
Ollama | Latest |
|
deepseek-r1:14b | — | ~9GB download |
ripgrep | Latest |
|
RAM | 16GB min | 32GB recommended |
macOS | Ventura 13+ | Apple Silicon recommended |
Quick Start
1. Install system dependencies
brew install ollama ripgrep
brew services start ollama
ollama pull deepseek-r1:14b # ~9GB — start this first2. Clone and set up Python environment
git clone https://github.com/YOUR_ORG/mcp-log-analyzer
cd mcp-log-analyzer
/opt/homebrew/bin/python3.11 -m venv .venv
source .venv/bin/activate
pip install --upgrade pip
pip install mcp "crewai>=0.80.0" crewai-tools langchain-ollama \
litellm fastapi uvicorn httpx httpx-sse \
structlog loguru pydantic python-dotenv \
tenacity rich typer3. Configure environment
cp .env.example .env
nano .env # fill in your valuesGITHUB_PAT=ghp_your_token_here
GITHUB_REPO_OWNER=your-username
GITHUB_REPO_NAME=your-repo
OLLAMA_BASE_URL=http://localhost:11434
OLLAMA_MODEL=deepseek-r1:14b
CREWAI_TELEMETRY_OPT_OUT=true
OTEL_SDK_DISABLED=true
OLLAMA_KEEP_ALIVE=-14. Create a GitHub PAT
Go to: github.com → Settings → Developer settings → Personal access tokens → Tokens (classic)
Enable scope: repo (full)
5. Register with Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"mcp-log-analyzer": {
"command": "/path/to/mcp-log-analyzer/.venv/bin/python",
"args": ["/path/to/mcp-log-analyzer/mcp_server/server.py"],
"env": {
"GITHUB_PAT": "ghp_your_token",
"GITHUB_REPO_OWNER": "your-username",
"GITHUB_REPO_NAME": "your-repo",
"OLLAMA_BASE_URL": "http://localhost:11434",
"OLLAMA_MODEL": "deepseek-r1:14b"
}
}
}
}Restart Claude Desktop. You should see the 🔨 tools icon appear.
Usage
Via Claude Desktop (natural language)
analyze the log file at /var/log/app.log and file GitHub issues for any errorsuse analyze_log_file with path="/var/log/app.log" dry_run=truecheck status of job abc12345Via Python CLI
source .venv/bin/activate
python3 -c "
from dotenv import load_dotenv
load_dotenv()
from mcp_server.tools.analyze_tool import analyze_log_file
import asyncio, json
result = asyncio.run(analyze_log_file({
'path': '/var/log/app.log',
'severity': 'ERROR',
'dry_run': False
}))
print(result[0].text)
"MCP Tools Reference
ping
Health check — verifies the server and Ollama are running.
{}Returns: "mcp-log-analyzer online — Ollama: deepseek-r1:14b"
analyze_log_file
Start async log analysis. Returns a job ID immediately — pipeline runs in background.
Parameter | Type | Required | Default | Description |
| string | ✅ | — | Absolute path to log file |
| string | — |
| Minimum severity: |
| boolean | — |
| Preview issues without filing to GitHub |
Returns:
{
"job_id": "abc12345",
"status": "started",
"message": "Analysis started. Check progress with get_job_status('abc12345')."
}get_job_status
Check the status of a running analysis job.
Parameter | Type | Required | Description |
| string | ✅ | Job ID returned by analyze_log_file |
Returns (running):
{
"status": "running",
"job_id": "abc12345",
"lines_filtered": 487,
"chunks": 1
}Returns (done):
{
"status": "done",
"job_id": "abc12345",
"lines_filtered": 487,
"unique_events": 4,
"chunks": 1,
"issues_filed": 2,
"github_issues": [
{
"title": "[CRITICAL][minting-service] DB connection pool exhausted (x117)",
"url": "https://github.com/your-org/your-repo/issues/42",
"number": 42
}
]
}Compatible MCP Clients
Client | Transport | Config |
Claude Desktop | stdio |
|
Claude Code CLI | stdio |
|
Cursor | stdio or HTTP+SSE |
|
LangChain | HTTP+SSE |
|
n8n | HTTP+SSE | HTTP Request node → SSE |
HTTP+SSE Transport (for Cursor, LangChain, n8n)
python mcp_server/server.py --transport sse --port 8000Customising with Skills
Skills are plain English .md files that teach the agents your stack's error patterns. Three built-in skills ship with the project:
Skill | Purpose |
| NFT/blockchain error classification |
| Infrastructure error classification |
| GitHub Issue format rules |
Writing your own skill
Create skills/my-stack-errors.skill.md:
# My Stack Error Classification
## CRITICAL — file bug immediately
- "FATAL: database connection refused" = service down
- "out of memory" = process crash imminent
## HIGH — file bug, non-urgent
- "connection timeout" on external API = degraded performance
## IGNORE — known false positives
- "reconnecting..." during deploys = expectedThen load it in agents/crew.py:
_load_skill("my-stack-errors.skill.md")Pipeline Internals
500MB log file
↓ ripgrep (2-4 seconds)
↓ Filters: ERROR|FATAL|CRITICAL|WARN|Exception|Traceback
~5MB of error lines
↓ mmap streaming parser
↓ LogEvent objects with timestamp, level, component, message
↓ Deduplicator (fingerprints strip req_id, numbers, hex)
4-20 unique error patterns
↓ Chunker (10 events per chunk, CRITICAL first)
1-3 chunks
↓ Single CrewAI agent → Ollama (local)
↓ Structured bug reports in markdown
↓ Title extractor + label classifier
↓ Duplicate check via GitHub search API
GitHub Issues filedPerformance
Tested on Apple Silicon (M2, 32GB):
File size | Filter time | Analysis time | Total |
10MB | <1s | 3-5 min | ~5 min |
100MB | 1-2s | 3-5 min | ~7 min |
500MB | 3-5s | 5-10 min | ~15 min |
Analysis time depends on number of unique error patterns found (not file size).
Troubleshooting
Symptom | Fix |
| Run |
MCP server disconnected in Claude Desktop | Check |
| Verify |
Timeout after 600s | Add |
| Requires Python 3.11 — not compatible with 3.13/3.14 |
Permission denied on | Use |
Roadmap
v1 (current)
Local filesystem log ingestion
ripgrep + mmap pipeline
Single-agent CrewAI analysis
GitHub Issues filing with dedup
Claude Desktop + stdio MCP transport
v2 (planned)
Datadog MCP integration
Splunk MCP integration
HTTP+SSE transport (Cursor, LangChain, n8n)
Scheduled analysis triggers
Parallel chunk processing
Web dashboard for job history
Contributing
Contributions welcome — especially new skill files for different stacks.
Fork the repo
Create
skills/your-stack-errors.skill.mdTest it against a real log file
Open a PR with example output
License
MIT — see LICENSE
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mashish/nft-log-analyzer'
If you have feedback or need assistance with the MCP directory API, please join our Discord server