Kick · OAuth Scopes

Kick OAuth Scopes

OAuth 2.0 searched

Kick 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 Kick API on a user’s behalf.

Tokens are issued from https://use.kick.co/mcp/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.

CompanyBookkeepingAccountingFinanceFinTechMCPAI AgentsSmall Business

Scopes: 2 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://use.kick.co/mcp/oauth/authorize

Token URL
https://use.kick.co/mcp/oauth/token

Flows
authorizationCode

Scopes (2)

Scope	Description	Flows
mcp:read	Tool discovery and read-only calls against the Kick MCP server.	authorizationCode
mcp:write	Tools that can change data; write tools are preview-first and require explicit confirmation.	authorizationCode

📄 Provider scope reference: https://docs.kick.co/ai/permissions-and-security.md

Source

OAuth Scopes

generated: '2026-07-19'
method: searched
source: https://use.kick.co/.well-known/oauth-authorization-server
docs: https://docs.kick.co/ai/permissions-and-security.md
schemes:
- name: OAuth2
  source: https://use.kick.co/.well-known/oauth-authorization-server
  flows:
  - flow: authorizationCode
    authorizationUrl: https://use.kick.co/mcp/oauth/authorize
    tokenUrl: https://use.kick.co/mcp/oauth/token
    registrationUrl: https://use.kick.co/mcp/oauth/register
    code_challenge_methods: [S256]
scopes:
- scope: mcp:read
  description: Tool discovery and read-only calls against the Kick MCP server.
  flows: [authorizationCode]
  sources: [https://use.kick.co/.well-known/oauth-authorization-server]
- scope: mcp:write
  description: Tools that can change data; write tools are preview-first and require explicit confirmation.
  flows: [authorizationCode]
  sources: [https://use.kick.co/.well-known/oauth-authorization-server]
notes: >-
  Scopes are those advertised for the Kick MCP OAuth surface (RFC 8414 metadata +
  the Permissions and Security docs). Kick has no public OpenAPI, so scopes are not
  derived per-operation; the two coarse MCP scopes gate read vs. write across the
  full tool roster.