Definite · OAuth Scopes

Definite OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://api.definite.app/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.

CompanyDataAnalyticsBusiness IntelligenceData IntegrationData WarehouseLakehouseSemantic LayerArtificial IntelligenceAI AgentsModel Context ProtocolETL

Scopes: 1 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://api.definite.app/oauth/authorize

Token URL
https://api.definite.app/oauth/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
mcp	Grants an OAuth-authorized MCP client access to the Definite Model Context Protocol server tools (query, semantic layer, integrations, syncs, docs, drive). The only scope advertised in the authorization-server metadata.	authorizationCode

📄 Provider scope reference: https://www.definite.app/docs/mcp/mcp

Source

OAuth Scopes

generated: '2026-07-18'
method: searched
source: https://api.definite.app/.well-known/oauth-authorization-server
docs: https://www.definite.app/docs/mcp/mcp
schemes:
- name: oauth2Mcp
  source: /.well-known/oauth-authorization-server
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.definite.app/oauth/authorize
    tokenUrl: https://api.definite.app/oauth/token
    pkce: S256
scopes:
- scope: mcp
  description: >-
    Grants an OAuth-authorized MCP client access to the Definite Model Context
    Protocol server tools (query, semantic layer, integrations, syncs, docs,
    drive). The only scope advertised in the authorization-server metadata.
  flows: [authorizationCode]
  sources: [/.well-known/oauth-authorization-server]