Query Honeycomb datasets for context, then create triggers and boards with approval.
Connect Honeycomb and Luumen can read your telemetry the way you would: pull a dataset's column schema, replay a trace as a waterfall, check existing triggers and anomaly signals. When the investigation points to a change — a new trigger, an SLO, a deploy marker — Luumen writes it back to Honeycomb as a step you approve first. Auth is handled through OAuth.
33 tools: 23 read, 10 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Honeycomb MCP run looks like inside Luumen.
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as canvas agent invoke, create board, create marker, create recipient, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Honeycomb MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.