Logclaw Mcp Server

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.

[图片] [图片] [图片] [图片] [图片]

[LogClaw Dashboard — real-time log monitoring with AI anomaly detection]

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.ymlcurl -O https://raw.githubusercontent.com/logclaw/logclaw/main/otel-collector-config.yamldocker 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:

Pull any image directly:

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

See It in Action

Live demo: console.logclaw.ai | Video walkthrough: logclaw.ai

Open Source vs Cloud vs Enterprise

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

1. Copy the template:

   bash

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

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

3. 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 pluginshelm plugin install https://github.com/databus23/helm-diffhelm plugin install https://github.com/helm-unittest/helm-unittest
# Docker Desktop must be runningopen -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 -wkubectl 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

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-localopen 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-localopen 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 logspython3 scripts/generate-applepay-logs.py    # → 500 payment flow logspython3 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-timekubectl logs -f deployment/logclaw-bridge-dev-local -n logclaw-dev-local
# Check auto-created incidentskubectl port-forward svc/logclaw-opensearch-dev-local 9200:9200 -n logclaw-dev-local &curl -s 'http://localhost:9200/logclaw-incidents-*/_search?size=5&sort=created_at:desc' | python3 -m json.tool
# Or use the Dashboardopen http://localhost:3333/incidents

8 — Tear down

# Remove just the tenantmake uninstall TENANT_ID=dev-local
# Remove everything including the Kind clustermake kind-delete

Repository Layout

charts/├── logclaw-tenant/           # Umbrella chart — single install entry point├── logclaw-auth-proxy/       # API key validation + tenant ID injection├── logclaw-otel-collector/   # OpenTelemetry Collector (OTLP gRPC + HTTP)├── logclaw-ingestion/        # Vector.dev edge ingestion├── logclaw-kafka/            # Strimzi Kafka + KafkaConnect + MirrorMaker2├── logclaw-flink/            # Flink ETL + enrichment + anomaly jobs├── logclaw-opensearch/       # OpenSearch cluster via Opster operator├── logclaw-bridge/           # OTLP ETL + trace correlation + lifecycle manager├── logclaw-ml-engine/        # Feast + KServe/TorchServe + Ollama├── logclaw-airflow/          # Apache Airflow├── logclaw-ticketing-agent/  # AI-powered RCA + multi-platform ticketing├── logclaw-agent/            # In-cluster infrastructure health agent├── logclaw-dashboard/        # Next.js web UI└── logclaw-console/          # Enterprise SaaS console
apps/├── bridge/                # Python — OTLP ETL + anomaly detection + trace correlation├── agent/                 # Go — infrastructure health collector├── dashboard/             # Next.js — web UI (incidents, logs, config, dark mode)├── ticketing-agent/       # Python — AI-powered RCA + multi-platform ticketing├── flink-jobs/            # Java — Flink stream processing jobs├── logclaw-auth-proxy/    # TypeScript/Express — API key validation + tenant injection├── logclaw-slack-bot/     # TypeScript/Hono — Slack incident bot (Cloudflare Workers)├── logclaw-mcp-server/    # TypeScript — MCP server for AI coding tools (8 tools)└── logclaw-mcp-remote/    # TypeScript — remote MCP client (OAuth 2.1)
cli/                        # Go CLI (logclaw start/stop/status)
scripts/├── setup-dev.sh                # One-command local dev setup (Kind cluster)├── setup-gke.sh                # GKE production cluster setup├── ingest-logs.sh              # Log ingestion helper (--generate, --smoke)├── generate-applepay-logs.py   # Generate 500 OTel sample logs (batch 1)├── generate-applepay-logs-2.py # Generate 400 infra/security logs (batch 2)├── trigger-anomaly.sh          # Trigger test anomaly for demo└── trigger-request-failure.sh  # Trigger test request failure for demo
operators/                    # Cluster-level operator bootstrap (once per cluster)├── strimzi/                  # strimzi-kafka-operator 0.41.0├── flink-operator/           # flink-kubernetes-operator 1.9.0├── opensearch-operator/      # opensearch-operator 2.6.1├── eso/                      # external-secrets 0.10.3└── cert-manager/             # cert-manager v1.16.1
helmfile.d/                   # Ordered helmfile releases (00-operators → 90-dashboard)gitops/                       # ArgoCD ApplicationSet + per-tenant value filestests/                        # Helm chart tests + integration test podsdocs/                         # Architecture, onboarding, values reference

Key Features

For a side-by-side comparison across tiers, see Open Source vs Cloud vs Enterprise above.

Trace-Correlated AI Ticket Engine

The Bridge runs a 5-layer trace correlation engine:

1. ETL Consumer — Consumes enriched logs from Kafka
2. Anomaly Detector — Statistical anomaly scoring on error rates
3. OpenSearch Indexer — Indexes logs for search and correlation
4. Lifecycle Engine — Traces causal chains across services, computes blast radius, creates/deduplicates incidents

When an anomaly is detected, the system:

• Queries all logs sharing the same trace_id
• Builds a causal chain showing error propagation across services
• Computes blast radius (% of services affected)
• Creates a deduplicated incident ticket with full trace context

Multi-Platform Ticketing

The logclaw-ticketing-agent supports 6 independently-toggleable platforms simultaneously:

Per-severity routing (critical → PagerDuty, medium → Jira, etc.) is configurable via config.routing.*.

Air-Gapped Mode

