Dropbox is a cloud storage and collaboration platform for storing, syncing, and sharing files and folders.
It can be connected to Agen.co two ways, matching the Official / In-house filter in the connector picker:
- Official — Agen.co connects through Dropbox's own hosted MCP server (
https://mcp.dropbox.com/mcp), so your AI agents use the same file, search, and sharing tools Dropbox exposes to MCP clients like Claude. Authorization uses a Dropbox app that you register yourself. - In-house — Agen.co wraps the Dropbox API directly through its own integration layer, using an OAuth 2.0 app you register in the Dropbox App Console.
Pick Official if the built-in MCP tools cover what your agents need. Fall back to In-house if you need the Dropbox API surface beyond them.
Prerequisites
Prerequisites
- A Dropbox account that can create apps in the Dropbox App Console. On a Dropbox team, your admin may control whether you can register or connect apps.
Dropbox refuses dynamic client registration from clients outside its partner list, so you register your own Dropbox app and give Agen.co its App key and App secret. The app needs Agen.co's callback URLs, so start in Agen.co.
- In the Agen.co portal, go to Connectors → My connectors and click Add connector.
- Find Dropbox and select it.
- In the Add Dropbox panel, keep the Official tab selected. The panel shows two read-only URLs at the bottom — copy both:
- Callback URL — completes the initial OAuth handshake between Agen.co and your Dropbox app.
- Gateway callback URL — used by the Agen.co MCP gateway for per-user authorization at runtime.
Leave this panel open — you return to it after registering the app in Dropbox.
- In the Dropbox App Console, click Create app.
- Select Scoped access, then Full Dropbox, enter a name (for example,
Agen.co), and click Create app. - On the Settings tab, copy the App key, and click Show next to App secret to copy it.
- In the OAuth 2 section, add both callback URLs from Agen.co under Redirect URIs, clicking Add after each. Each URI is saved as soon as you add it. Still under OAuth 2, set Allow public clients (Implicit Grant & PKCE) to Allow.
- Open the Permissions tab, enable the following scopes under Individual Scopes, and click Submit:
| Scope | Description |
|---|---|
account_info.read | Read basic account information |
files.metadata.read | List files and folders and read their metadata |
files.metadata.write | Update file and folder metadata |
files.content.read | Download and read file content |
files.content.write | Create, upload, move, copy, and delete files and folders |
sharing.read | Read sharing settings and shared links |
sharing.write | Create and manage shared links |
file_requests.read | Read file requests |
file_requests.write | Create and manage file requests |
In the App Console, a read scope is disabled while its matching write scope is enabled, because the write scope already includes read access.
Enable the scopes before you connect
Enable the scopes before you connect
Agen.co requests the scopes the Dropbox MCP server publishes. If a scope is not enabled on the Permissions tab, Dropbox cannot grant it during sign-in, so enable all of them before you click Connect.
A new Dropbox app starts in Development status, which limits how many Dropbox users can connect to it until the app is moved to production.
Return to the open Add Dropbox panel and fill in the fields:
| Field | Required | Description |
|---|---|---|
| Instance Slug | Yes | Namespaces this instance — it prefixes each imported tool as slug__tool, so several instances of the same MCP can coexist. Use lowercase kebab-case. You can change it later from the connector's settings. |
| Client ID | Yes | The App key from your Dropbox app. |
| Client Secret | Yes | The App secret from your Dropbox app. |
| Callback URL | — | Read-only. Add it as a redirect URI in your Dropbox app. |
| Gateway callback URL | — | Read-only. Also add it as a redirect URI — the MCP gateway uses it for per-user authorization at runtime. |
- Click Connect. You are redirected to Dropbox to sign in and approve access.
- After you approve, the panel switches to Select the tools to import from Dropbox. Every tool is on by default; turn off any you do not want your agents to see.
- Click Add. The connector is created and the selected tools are imported only when you click Add — if you close the panel first, nothing is saved, even if the Dropbox callback page reported success.
| Area | What it covers |
|---|---|
| Files and folders | Browse, read, create, copy, move, and delete files and folders |
| Search | Find files and folders |
| Content | Extract file content as text, Markdown, or transcripts |
| Revisions | List and restore file revisions |
| Sharing | Create and manage shared links |
Content extraction is limited to 5 MB per file, and a folder listing returns at most 100 items per call. Tool availability follows Dropbox's own list and can change.
Enabling the Dropbox connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.
Prerequisites
Prerequisites
- A Dropbox account
- Access to the Dropbox App Console
Navigate to dropbox.com/developers/apps. Sign in with your Dropbox account if prompted. You will see your list of existing apps. Click Create app.
On the Create a new app on the DBX Platform page, select Scoped access under step 1. This is the recommended API type that gives your app fine-grained control over the permissions it requests.
Under step 2, select Full Dropbox to allow your app to access all files and folders in the user's Dropbox.
Under step 3, enter a name for your app (for example, Frontegg Integration), then click Create app.
After the app is created, you land on the Settings tab. Find the App key field — this is your OAuth 2.0 Client ID. Copy it for use in the Frontegg portal.
Next to the App secret field, click Show. Copy the revealed secret for use in the Frontegg portal.
Keep your credentials secure
Keep your credentials secure
Store the App secret immediately after copying it. Never share or commit it to version control.
Scroll down to the OAuth 2 section. In the Redirect URIs field, enter the following URIs one at a time and click Add after each:
https://YOUR_MCP_GATEWAY_URL/integration-callback
The redirect URI appears as a saved entry in the Redirect URIs section.
Click the Permissions tab. In the Individual Scopes section, enable the following scopes:
| Scope | Description |
|---|---|
account_info.read | View basic account information (username, email, country) |
files.metadata.read | View information about files and folders |
files.content.write | Upload, create, and delete files and folders |
files.content.read | Download files and view folder contents |
sharing.write | Manage sharing settings and shared links |
sharing.read | View sharing settings and collaborators |
file_requests.write | Create and manage file requests |
file_requests.read | View file requests |
contacts.read | View manually added Dropbox contacts |
Click Submit to save the permissions.
A confirmation banner appears: Permissions change successful. Your app is now fully configured.
Once you have your App key and App secret, configure the integration in the Frontegg portal:
- Open the Frontegg portal and navigate to [ENVIRONMENT] → Integrations → Dropbox.
- Enter the App key in the Client ID field and the App secret in the Client Secret field.
- Select the required scopes.
- Click Save.