Lumen

Lumen MCP

MCP tool inventory on mcp-lumen.orkestia.dev — same org-scoped REST surface, Bearer forwarded

Lumen MCP is a separate server from the workflow catalog MCP.

	Workflow MCP	Lumen MCP
URL	`https://mcp.orkestia.dev`	`https://mcp-lumen.orkestia.dev/mcp`
Job	Discover / start / watch workflows	Read + triage telemetry
Docs	MCP integration	this page

Every tool forwards the caller's Authorization: Bearer. Org scope is identical to Query API. Enable Lumen first — Enable.

{
  "mcpServers": {
    "lumen": {
      "type": "http",
      "url": "https://mcp-lumen.orkestia.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${ORKESTIA_TOKEN}"
      }
    }
  }
}

Keep the token in the environment. Clients that support OAuth can sign in instead of a static bearer.

lumk_ read keys work for GET-shaped tools only. Resolve / create-rule / create-key need a write-capable org token (403 WRITE_ACCESS_REQUIRED otherwise).

Tools

Identity and fleet:

Tool	Maps to
`whoami`	Token identity
`list_projects`	`GET /api/projects`
`dashboard_summary`	`GET /api/dashboard/summary`
`dashboard_projects`	`GET /api/dashboard/projects`
`dashboard_top_error_groups`	`GET /api/dashboard/top-error-groups`
`dashboard_events`	`GET /api/dashboard/events`
`usage`	`GET /api/usage`
`org_plan`	`GET /api/org-plans/{org}`

Logs:

Tool	Maps to
`list_logs`	`GET /api/logs`
`get_log`	`GET /api/logs/{id}`
`log_stats`	`GET /api/logs/stats`
`log_pulse`	`GET /api/logs/pulse`

Error groups and triage:

Tool	Maps to
`list_error_groups` / `get_error_group`	`GET /api/error-groups[/{id}]`
`resolve_error_group`	`PATCH …/resolve` (root cause + solution → triage memory)
`ignore_error_group` / `reopen_error_group`	`PATCH …/ignore` \| `…/reopen`
`assign_error_group`	`PATCH …/assign`
`set_error_group_severity`	`PATCH …/severity`
`link_error_group_ticket` / `unlink_error_group_ticket`	ticket link
`bulk_resolve_error_groups` / `bulk_ignore_error_groups`	bulk (may require elevated principal)

Traces, metrics, memory:

Tool	Maps to
`get_trace`	`GET /api/traces/{trace_id}`
`span_stats` / `slow_spans` / `span_errors`	`/api/spans/*`
`list_metrics` / `aggregate_metrics` / `metric_names`	`/api/metrics*`
`list_visible_metrics`	customer metric catalog
`memory_similar`	`GET /api/memory/similar`
`memory_context`	`GET /api/memory/context/{trace_id}`
`memory_unresolved`	`GET /api/memory/unresolved`

Rules and keys:

Tool	Maps to
`list_alert_rules` / `get_alert_rule` / `create_alert_rule` / `delete_alert_rule`	`/api/alert-rules`
`list_ingest_rules` / `get_ingest_rule`	`/api/ingest-rules`
`list_fingerprint_rules` / `get_fingerprint_rule`	`/api/fingerprint-rules`
`list_api_keys` / `create_api_key` / `revoke_api_key`	`/api/api-keys` (plaintext once on create)

Filter arguments match the Query API query string (project, level, from/to, window, limit, …). Discover the live input schema from the MCP tool descriptors — do not hard-code optional fields from this table.

Day-to-day UI: Use Lumen. Ingest contract: Send data.

Use Lumen

App routes mapped to the Query API — dashboard, logs, groups, traces, metrics, rules

Query API

Read and mutate Lumen over HTTP — logs, error groups, traces, metrics, Pulse, dashboards, and rule JSON