Connect Dropbox to Claude Code

Let Claude upload, move, and organize files in Dropbox. From the terminal, inside the sessions where you already work.

How do you connect Dropbox to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Dropbox, you add a Dropbox MCP server: a small hosted service that exposes Dropbox's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Dropbox account. No API keys pasted into config files.

claude mcp add --transport http dropbox https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Dropbox once connected?

Full read-write Dropbox access lets Claude create folders, upload and move files, rename and organize content, and generate share links once you approve. The filing and cleanup that used to mean dragging files by hand happen where your storage already lives, with Claude working inside the folder structure.

Create a folder structure and move existing files into the right places
Upload a generated document or summary into a specific folder
Rename files to follow a consistent naming convention
Create a shared link for a file or folder after you approve it
Find every file matching a query and propose a batched reorganization
Copy a template folder to start a new project

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Dropbox access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Dropbox API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Dropbox changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Dropbox connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Dropbox connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Dropbox account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Dropbox's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Dropbox?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Dropbox account it signs in with. Revoking access is one click in Dropbox.

More on the Dropbox connector

Dropbox connector for claude.ai Google Drive + Claude Code Box + Claude Code SharePoint + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us