Kana · OAuth Scopes

Kana OAuth Scopes

OAuth 2.0 probed

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

CompanyMarketingArtificial IntelligenceAgentic AIMarketing TechnologyAudience IntelligenceCustomer Data PlatformAI Search OptimizationGrowth

Scopes: 0 Flows: Method: probed

Scopes (0)

Kana 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:

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://apps.kana.ai/.well-known/oauth-authorization-server
docs: null
issuer: https://apps.kana.ai
authorization_url: https://apps.kana.ai/oauth/authorize
token_url: https://apps.kana.ai/oauth/token
scope_count: 4
scopes:
- name: mcp:read
  description: >-
    Read-level access to Kana's MCP surface. Verbatim from scopes_supported in the
    authorization-server metadata; Kana publishes no scope-reference page, so no
    per-scope description is available beyond the scope string itself.
- name: mcp:write
  description: >-
    Write-level access to Kana's MCP surface. Verbatim from scopes_supported; no
    published scope reference.
- name: kana:read
  description: >-
    Read-level access to the Kana platform API. Verbatim from scopes_supported; no
    published scope reference.
- name: kana:write
  description: >-
    Write-level access to the Kana platform API. Verbatim from scopes_supported; no
    published scope reference.
notes: >-
  These four strings are exactly what the provider advertises in scopes_supported.
  The mcp:* / kana:* split is the only structure Kana publishes — it separates the
  MCP agent surface from the platform surface. Nothing here is inferred or expanded:
  Kana has no public scopes/permissions documentation page to enrich from, and every
  other path on apps.kana.ai (including /.well-known/oauth-protected-resource, which
  would name the resource each scope guards) returns 401.
x-evidence:
  fetched: '2026-08-13'
  url: https://apps.kana.ai/.well-known/oauth-authorization-server
  http_status: 200
  content_type: application/json; charset=utf-8