Configure your stack in the admin panel
The Opsphere admin panel is where tenant admins set up Cloud Catalog, environments and profiles, integration tools and credentials, invite teammates, manage API keys, and review usage and activity — so Cursor, Slackbot, and other MCP clients operate on the right connected stack.
THE CONFIGURATION GAP
Operational tools fail without a governed control plane
Integrations need more than a one-off API key paste. Cloud accounts span environments and profiles, each tool expects its own tokens and scopes, and teammates need invites without secrets pasted into chat.
Without a governed admin surface, credentials sprawl across notes, spreadsheets, and support tickets, cloud profiles drift out of sync with what agents actually query, and nobody can say who configured what or when a token was last rotated — until an integration breaks in production and the trail has already gone cold.
Credentials without a home
Tokens and endpoints live in spreadsheets and Slack threads instead of a tenant-owned tools catalog with clear ownership.
Environments without structure
Dev, staging, and production — plus multi-account cloud profiles — stay implicit, so agents and humans query the wrong scope.
Access without audit
Inviting users and issuing API keys without usage and activity visibility leaves no reliable trail of who configured what.
HOW THE ADMIN PANEL WORKS
Catalog, tools, and team access in one place
Configure the connected stack your plan allows, wire credentials once, and invite the people who should operate it — with visibility into usage and activity.
Once configured, Cursor, Slackbot, and other MCP clients read directly from this catalog at query time — no environment variables to sync by hand, no tribal knowledge about which token unlocks which environment.
Cloud Catalog
Register cloud providers such as AWS and Azure, then define environments and account profiles — including dedicated profiles per account in a multi-account estate — so every query resolves to the right account scope.
Tools & Credentials
Browse tools by category, configure each integration individually, and store the tokens, credentials, and endpoints that tool needs — without scattering secrets outside the tenant.
Users, Keys & Audit
Create and invite users, issue API keys for MCP clients, and review usage charts plus activity logs so configuration and access stay traceable.
GET STARTED
Set up your tenant in the admin panel.
Configure Cloud Catalog, tools, and team access — then connect Cursor, Slackbot, or the web client to the stack you just defined.