Componecat OAuth Scopes

generated: '2026-11-04'
method: searched
source: https://docs.componecat.ai/app/reference/apis/
docs: https://docs.componecat.ai/app/guides/connect-ai-agents/
description: >-
  Componecat tokens (personal access tokens and OAuth device-flow tokens for MCP) are
  scoped per resource category with an access level, and can additionally be narrowed
  to specific entities. Docs: "Tokens are scoped: you grant read or write access per
  resource category (catalog entities, teams, schema, wiki), and can scope a token to
  specific entities." The OpenAPI CredentialScopeRequest schema carries resource,
  access ("none, read, or write (any casing is accepted)") and canCreate. These are
  category grants, not OAuth scope strings; the literal resource identifiers are not
  enumerated in the docs or the spec, so the names below are the docs' category labels.
model: resource-category x access-level (none|read|write), optional per-entity restriction
access_levels: [none, read, write]
scopes:
- name: catalog entities
  levels: [read, write]
  description: Read or edit catalog entities; write is required to create/update entities and to move them between teams.
- name: teams
  levels: [read, write]
  description: Read or edit teams; POST /teams/{id}/reassign-entities needs write access to both teams and entities.
- name: schema
  levels: [read, write]
  description: Read or edit kind, field and relationship-kind definitions.
- name: wiki
  levels: [read, write]
  description: Gates the /wiki REST routes and the MCP wiki tools (list_wiki_pages, get_wiki_page, create_wiki_page, update_wiki_page, get_guides_for).
notes: >-
  "An agent only sees the tools its grant allows, so a read-only agent is not offered
  the editing tools at all." (connect-ai-agents guide)