Comment.io · OAuth Scopes
Comment.io OAuth Scopes
OAuth 2.0
none
Comment.io 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.
CompanyAI AgentsCollaborationDocumentsMarkdownMCPKnowledge ManagementWorkspace
Scopes: 0
Flows:
Method: none
Scopes (0)
Comment.io 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.
Comment.io documents OAuth 2.1 for its MCP servers but states it has no scopes ("there are no scopes: a grant is for one agent in one workspace, at one MCP server"). The OpenAPI declares only an http bearer scheme.
Comment.io documents OAuth 2.1 for its MCP servers but states it has no scopes ("there are no scopes: a grant is for one agent in one workspace, at one MCP server"). The OpenAPI declares only an http bearer scheme.
📄 Provider scope reference: https://comment.io/auth.md
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.