When paired with Zammad (external ITSM chart) and Ollama for local LLM inference, the needsExternalHttps helper sets the NetworkPolicy to zero external egress — fully air-gapped. No logs, tickets, or model calls leave the cluster.

LLM Provider Abstraction

global:  llm:    provider: ollama   # claude | openai | ollama | vllm | disabled    model: llama3.2:8b

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 actions — select multiple incidents and acknowledge/resolve/escalate in batch
• CSV export — download incidents as a CSV file
• Loading skeletons — smooth animated placeholders during data fetches
• Error boundaries — graceful crash recovery with retry UI
• LLM fallback badge — indicates when AI RCA is unavailable and rule-based fallback was used
• Incident auto-deduplication — prevents duplicate incidents for the same anomaly

Log Ingestion — OTLP Native

LogClaw uses OTLP (OpenTelemetry Protocol) as its sole ingestion protocol — the CNCF industry standard supported by every major observability vendor (Datadog, Splunk, Grafana, AWS, GCP, Azure).

Supported transports:

• gRPC — <collector>:4317 (recommended for high-throughput)
• HTTP/JSON — <collector>:4318/v1/logs

Any OpenTelemetry SDK, agent, or collector can send logs directly to LogClaw without custom integrations. The OTel Collector enriches each log with tenant_id, batches them, and writes to Kafka using otlp_json encoding.

{  "resourceLogs": [{    "resource": {      "attributes": [        {"key": "service.name", "value": {"stringValue": "my-service"}},        {"key": "host.name", "value": {"stringValue": "my-service-pod-abc12"}}      ]    },    "scopeLogs": [{      "logRecords": [{        "timeUnixNano": "1709510400000000000",        "severityText": "ERROR",        "body": {"stringValue": "Something went wrong"},        "traceId": "abcdef1234567890abcdef1234567890",        "spanId": "abcdef12345678",        "attributes": [          {"key": "environment", "value": {"stringValue": "production"}}        ]      }]    }]  }]}

See OTLP Integration Guide for Python, Java, and Node.js SDK examples.

MCP Server — AI Coding Tools

The logclaw-mcp-server connects AI coding tools to LogClaw incidents, logs, and anomalies via the Model Context Protocol. Published as an npm package with 8 tools.

npx logclaw-mcp-server

Works with Claude Code, Cursor, Windsurf, and any MCP-compatible client. Also available as a hosted server at https://mcp.logclaw.ai (OAuth 2.1, no install needed).

See MCP Integration Guide for setup instructions.

Slack Bot — Incident Notifications

The logclaw-slack-bot delivers real-time incident notifications to Slack with rich Block Kit formatting, DM support, and OAuth. Runs on Cloudflare Workers.

See Integrations for setup.

Auth Proxy — API Key Validation

The logclaw-auth-proxy sits between ingress and the OTel Collector. It validates API keys against PostgreSQL, injects tenant_id into OTLP payloads, and enforces rate limits (200 req/min unauthenticated, 6000 req/min per tenant). Stateless and horizontally scalable.

Component Versions

Development

Dashboard (Next.js)

cd apps/dashboardnpm installnpm run dev# → http://localhost:3000

Bridge (Python)

cd apps/bridgepip install -r requirements.txtexport KAFKA_BROKERS="localhost:9092"export OPENSEARCH_ENDPOINT="http://localhost:9200"python main.py# → HTTP API on :8080 (/health, /metrics, /config)

See Bridge docs for configuration reference.

Ticketing Agent (Python)

cd apps/ticketing-agentpip install -r requirements.txtexport KAFKA_BROKERS="localhost:9092"export OPENSEARCH_ENDPOINT="http://localhost:9200"python main.py# → HTTP API on :8080

Agent (Go)

cd apps/agentgo run main.go# → HTTP API on :8080 (/health, /ready, /metrics)

Auth Proxy (TypeScript)

cd apps/logclaw-auth-proxynpm installnpm run dev# → HTTP API on :4318

Requires a PostgreSQL database with API keys. See API Keys docs.

MCP Server (TypeScript)

cd apps/logclaw-mcp-servernpm install && npm run buildLOGCLAW_API_KEY=lc_proj_test npx .

Helm Charts

# Lint all chartsmake lint
# Render templates (dry-run, no cluster needed)make template TENANT_ID=ci-test
# Diff current vs newmake template-diff TENANT_ID=dev-local
# Package charts as .tgzmake package
# Push to OCI registrymake push HELM_REGISTRY=oci://ghcr.io/logclaw/charts

Docs

Full documentation is available at docs.logclaw.ai.

Getting Started:

• Quick Start — Send Logs
• API Keys
• Local Development
• Architecture

Components:

• Bridge — anomaly detection + trace correlation
• Dashboard — web UI
• Ticketing Agent — multi-platform incident routing
• OTel Collector — OTLP ingestion
• Incident Classification — composite scoring

Integrations:

• Integrations Overview — PagerDuty, Jira, ServiceNow, OpsGenie, Slack
• MCP Server — Claude Code, Cursor, Windsurf

Reference:

• OTLP Integration Guide — Python, Java, Node.js, Go SDK examples
• Values Reference — Helm chart configuration
• Onboarding a New Tenant
• API Reference

Enterprise:

• Enterprise Console — multi-org, API key management, project settings

Contributing

We welcome contributions! Please read our guidelines before opening a PR:

• Contributing Guide
• Code of Conduct
• Security Policy

Use the issue templates for bug reports and feature requests.

License

Apache 2.0 — see LICENSE