Logclaw MCP server
io.github.RobelDev/logclaw-mcp-server·v1.0.4·79 starsConnect AI coding tools to LogClaw incidents, logs, and anomaly detections.
79 stars38 downloads/wk
Reviews
Write oneNobody has reviewed Logclaw yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Logclaw tools (6, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
logclaw_get_anomaliesGet recent anomaly detections. Anomalies are auto-detected using Z-score analysis on error rates. Returns score, detection mode, service.
logclaw_get_incidentGet full incident details including root cause, causal chain, evidence logs, traces, timeline, blast radius, and suggested fix.
logclaw_list_incidentsList and filter LogClaw incidents. Returns summaries with ID, title, severity, state, service, timestamps.
logclaw_search_logsSearch raw logs in LogClaw. Filter by service, level, time range, and query. Returns entries with timestamp, service, level, message, trace_id.
logclaw_service_healthCheck the health status of LogClaw pipeline services (ticketing agent, etc). Returns status and latency.
logclaw_update_incidentwrite actionTransition an incident state (acknowledge, investigate, mitigate, resolve) or add a timeline note.
Public scan report
scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it
- Code scan11 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 139 days ago8/15
- Maintainer identitynamespace and repository owner differ4/10
How Logclaw compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 45% of 48,255 servers
- Tools
- 6
- the typical server has 7
- Tools that change things
- 17%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 79
- more than 95% of 28,688 servers
- Downloads a week
- 38
- more than 29% of 12,191 servers with a package
What its tools let an agent do: 5 read · 1 change
Install Logclaw in Claude Code, Cursor or VS Code
Runs npx -y logclaw-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add logclaw-mcp-server -- npx -y logclaw-mcp-server
What the publisher says
From the Logclaw repository's README, as published. We do not edit it. Read it on GitHub
LogClaw
AI SRE that deploys in your VPC. Real-time anomaly detection, trace-correlated incident tickets, and AI root cause analysis — your logs never leave your infrastructure.
TL;DR — Try It
Option A: Managed Cloud (no install — fastest)
Try the full experience instantly at console.logclaw.ai — includes AI root cause analysis, API key management, multi-tenant isolation, and the complete incident pipeline. No Docker required.
Option B: Docker Compose (self-hosted, no Kubernetes)
curl -O https://raw.githubusercontent.com/logclaw/logclaw/main/docker-compose.yml
curl -O https://raw.githubusercontent.com/logclaw/logclaw/main/otel-collector-config.yaml
docker compose up -dOpen http://localhost:3000 — the LogClaw stack is running:
- Dashboard (:3000) — incidents, log ingestion, config
- OTel Collector (:4317 gRPC, :4318 HTTP) — send logs via OTLP
- Bridge (:8080) — anomaly detection + trace correlation
- Ticketing Agent (:18081) — AI-powered incident management
- OpenSearch (:9200) — log storage + search
- Kafka (:9092) — event bus
All images are pulled from ghcr.io/logclaw/ — no registry auth required.
Note: The local stack runs in single-tenant mode with LLM-powered root cause analysis disabled. For AI RCA, API key management, and multi-tenant isolation, use the managed cloud or deploy to Kubernetes with LLM_PROVIDER=claude|openai|ollama.
Option C: Kind Cluster (full Kubernetes stack)
git clone https://github.com/logclaw/logclaw.git && cd logclaw
./scripts/setup-dev.shThis creates a Kind cluster, installs all operators and services, builds the dashboard, and runs a smoke test. Takes ~20 minutes on a 16 GB laptop.
Container Images
All LogClaw images are published to GHCR as public packages:
Pull any image directly:
docker pull ghcr.io/logclaw/logclaw-dashboard:stableSee It in Action
Incident Management AI Root Cause Analysis Log Ingestion Dashboard Overview
Live demo: console.logclaw.ai | Video walkthrough: logclaw.ai
Open Source vs Cloud vs Enterprise
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Logclaw: common questions
- Is Logclaw MCP server safe?
- Mostly: it is graded B (75/100). Read the Logclaw safety report
- How do I install Logclaw?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Logclaw need an API key?
- No secret keys are declared. It reads 2 settings from the environment.
- Is Logclaw maintained?
- The last commit was 177 days ago (2026-05-11). The latest release is v1.0.4.
- What can I use instead of Logclaw?
- Servers from other publishers that do the same job: Netdata MCP server.
- How does Logclaw compare with other MCP servers?
- safety score 75/100 (higher than 45% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Logclaw
Same job from other publishers: the closest match first, then the best rated.
- NetdataReal-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.not reviewedWidely usedA