Skip to main content

OAuth Storage Providers

Connect cloud storage services like Google Drive, GitHub, Dropbox, and OneDrive through a secure OAuth flow. Once connected, storage tools for that provider are exposed to your agents and IDE through the MCP gateway.

Key Concepts

Supported providers

ProviderFile typesAccess scope
Google DriveDocs, Sheets, PDFs, imagesRead-only access to files you select or all files
GitHubRepositories, code, issues, PRsRead access to selected repositories
DropboxAll file typesRead access to selected folders
OneDriveOffice docs, PDFs, imagesRead access to selected folders

How OAuth works

When you connect a provider, you're redirected to their authorization page where you grant Clevername specific permissions. Clevername receives an access token and refresh token, both stored encrypted. Access tokens are refreshed automatically when they expire — you only authorize once.

Token security

OAuth tokens are encrypted at rest using AES-256-GCM. Refresh tokens are used server-side only and never sent to the browser. If you disconnect a provider, all stored tokens are immediately deleted.

Step-by-Step Guide
1

Find the Storage section

Go to Dashboard → Integrations and scroll to the Storage section at the bottom of the Tools tab. You'll see cards for each supported storage provider with their connection status.

Storage section at the bottom of the Integrations Tools tab, showing cards for Google Drive, GitHub, Dropbox, and OneDrive with Connect buttons
Each provider card shows its connection status and a Connect or Disconnect button.
2

Connect a provider

Click Connect on the provider you want to add. You'll be redirected to the provider's OAuth authorization page.

Note
Clevername requests the minimum scopes needed for file reading. You can review the exact permissions on the provider's consent screen before authorizing.
3

Authorize access

On the provider's page, review the requested permissions and click Allow or Authorize. You'll be redirected back to Clevername automatically.

Google OAuth consent screen showing the permissions Clevername is requesting
Review the permissions before authorizing. Clevername only requests read access.
4

Verify the connection

After authorization, the provider card shows a green Connected status. Storage tools for that provider are now exposed to your agents and IDE through the MCP gateway.

Tip
To test the connection, ask an agent or IDE that is connected through the MCP gateway to list files from your connected storage. It will use the storage tools to browse your files.
5

Disconnect a provider

To revoke access, click Disconnect on the provider card. This deletes all stored tokens from Clevername. For complete revocation, also remove Clevername from the provider's authorized apps page (e.g., Google Account → Security → Third-party apps).