Connect AI coding tools to LogClaw incidents, logs, and anomaly detections.
Connect AI coding tools to LogClaw incidents, logs, and anomaly detections. Exposed over MCP by the logclaw mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
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.
Everything the assistant can do here goes through one of these:
Prerequisites — The Prerequisites tool exposed by this serverDashboard — The Dashboard provides: - Dark mode — system-aware with manual toggle (Light/Dark/System), persisted in localStorage - Drag-and-drop uploadYou will need 4 environment variables: KAFKA_BROKERS, OPENSEARCH_ENDPOINT, TENANT_ID, LOGCLAW_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
One-time cluster setup (operators, run once per cluster):
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Logclaw's toolset — Prerequisites, Dashboard — is a fair guide to whether it matches your workflow. It is maintained by RobelDev; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Dashboard | The Dashboard provides: - **Dark mode** — system-aware with manual toggle (Light/Dark/System), persisted in localStorage - **Drag-and-drop upload** supporting JSON, NDJSON, CSV, and plain text files - **Bulk incident act |
{
"mcpServers": {
"logclaw": {
"command": "npx",
"args": ["-y", "logclaw-mcp-server"],
"env": {
"KAFKA_BROKERS": "your-value",
"OPENSEARCH_ENDPOINT": "your-value",
"TENANT_ID": "your-value",
"LOGCLAW_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
One-time cluster setup (operators, run once per cluster):
| Variable | Description | Required |
|---|---|---|
| KAFKA_BROKERS | Configuration value read at startup. | Optional |
| OPENSEARCH_ENDPOINT | Configuration value read at startup. | Optional |
| TENANT_ID | Configuration value read at startup. | Optional |
| LOGCLAW_API_KEY | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.