Clevra · OAuth Scopes
Clevra OAuth Scopes
OAuth 2.0
none
Clevra 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.
CompanyField Service ManagementContractorsSchedulingInvoicingPaymentsCRMMCPAI Assistant
Scopes: 0
Flows:
Method: none
Scopes (0)
Clevra 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.
The MCP docs state "Scopes: None. What the assistant can see and do is decided by the person's Clevra role on every request." Access is role-based (Org Admin, Manager, Dispatcher), not scope-based.
The MCP docs state "Scopes: None. What the assistant can see and do is decided by the person's Clevra role on every request." Access is role-based (Org Admin, Manager, Dispatcher), not scope-based.
📄 Provider scope reference: https://clevra.ai/mcp
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.