Overview This page provides a comprehensive reference of OAuth scopes required for each supported app in Klavis AI.
These are the minimum OAuth scopes required for all tools in each Klavis MCP server to function properly.
Supported OAuth App
data.records:read data.records:write data.recordComments:read data.recordComments:write schema.bases:read schema.bases:write user.email:read
goals:read project_templates:read projects:read projects:write projects:delete stories:read task_templates:read tasks:read tasks:write tasks:delete teams:read users:read workspaces:read workspaces.typeahead:read
Attio uses API key authentication rather than OAuth scopes. No specific scopes are required for this integration.
app:read app:write asset:read asset:write brandtemplate:content:read brandtemplate:meta:read comment:read comment:write design:content:read design:content:write design:meta:read design:permission:read design:permission:write folder:read folder:write folder:permission:read folder:permission:write profile:read
ClickUp uses OAuth 2.0 with client credentials. The specific scopes are managed through the ClickUp app configuration rather than explicit scope parameters.
all.full_access offline_access
write:space.permission:confluence write:space:confluence read:attachment:confluence read:page:confluence write:page:confluence search:confluence read:space:confluence read:hierarchical-content:confluence write:confluence-content read:confluence-content.all read:confluence-content.summary read:confluence-space.summary write:confluence-space write:confluence-file read:confluence-props write:confluence-props manage:confluence-configuration read:confluence-content.permission read:confluence-user read:confluence-groups write:confluence-groups readonly:content.attachment:confluence read:me read:account report:personal-data offline_access
account_info.read files.metadata.read files.metadata.write files.content.read files.content.write file_requests.read file_requests.write sharing.read sharing.write contacts.read contacts.write
repo read:user read:org security_events
https://www.googleapis.com/auth/gmail.readonly https://www.googleapis.com/auth/gmail.send https://www.googleapis.com/auth/gmail.compose https://www.googleapis.com/auth/gmail.modify
https://www.googleapis.com/auth/calendar.readonly https://www.googleapis.com/auth/calendar.events
https://www.googleapis.com/auth/drive
https://www.googleapis.com/auth/drive
https://www.googleapis.com/auth/drive
account-info.security.read accounting cms.domains.read cms.domains.write crm.export crm.import crm.lists.read crm.lists.write crm.objects.companies.read crm.objects.companies.write crm.objects.contacts.read crm.objects.contacts.write crm.objects.deals.read crm.objects.deals.write crm.objects.marketing_events.read crm.objects.marketing_events.write crm.objects.owners.read crm.objects.quotes.read crm.objects.quotes.write crm.schemas.companies.read crm.schemas.companies.write crm.schemas.contacts.read crm.schemas.contacts.write oauth settings.users.read settings.users.write tickets timeline e-commerce crm.objects.custom.read crm.schemas.custom.read content sales-email-read
read:jira-user read:jira-work write:jira-work manage:jira-configuration offline_access
read write issues:create comments:create timeSchedule:write
openid profile email w_member_social
users:read boards:read boards:write updates:write
sales_invoices documents estimates bank time_entries settings
read_content update_content insert_content read_comments insert_comments read_user_information_including_email_addresses
openid profile email offline_access Files.ReadWrite.All User.Read
com.intuit.quickbooks.accounting com.intuit.quickbooks.payment openid
api refresh_token offline_access
Bot Scopes: app_mentions:read channels:history channels:read chat:write chat:write.customize commands files:read groups:read groups:write im:history im:read mpim:read reactions:read reactions:write team:read users:read User Scopes: channels:history channels:read channels:write chat:write groups:history groups:read groups:write im:history im:read im:write mpim:history mpim:read users:read users:write search:read
Supabase uses OAuth 2.0 with client credentials. The specific scopes are managed through the Supabase project configuration rather than explicit scope parameters.
accounting.transactions.read accounting.transactions offline_access Need Help? If you need assistance with OAuth scope configuration for any specific application, please refer to the individual OAuth app setup guides or contact our support team.
