
Read BTP accounts and destinations, change them as approved steps
Connect your SAP BTP landscape and ask about it in plain language. Luumen reads global accounts, subaccounts, entitlements, environments and destinations through SAP's hosted MCP endpoint, using OAuth2. Changes — a new destination, an entitlement assignment, a subaccount update — are previewed, approved by default, and recorded.
33 tools: 22 read, 11 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed SAP BTP Administration 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.
Read actions answer immediately. Anything that writes — enable cloud foundry environment, create destination, delete destination, update destination, and more — is shown as a plan and requires approval by default, including the 3 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
SAP BTP Administration is available on the enterprise plan. Talk to us about enabling it for your account — the rest of the catalogue is available on every plan.
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 SAP BTP Administration — 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.