MCP Server for Google Drive, OneDrive and Dropbox
TL;DR: Most Google Drive MCP servers let an AI search and read files, and some let it write one file at a time. The Drive AI's MCP connector gives Claude, ChatGPT and other MCP clients one set of tools across Google Drive (including shared drives), OneDrive, SharePoint, Dropbox and The Drive AI's own workspace. Every change is proposed as a preview, confirmed by you, applied in the background if it's large, and reversible with one undo call.
The Model Context Protocol (MCP) is how assistants like Claude and ChatGPT use outside tools. Connect an MCP server for your files, and the assistant can look things up in your drive instead of asking you to paste them in.
There are a lot of these servers now. Directories list dozens for Google Drive alone. Most do the same thing: list, search and read. A few add writing, usually as a direct "move this file" or "delete this file" tool.
Reading is the easy half. This post is about the half that's harder to get right: letting an assistant change your files safely, across more than one cloud.
What should a file MCP server be able to do?
For read-only work, any decent server will do. For changes, look for five things:
- A preview before anything changes. The assistant should be able to propose a batch, see what it would do (count, sample, conflicts), and show you before applying it.
- Your confirmation, tied to that exact preview. Approving a 12-file change shouldn't let a 1,200-file change through.
- An undo. Not "ask the assistant to move everything back," but a call that reverses a specific change.
- Background jobs for big changes. A 5,000-file reorganization shouldn't have to finish inside one tool call.
- Your own permissions. The server should act as you, seeing only what you can see.
And if your files aren't all in one place, one server that covers every drive beats four servers that each behave differently.
What does The Drive AI MCP connector do?
It relays the same tools The Drive AI's own file agent uses, so Claude or ChatGPT works on your files exactly as the agent would. Your workspace and every connected drive appear in one folder tree, addressed by path (/Finance/2026/Invoices) or by ID.
Finding and reading
| Tool | What it does |
|---|---|
fs_tree, fs_digest | The shape of a folder: outline, counts, sizes, types, ages |
fs_ls | List a folder, paged |
fs_find, fs_glob | Find files by type, size, date, or name pattern |
fs_grep | Exact words in names, or inside documents |
fs_search | Find documents by topic or keywords |
fs_read | Read pages of a document, sheets of a spreadsheet, transcripts of recordings |
fs_stat, fs_versions | Details and earlier versions of a file |
fs_access | Who can reach a file or folder |
fs_duplicates | Identical files and look-alikes |
Changing things
| Tool | What it does |
|---|---|
changeset_propose | Build a change (moves, renames, new folders, copies, trash, new or edited documents) and return a preview. Nothing changes. |
changeset_apply | Apply it. Small, low-risk changes go straight through; bigger ones need your confirmation. |
changeset_status | Progress of a change running in the background |
changeset_undo | Reverse an applied change as a whole |
Sharing, files, and the agent itself
share_set,share_revoke,share_publishshare workspace files with people or by public link.create_file_from_attachment,create_file_from_urland upload tools save a file you give the assistant into a folder, which can be undone like any change.agent_askhands a whole task to The Drive AI's own agent. That's how an outside assistant reaches the things that aren't single tools: totals across hundreds of invoices, exports, workflows, e-signature requests and file requests.
How do confirmations work over MCP?
When a change is too big or too risky to apply on its own, changeset_apply returns a confirmation request instead of applying it. The assistant shows you the preview in plain words, and only after you agree does it call again with the confirmation token.
That token is tied to the exact change that was previewed and expires after 15 minutes. If anything about the request differs, it doesn't work. In clients that support MCP's built-in confirmation prompts, the question appears in the client's own interface, so the assistant can't answer it for you.
The thresholds are the same as in the app. By default, up to 20 non-destructive operations apply on their own. Anything that trashes files, works outside the folder you're focused on, or goes over 20 operations needs one confirmation. Over 5,000 operations, you confirm the count. Workspace admins can change these limits.
What does a session look like?
Here's a typical request in Claude with the connector attached:
My Google Drive /Inbox has about 900 scans. File them into the existing client folders under /Clients and rename each one Client, Document type, Date.
- Claude calls
fs_digeston/Inboxto see what's there, thenfs_lsandfs_readon a sample to understand the documents. - It calls
changeset_proposewith the moves and renames. The preview comes back: 900 moves, 900 renames, 14 name collisions, risk medium. - Claude summarizes that for you and asks whether to go ahead. You say yes.
changeset_applywith the token starts a background job. Claude reports progress withchangeset_statuswhen you ask.- You notice the tax returns went under the wrong client. Claude calls
changeset_undo, everything returns to/Inboxwith its original name, and you try again with a clearer rule.
The same session works on OneDrive, SharePoint or Dropbox folders without changing anything, because they're all in the same tree.
How is this different from Claude's or ChatGPT's own Drive connector?
The built-in connectors are good at reading and at single actions. Claude's and ChatGPT's Google Drive integrations can now move, share and trash files, asking before each action. (Claude Help Center)
The differences show up in big jobs and across clouds:
| Built-in Drive connector | The Drive AI connector | |
|---|---|---|
| Google Drive | Yes | Yes, including shared drives |
| OneDrive, SharePoint, Dropbox | Separate connectors, where available | Same tools, one tree |
| How changes apply | One action at a time | Whole batch as one change |
| Preview of a batch | No | Count, sample, conflicts, risk |
| Undo | No | One call reverses a change |
| Large jobs | Within the conversation | Background job with progress |
| Totals across many files | Reads what fits in the chat | Computed across every file via agent_ask |
You don't have to choose. Keep the built-in connector for quick lookups and use The Drive AI connector when the job involves many files or more than one drive. For a deeper comparison, see can Claude organize your Google Drive.
What can't it do?
- No moving between two different clouds. It moves and copies within each drive, not from Dropbox to SharePoint.
- Search on connected drives matches words, not meaning. It finds files by name, type, date, folder and text. Meaning-based search covers files stored in The Drive AI.
- Sharing tools cover workspace files. It doesn't change Google, Microsoft or Dropbox sharing permissions.
- Connected drives need the Max plan or any Team plan. Workspace files work on every plan.
Does using the MCP connector use up assistant tasks?
Direct tool calls, like reading, searching, proposing and applying changes, don't count as assistant tasks. agent_ask does, because it starts a full run of The Drive AI's own agent. So the outside assistant can do most of the work with its own tool calls and use agent_ask for the jobs that need the agent itself.
How do you set it up?
Setup steps for Claude, Claude Desktop, ChatGPT, Cursor and Claude Code are on the MCP page. In Claude and ChatGPT, it's added as a custom connector under Settings, Connectors. You sign in with the Google account your The Drive AI account uses; accounts created with Microsoft, Apple or email can't connect yet. To use your Google Drive, OneDrive, SharePoint or Dropbox through the connector, connect them in The Drive AI first.
Frequently Asked Questions
Is there an MCP server for Google Drive that can move files?
Yes. Several community servers add write tools, and Claude's and ChatGPT's built-in Drive connectors can now move files one action at a time. The Drive AI's MCP connector moves and renames files as previewed batches with undo, in Google Drive (including shared drives), OneDrive, SharePoint and Dropbox.
Is there an MCP server for OneDrive and SharePoint?
Yes. The Drive AI's connector covers OneDrive and SharePoint document libraries alongside Google Drive and Dropbox, with the same tools for each. Microsoft 365 also has its own connectors with some file actions.
Can Claude undo changes to my files?
With The Drive AI's MCP connector, yes. Every change Claude applies through it is recorded as a changeset, and changeset_undo reverses that change as a whole.
Is it safe to give an AI write access to my drive through MCP?
It's as safe as the server's safeguards. Look for previews before changes, confirmations tied to the previewed change, an undo, and access limited to your own permissions. See is it safe to let AI edit your Google Drive.
Does the MCP connector work with ChatGPT?
Yes. Add it as a custom connector in ChatGPT under Settings, Connectors, using the server URL on The Drive AI's MCP page.
Try a read-only question first
Once it's connected, start with something that changes nothing, like what's in my shared drives, roughly, and where are the duplicates? When you trust the answers, ask for a small change, read the preview, apply it, and undo it once just to see that it works. Then give it the folder you've been avoiding.
Share it with your network