Query, inspect, and update your InfluxDB Cloud time series stack from the terminal
Connect InfluxDB Cloud and Luumen can read the pieces you usually check by hand: the API routes available to your org, the DBRP mappings that route v1 queries, and the parsed structure of a Flux script before you run it. Changes — updating a DBRP mapping, writing line protocol, adding a dashboard cell — are previewed, approved, and recorded. Auth is by API key.
9 tools: 3 read, 6 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed InfluxDB Cloud run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add dashboard cell, delete user, sign in, sign out, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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 InfluxDB Cloud — 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.