Logclaw MCP Server

Name: Logclaw MCP Server
Author: logclaw

by logclawversion 1.0.4i★ 79 (Stars belong to another repo)iRuns on your computer

Registry nameio.github.RobelDev/logclaw-mcp-server

How to install

What it does

Connect AI coding tools to LogClaw incidents, logs, and anomaly detections.

Connects Runs on your computer
Account or key Needs LOGCLAW_API_KEY
Category Developer tools

Install

Pick the AI app you use, then copy the settings.

Passed 0/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

ClaudeWeb · app · phoneChatGPTWebClaude CodeTerminalCursorCode editorVS CodeCode editorOtherOther apps

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Logclaw MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Logclaw MCP Server for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "logclaw": { "command": "npx", "args": [ "-y", "logclaw-mcp-server" ], "env": { "LOGCLAW_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For LOGCLAW_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Logclaw MCP Server tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

1
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v
- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Done
Sign up and create a Logclaw MCP Server key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Done
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Done

Paste these settings and save the file

{
  "mcpServers": {
    "logclaw": {
      "command": "npx",
      "args": [
        "-y",
        "logclaw-mcp-server"
      ],
      "env": {
        "LOGCLAW_API_KEY": "your-value"
      }
    }
  }
}

Paste the key only into the app’s field, never into a chat or to anyone

Done

Quit Claude and open it again
Done
Try it
Use Logclaw MCP Server and tell me what you can do for me, then show me one thing
✓ If Claude says it is using Logclaw MCP Server or shows a Logclaw MCP Server tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

LOGCLAW_ENDPOINT LogClaw auth proxy endpoint (default: https://ticket.logclaw.ai)

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Logclaw MCP Server yet

Logclaw MCP Server runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Logclaw MCP Server

Steps for Claude →You need a Logclaw MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Steps for Claude Code →You need a Logclaw MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Steps for Cursor →You need a Logclaw MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Steps for VS Code →You need a Logclaw MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Sentry✓ ChatGPT
Compiler Explorer✓ ChatGPT
GitDiagram✓ ChatGPT

Works with Claude Code, with some setup first

You need a Logclaw MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Logclaw MCP Server for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user logclaw --env LOGCLAW_API_KEY=your-value -- npx -y logclaw-mcp-server 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For LOGCLAW_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Logclaw MCP Server tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

1
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v
- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Done
Sign up and create a Logclaw MCP Server key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Done
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Done
4
Paste this command and press Enter
```
claude mcp add --scope user logclaw --env LOGCLAW_API_KEY=your-value -- npx -y logclaw-mcp-server
```
Replace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
Done
Type /mcp in Claude Code
You should see Logclaw MCP Server listed as connected
Done
Try it
Use Logclaw MCP Server and tell me what you can do for me, then show me one thing
✓ If Claude Code says it is using Logclaw MCP Server or shows a Logclaw MCP Server tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

LOGCLAW_ENDPOINT LogClaw auth proxy endpoint (default: https://ticket.logclaw.ai)

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Logclaw MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Logclaw MCP Server for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "logclaw": { "command": "npx", "args": [ "-y", "logclaw-mcp-server" ], "env": { "LOGCLAW_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For LOGCLAW_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Logclaw MCP Server tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

1
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v
- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Done
Sign up and create a Logclaw MCP Server key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Done
Click this button to open Cursor
Open in Cursor
Cursor asks you to confirm; click Install
Done
Fill in your key
In the Logclaw MCP Server settings, LOGCLAW_API_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Done
Open the AI chat in Cursor in Agent mode
Done
Try it
Use Logclaw MCP Server and tell me what you can do for me, then show me one thing
✓ If Cursor says it is using Logclaw MCP Server or shows a Logclaw MCP Server tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

LOGCLAW_ENDPOINT LogClaw auth proxy endpoint (default: https://ticket.logclaw.ai)

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Logclaw MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Logclaw MCP Server for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "logclaw": { "type": "stdio", "command": "npx", "args": [ "-y", "logclaw-mcp-server" ], "env": { "LOGCLAW_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For LOGCLAW_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Logclaw MCP Server tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

1
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v
- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Done
Sign up and create a Logclaw MCP Server key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Done
Click this button to open VS Code
Open in VS Code
VS Code asks you to confirm; click Install
Done
Fill in your key
In the Logclaw MCP Server settings, LOGCLAW_API_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Done
Open the AI chat in VS Code in Agent mode
Done
Try it
Use Logclaw MCP Server and tell me what you can do for me, then show me one thing
✓ If VS Code says it is using Logclaw MCP Server or shows a Logclaw MCP Server tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

LOGCLAW_ENDPOINT LogClaw auth proxy endpoint (default: https://ticket.logclaw.ai)

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Logclaw MCP Server💬 Discussion →

For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user logclaw --env LOGCLAW_API_KEY=your-value -- npx -y logclaw-mcp-server

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "logclaw": {
      "command": "npx",
      "args": [
        "-y",
        "logclaw-mcp-server"
      ],
      "env": {
        "LOGCLAW_API_KEY": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "logclaw": {
      "command": "npx",
      "args": [
        "-y",
        "logclaw-mcp-server"
      ],
      "env": {
        "LOGCLAW_API_KEY": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "logclaw": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "logclaw-mcp-server"
      ],
      "env": {
        "LOGCLAW_API_KEY": "your-value"
      }
    }
  }
}

Values you fill in

LOGCLAW_API_KEY secret required env
Your LogClaw project API key (starts with lc_proj_)
LOGCLAW_ENDPOINT env
LogClaw auth proxy endpoint (default: https://ticket.logclaw.ai)

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

GitHub stars i: 79 (Stars belong to another repo)
This listing points to someone else’s repo, so its stars are not counted in rankings
Downloads per weeki: 56/wk
Licence i: No licence stated
Connection: Runs on your computer
Transport: stdio
Latest versioni: 1.0.4
Categoryi: Developer tools
Published to registryi: Mar 11, 2026
Code last changedi: May 12, 2026
Maker: logclaw
Packages: npm: logclaw-mcp-server
Repo: logclaw/logclaw
Registry status: Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

Claude Goose LM Studio Msty Studio Cherry Studio Cursor VS Code + GitHub Copilot Visual Studio Windsurf (Devin Desktop)Zed Kiro Cline Continue JetBrains AI Assistant Claude Code Codex CLI Gemini CLI OpenCode nodecode Warp LibreChat Raycast

All apps, with pros and cons →

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 15, 2026

! Caution
Maker matches the repo
The publisher (RobelDev) is not the repo owner (logclaw); someone else may have listed it
! Caution
Still maintained
Code last changed 6 months ago, more than 6 months ago
✕ Fail
Has a licence
No licence file found in the repo
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked yet

What we check → · JSON

Makers: ask for a re-check or report wrong info

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

User reviews

No reviews yet

Compared with others in Developer toolsi

More stars than 0% of the other 5911 servers in this category
Published to the registry more recently than 5% of the other 5911 servers in this category
Basic checks equal to or better than 4% of the other 5911 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Logclaw MCP Server safe?

It passed 0 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: LOGCLAW_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 6 months ago, and the latest version (1.0.4) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

by ahmedkhaleel2004Widely used★ 18.9KUpdated 2 months ago

Runs in the cloud✓ service owner · gitdiagram.comTried by the PopNx team

How to connect

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

by AppllamaWidely used★ 5.2KUpdated 3 months ago

Runs in the cloud✓ service owner · appllama.io

How to connect

Cloudflare MCP

Cloudflare MCP servers

by cloudflareWidely used★ 4.5KUpdated 14 months ago

Runs in the cloud✓ service owner · mcp.cloudflare.comTried by the PopNx team

How to connect

Omnara

Deploy durable AI agents with Omnara, an open-source managed-agent platform.

by omnara-aiWidely used★ 3.4KUpdated 2 months ago

Runs in the cloud✓ service owner · omnara.com

How to connect

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

by repowise-devWidely used↓ 6.5K/wk★ 8.1K Stars for the whole repoUpdated 2 days ago

Computer or cloud✓ service owner · repowise.dev

Install

GitDiagram — Runs in the cloud, nothing to install · No key needed
Appllama — Runs in the cloud, nothing to install · No key needed
Cloudflare MCP — Runs in the cloud, nothing to install · No key needed · In Claude’s directory
Omnara — Runs in the cloud, nothing to install · No key needed
Repowise — Cloud or install on your computer · No key needed

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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](https://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 -d

Open 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.sh

This 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:

Service	Image	Latest Stable
Dashboard	`ghcr.io/logclaw/logclaw-dashboard`	`stable` / `2.5.0`
Bridge	`ghcr.io/logclaw/logclaw-bridge`	`stable` / `1.3.0`
Ticketing Agent	`ghcr.io/logclaw/logclaw-ticketing-agent`	`stable` / `1.5.0`
Flink Jobs	`ghcr.io/logclaw/logclaw-flink-jobs`	`stable` / `0.1.1`

Pull any image directly:

docker pull ghcr.io/logclaw/logclaw-dashboard:stable

See 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

Capability	Open Source (free)	Cloud ($0.30/GB)	Enterprise (custom)
Log Ingestion (OTLP)	Unlimited	1 GB/day free	Unlimited
Anomaly Detection	Z-score statistical	Z-score + ML pipeline	Z-score + ML + custom models
AI Root Cause Analysis	BYO LLM (Ollama/OpenAI/Claude)	Included	Included + fine-tuned models
Incident Ticketing	PagerDuty, Jira, ServiceNow, OpsGenie, Slack, Zammad	All 6 platforms	All 6 + custom connectors
Dashboard	Full UI (logs, incidents, config)	Full UI + hosted	Full UI + white-label option
Authentication	None (open access)	Clerk OAuth + org management	SSO (SAML/OIDC) + RBAC
Multi-tenancy	Single tenant	Multi-org, multi-project, multi-env	Full namespace isolation per tenant
API Keys	N/A	Per-project, SHA-256 hashed, revocable	Per-project + custom scoping
Data Residency	Your infrastructure	LogClaw-managed cloud	Your VPC (AWS/Azure/GCP)
Secrets Encryption	At rest (OpenSearch)	At rest + in transit	AES-256-GCM for secrets + full TLS
Config Management	Env vars	6-tab settings UI	UI + API + GitOps
Retention	Configurable via Helm	9-day logs, 97-day incidents	Custom retention policies
Air-Gapped Mode	Yes (Zammad + Ollama)	No	Yes
MCP Server	Self-hosted	Hosted (mcp.logclaw.ai)	Both
Support	GitHub Issues	Email (support@logclaw.ai)	Dedicated SRE team + SLA
Pricing	Free forever (Apache 2.0)	$0.30/GB ingested	Custom

No per-seat fees. No per-host fees. AI features included at every tier.

Start Free (Cloud) | Deploy from GitHub (OSS) | Book a Demo (Enterprise)

Architecture

All components below are included in every tier — Open Source, Cloud, and Enterprise.

LogClaw Stack (per tenant, namespace-isolated)

│ ├── logclaw-auth-proxy API key validation + tenant ID injection ├── logclaw-otel-collector OpenTelemetry Collector (OTLP gRPC + HTTP) ├── logclaw-ingestion Vector.dev edge ingestion (optional) ├── logclaw-kafka Strimzi Kafka 3-broker KRaft cluster ├── logclaw-flink ETL + enrichment + anomaly scoring ├── logclaw-opensearch OpenSearch cluster (hot-tier log storage) ├── logclaw-bridge OTLP ETL + trace correlation + lifecycle manager ├── logclaw-ml-engine Feast Feature Store + KServe/TorchServe + Ollama ├── logclaw-airflow Apache Airflow (ML training DAGs) ├── logclaw-ticketing-agent AI-powered RCA + multi-platform ticketing ├── logclaw-agent In-cluster infrastructure health collector ├── logclaw-dashboard Next.js web UI (ingestion, incidents, config, dark mode) └── logclaw-console Enterprise SaaS console (multi-tenant)

Data flow: Logs → Auth Proxy (API key + tenant injection) → OTel Collector (OTLP ingestion) → Kafka → Bridge (ETL + anomaly + trace correlation) → OpenSearch + Ticketing Agent → Incident tickets

All charts are wired together by the `logclaw-tenant` umbrella chart — a single helm install deploys the full stack for one tenant.

Quick Start (Production / ArgoCD)

Prerequisites

One-time cluster setup (operators, run once per cluster):

helmfile -f helmfile.d/00-operators.yaml apply

Onboard a new tenant

Copy the template:

   cp gitops/tenants/_template.yaml gitops/tenants/tenant-<id>.yaml

Fill in the required values (tenantId, tier, cloudProvider, secret store config).

Commit and push — ArgoCD will detect the new file and deploy the full stack in ~30 minutes.

Manual install (dev/staging)

helm install logclaw-acme charts/logclaw-tenant \

--namespace logclaw-acme \ --create-namespace \ -f gitops/tenants/tenant-acme.yaml

Running Locally (Step by Step)

Prefer the one-command setup? Run ./scripts/setup-dev.sh and skip to Step 6.

Prerequisites

# macOS (Homebrew)

brew install helm helmfile kind kubectl node python3

Helm plugins

helm plugin install https://github.com/databus23/helm-diff helm plugin install https://github.com/helm-unittest/helm-unittest

Docker Desktop must be running

open -a Docker

1 — Create a local Kubernetes cluster

make kind-create

Verify:

kubectl cluster-info --context kind-logclaw-dev

2 — Install cluster-level operators

make install-operators

Wait for operators to be ready (~3 min):

kubectl get pods -n strimzi-system -w

kubectl get pods -n opensearch-operator-system -w

3 — Install the full tenant stack

make install TENANT_ID=dev-local STORAGE_CLASS=standard

This deploys all 16 helmfile releases in dependency order. Monitor progress:

watch kubectl get pods -n logclaw-dev-local

Time	Milestone
T+2 min	Namespace, RBAC, NetworkPolicies
T+6 min	Kafka broker ready
T+10 min	OpenSearch cluster green
T+15 min	Bridge + Ticketing Agent running
T+20 min	Full stack operational

4 — Build and deploy the Dashboard

The dashboard requires a Docker image build:

docker build -t logclaw-dashboard:dev apps/dashboard/

kind load docker-image logclaw-dashboard:dev --name logclaw-dev

helm upgrade --install logclaw-dashboard-dev-local charts/logclaw-dashboard \ --namespace logclaw-dev-local \ --set global.tenantId=dev-local \ -f charts/logclaw-dashboard/ci/default-values.yaml

5 — Access the services

# Dashboard (main UI)

kubectl port-forward svc/logclaw-dashboard-dev-local 3333:3000 -n logclaw-dev-local open http://localhost:3333

OpenSearch (query API)

kubectl port-forward svc/logclaw-opensearch-dev-local 9200:9200 -n logclaw-dev-local

Airflow (ML pipelines)

kubectl port-forward svc/logclaw-airflow-dev-local-webserver 8080:8080 -n logclaw-dev-local open http://localhost:8080 # admin / admin

6 — Send logs

LogClaw ingests logs via OTLP (OpenTelemetry Protocol) — the CNCF industry standard. Port-forward the OTel Collector:

kubectl port-forward svc/logclaw-otel-collector-dev-local 4318:4318 -n logclaw-dev-local &

Send a single log via OTLP HTTP:

curl -X POST http://localhost:4318/v1/logs \

-H "Content-Type: application/json" \ -d '{ "resourceLogs": [{ "resource": { "attributes": [ {"key": "service.name", "value": {"stringValue": "payment-api"}} ] }, "scopeLogs": [{ "logRecords": [{ "timeUnixNano": "'$(date +%s)000000000'", "severityText": "ERROR", "body": {"stringValue": "Connection refused to database"}, "traceId": "abcdef1234567890abcdef1234567890", "spanId": "abcdef12345678" }] }] }] }'

Any OpenTelemetry SDK or agent can send logs to LogClaw — no custom integration needed. See OTLP Integration Guide for SDK examples.

Generate and ingest 900 sample Apple Pay logs:

# Generate sample OTel logs

python3 scripts/generate-applepay-logs.py # → 500 payment flow logs python3 scripts/generate-applepay-logs-2.py # → 400 infra/security errors

Ingest them

./scripts/ingest-logs.sh scripts/applepay-otel-500.json ./scripts/ingest-logs.sh scripts/applepay-otel-400-batch2.json

Or use the helper script:

./scripts/ingest-logs.sh --generate   # generates + ingests all sample logs

./scripts/ingest-logs.sh --smoke # single test log

7 — See it in action

After ingesting error logs, the Bridge detects anomalies and the Ticketing Agent creates incident tickets. View them:

# Watch Bridge trace correlation in real-time

kubectl logs -f deployment/logclaw-bridge-dev-local -n logclaw-dev-local

Check auto-created incidents

kubectl port-forward svc/logclaw-opensearch-d

Only the beginning is shown; read the rest in the repo

Logclaw MCP Server

What it does

Install

Install Node.js (if you don’t have it)

Sign up and create a Logclaw MCP Server key

Open the Claude desktop app’s settings file

Paste these settings and save the file

Quit Claude and open it again

Try it

What you can do instead

Install Node.js (if you don’t have it)

Sign up and create a Logclaw MCP Server key

Open Terminal

Paste this command and press Enter

Type /mcp in Claude Code

Try it

Install Node.js (if you don’t have it)

Sign up and create a Logclaw MCP Server key

Click this button to open Cursor

Fill in your key

Open the AI chat in Cursor in Agent mode

Try it

Install Node.js (if you don’t have it)

Sign up and create a Logclaw MCP Server key

Click this button to open VS Code

Fill in your key

Open the AI chat in VS Code in Agent mode

Try it

Installed on your computer

Values you fill in

At a glance

Which apps can use it

Related guides

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Published vulnerabilities (OSV.dev)

Discussion

User reviews

Compared with others in Developer toolsi

Common questions

Similar alternatives

GitDiagram

Appllama

Cloudflare MCP

Omnara

Repowise

README from the maker

LogClaw

TL;DR — Try It

Option A: Managed Cloud (no install — fastest)

Option B: Docker Compose (self-hosted, no Kubernetes)

Option C: Kind Cluster (full Kubernetes stack)

Container Images

See It in Action

Open Source vs Cloud vs Enterprise

Architecture

Quick Start (Production / ArgoCD)

Prerequisites

Onboard a new tenant

Manual install (dev/staging)

Running Locally (Step by Step)

Prerequisites

Helm plugins

Docker Desktop must be running

1 — Create a local Kubernetes cluster

2 — Install cluster-level operators

3 — Install the full tenant stack

4 — Build and deploy the Dashboard

5 — Access the services

OpenSearch (query API)

Airflow (ML pipelines)

6 — Send logs

Ingest them

7 — See it in action