Opsphere

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.

OPEN ADMIN (opens in new tab)

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, endpoints, and scopes; teammates need invites without sharing secrets in chat.

Without a central admin surface, credentials sprawl across personal notes, env files, and tickets — and nobody can answer which AWS profile, Azure tenant, or Datadog site a query will hit.

The result: brittle setups, missing audit trails, and MCP clients that cannot resolve the catalog your plan actually allows.

  • 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.

  • 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.

ADMIN CAPABILITIES

Built for tenant configuration and control

Everything needed to associate clouds, activate services, manage tools, and govern who can connect — before operational clients ask a single question.

  • Cloud Catalog

    Associate cloud providers and related services allowed on your plan. Track resources and observability wiring from a single catalog view.

  • Environments & Profiles

    Model environments and profiles per connected cloud account — the same multi-account pattern teams already use in AWS — so tools and agents stay scoped.

  • Categorized Tools

    Activate and manage available cloud and SaaS tools organized by category, then open each tool for individual configuration.

  • Credentials & Endpoints

    Configure authentication tokens, credentials, and endpoints (or equivalent mechanisms) required by each integration — owned by the tenant, not pasted into chat.

  • Users, API Keys & Logs

    Invite teammates, create users, manage API keys for MCP connections, and inspect usage plus activity logs for audit-style traceability.

Admin Panel Focus

Cloud association
Catalog-first
Env & profile scope
Per account
Tool configuration
Per integration
Credential storage
Tenant-owned
Provider coverage
Plan-based
Team invites
Self-service
Activity visibility
Usage · Logs
MCP API keys
Admin-issued
Access model
Admin-governed

TYPICAL WORKFLOW

From empty tenant to connected stack

Admin Setup Flow

How a tenant admin prepares Opsphere before engineers ask questions in Cursor or Slackbot.

  1. Open The Admin Panel

    Sign in to the Opsphere admin for your tenant and land on the control plane for catalog, tools, and access.

    • Login
    • Tenant
    • Console

  2. Configure Cloud Catalog

    Add cloud providers, environments, and profiles so multi-account AWS or Azure scopes resolve correctly for every tool call.

    • Catalog
    • Envs
    • Profiles
    • Clouds

  3. Wire Tools & Credentials

    Enable services by category, open each tool, and store the tokens and endpoints that integration requires.

  4. Invite Users & Issue Keys

    Create or invite teammates, mint API keys for MCP clients, then monitor usage and activity logs as the stack goes live.

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.

OPEN ADMIN (opens in new tab)