Kive · OAuth Scopes

Kive OAuth Scopes

OAuth 2.0 searched

Kive publishes 2 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Kive API on a user’s behalf.

Tokens are issued from https://mcp.kive.ai/oauth/token.

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.

CompanySoftware-as-a-ServiceArtificial IntelligenceGenerative AICreativeProduct PhotographyDigital Asset ManagementE-CommerceImageVideoMCP

Scopes: 2 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://mcp.kive.ai/oauth/authorize

Token URL
https://mcp.kive.ai/oauth/token

Flows
authorizationCode

Scopes (2)

Scope	Description	Flows
kive:mcp	Access the Kive MCP server on behalf of the authorizing user. Per Kive's MCP documentation this authorization allows a client to view and edit Kive assets, set up products, and spend Kive credits for supported generation actions.	authorizationCode
offline_access	Issue a refresh token so the client can keep access without re-prompting the user.	authorizationCode

📄 Provider scope reference: https://kive.ai/docs/mcp/overview.md

Source

OAuth Scopes

generated: '2026-07-19'
method: searched
source: https://mcp.kive.ai/.well-known/oauth-authorization-server
docs: https://kive.ai/docs/mcp/overview.md
notes: >-
  Scopes are advertised by the Kive MCP authorization server (RFC 8414) and
  echoed by its protected-resource metadata (RFC 9728). Kive exposes a single
  coarse-grained product scope rather than per-resource scopes; the effective
  permission boundary is the authorizing user's Kive workspace role and the
  workspace credit balance, both enforced server-side at call time.
schemes:
- name: KiveMCPOAuth
  source: https://mcp.kive.ai/.well-known/oauth-authorization-server
  flows:
  - flow: authorizationCode
    authorizationUrl: https://mcp.kive.ai/oauth/authorize
    tokenUrl: https://mcp.kive.ai/oauth/token
scopes:
- scope: kive:mcp
  description: >-
    Access the Kive MCP server on behalf of the authorizing user. Per Kive's MCP
    documentation this authorization allows a client to view and edit Kive
    assets, set up products, and spend Kive credits for supported generation
    actions.
  flows: [authorizationCode]
  sources: [https://mcp.kive.ai/.well-known/oauth-authorization-server]
- scope: offline_access
  description: Issue a refresh token so the client can keep access without
    re-prompting the user.
  flows: [authorizationCode]
  sources: [https://mcp.kive.ai/.well-known/oauth-authorization-server]
enforcement:
  model: workspace-permission-and-credit
  notes: >-
    Kive enforces workspace access, account permissions, and credit availability
    independently of the granted scope. A scoped token cannot exceed the
    authorizing user's workspace role.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/kive-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.