Kubit AI, Inc. · OAuth Scopes

Kubit AI, Inc. OAuth Scopes

OAuth 2.0 searched

Kubit AI, Inc. uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyAnalyticsProduct AnalyticsData WarehouseLLM ObservabilityModel Context ProtocolAgent AnalyticsOpenTelemetryDevops

Scopes: 0 Flows: Method: searched

Scopes (0)

Kubit AI, Inc. implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference: https://docs.kubit.ai/docs/mcp-server

Source

OAuth Scopes

generated: '2026-07-19'
method: searched
source: https://mcp.kubit.ai/.well-known/oauth-authorization-server
docs: https://docs.kubit.ai/docs/mcp-server
authorization_server: https://mcp.kubit.ai
protected_resource: https://mcp.kubit.ai/mcp
notes: >-
  Kubit's only documented OAuth surface is the hosted MCP server. The scopes below are
  taken verbatim from the published RFC 8414 authorization-server metadata and the
  RFC 9728 protected-resource metadata. Kubit's web platform authenticates with SSO
  (SAML/OIDC via Google Workspace, Okta, Microsoft Entra ID, AWS IAM Identity Center)
  and exposes no separate public scope registry.
scopes:
  - name: mcp:read
    description: >-
      Read access to Kubit analytics through the MCP server — user context, schema
      metadata, existing report results and raw data exports, and search.
  - name: mcp:write
    description: >-
      Write access through the MCP server — creating and executing new reports against
      the connected warehouse.