Lumoz MCP server for observability data, signals, and problem/RCA investigation and resolution
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"lumoz-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Lumoz MCP Server MCP server for Lumoz observability data and RCA resolution reporting. Connect it to Claude, Cursor, GitHub Copilot, Codex, or any other MCP-compatible client to query traces, signals, and problems, and to drive RCA generation and fix reporting directly from your AI tool. ## Getting an API Key 1. Log in to the [Lumoz console](https://console.lumoz.ai). 2. Go to **Settings → API Keys** (org admin required). 3. Click **Create Key**, name it (e.g. `MCP - my laptop`), and save it. 4. Copy the key shown as `client_id:client_secret` — you won't be able to see the secret again after closing the dialog. The default scopes granted (`read:telemetry`, `write:telemetry`) are sufficient for every tool in this server, including the ones that write RCA feedback and fix reports. ## Claude / Cursor / Codex / Copilot Config Requires [`uv`](https://docs.astral.sh/uv/getting-started/installation/) installed locally — `uvx` runs the server without a separate install step. ```json { "mcpServers": { "lumoz": { "command": "uvx", "args": ["lumoz-mcp"], "env": { "LUMOZ_API_KEY": "client_id:client_secret" } } } } ``` Paste in the key from the step above and you're done — the server talks to Lumoz's production API by default. Add this block to your client's MCP config file (e.g. Claude Desktop's `claude_desktop_config.json`, or the equivalent settings file for Cursor/Copilot/Codex), then restart the client. ## Tools - Data: `list_apps`, `list_traces`, `search_traces`, `get_trace`, `get_trace_spans`, `get_span` - Signals: `list_signal_definitions`, `list_signals`, `get_signal`, `list_traces_for_signal`, `list_trace_signals` - Business Tasks: `list_business_tasks`, `list_business_task_signals` - Problems: `list_problems`, `get_problem`, `list_problem_signals`, `generate_rca`, `report_fix`, `submit_problem_feedback` - RCA: `list_rcas`, `get_rca`, `submit_rca_feedback` - Eval Suggestions: `list_app_eval_suggestions`, `list…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.