Skip to main content

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

Attio uses API key authentication rather than OAuth scopes. No specific scopes are required for this integration.
Cal.com OAuth scopes are configured via the Cal.com app settings rather than an explicit scope string.
ClickUp uses OAuth 2.0 with client credentials. The specific scopes are managed through the ClickUp app configuration rather than explicit scope parameters.
Shopify OAuth scopes are configured via the Shopify app settings rather than an explicit scope string.
Bot Scopes:
User Scopes:
Supabase uses OAuth 2.0 with client credentials. The specific scopes are managed through the Supabase project configuration rather than explicit scope parameters.
Vercel OAuth scopes are configured via the Vercel app settings rather than an explicit scope string.
X (Twitter) OAuth scopes are configured via the X app settings rather than an explicit scope string.

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.