MCP server

The Drive AI MCP

The Drive AI MCP server lets Claude, ChatGPT, and other MCP clients find, read, and reorganize your files across Google Drive, OneDrive, SharePoint, Dropbox, and The Drive AI. Every change is previewed, confirmed by you, and can be undone.

Add to Claude

Add to Cursor

https://thedriveai.fastmcp.app/mcp

Installation

Claude.ai and Claude Desktop

Settings → Connectors → Add custom connector, then paste the server URL. Connectors are on your account, so the desktop app gets it too.

Add to Claude.ai and Claude Desktop

ChatGPT

Plugins → + → Add custom MCP server, then paste the server URL and sign in. Changing files from ChatGPT needs a Business or Enterprise workspace, where an admin publishes the server; on Pro, custom servers can only read.

Cursor

One-click install.

Add to Cursor

You sign in with your The Drive AI account, whichever way it signs in: Google, Microsoft, Apple or email. The first time, you see what the assistant may do and allow it. Settings → MCP lists everything connected as you, and disconnects it.

From the command line

Claude Code

claude mcp add --scope local --transport http thedriveai https://thedriveai.fastmcp.app/mcp

Codex CLI

codex mcp add --url https://thedriveai.fastmcp.app/mcp thedriveai

Gemini CLI

gemini mcp add thedriveai https://thedriveai.fastmcp.app/mcp --transport http

VS Code

code --add-mcp '{"name":"thedriveai","type":"http","url":"https://thedriveai.fastmcp.app/mcp"}'

What you can ask

File everything in /Inbox on my Google Drive into the existing client folders, and rename each file Client, Document type, Date.
Reads the files, proposes every move and rename as one change, applies it after you confirm.
Undo that.
Reverses the whole change: files return to /Inbox with their original names.
Find every W-9 we have, in any drive.
Searches the workspace and every connected drive at once.
Where are the duplicates in our shared drives?
Groups identical files and look-alikes without downloading them.
What did we spend with each vendor this year? Use every invoice under /Finance.
Hands the task to The Drive AI agent, which reads every invoice into a table and adds it up.
Every time an invoice lands in Gmail, file it by vendor and year.
Has The Drive AI agent draft a workflow that keeps running after the chat ends.

Jobs worked through end to end, with the prompt, what comes back and the limits, are in use cases, with setup and fixes for Claude and Google Drive.

How confirmations work

By default, a change of up to 20 non-destructive operations applies on its own. Anything that trashes files, works outside the folder in focus, or goes over 20 operations needs one confirmation, and over 5,000 you confirm the count. Workspace admins can change these limits.

When confirmation is needed, the assistant shows you the preview and asks. In clients that support MCP confirmation prompts, the question appears in the client's own interface. The confirmation is tied to the exact change previewed and expires after 15 minutes. Changes over a couple of hundred operations run in the background, and the assistant can report progress.

Tools

Find and read

fs_tree, fs_digestThe shape of a folder: outline, counts, sizes, types, ages
fs_lsList a folder, paged
fs_find, fs_globFind files by type, size, date, or name pattern
fs_grepExact words in names, or inside documents
fs_searchFind documents by topic or keywords
fs_readRead pages, sheets, or a recording's transcript
fs_stat, fs_versionsDetails and earlier versions of a file
fs_accessWho can reach a file or folder
fs_duplicates, fs_hash_backfillIdentical files and look-alikes

Change

changeset_proposeBuild a change (move, rename, new folder, copy, trash, create or edit a document) and return its preview
changeset_applyApply it; asks for confirmation when the change is large or destructive
changeset_statusProgress of a change running in the background
changeset_undoReverse an applied change as a whole

Share and save

share_set, share_revokeShare workspace files with people, or remove access
share_publishTurn a public link on or off
create_file_from_attachment, create_file_from_urlSave a file you give the assistant into a folder
create_upload_ticket, create_file_from_upload, upload_file_contentUpload bytes the assistant holds

The agent

agent_ask, agent_continueHand a whole task to The Drive AI agent: totals across many files, exports, workflows, e-signature and file requests
job_statusFollow a background job
approval_statusFollow a change that waits for the person's decision in The Drive AI
get_current_userWho is signed in, and their workspaces

Agents of their own

Claude and ChatGPT connect through the server above. A CLI, a coding agent or a script needs no chat host: The Drive AI is its authorization server, and it signs in, or signs up, by itself. You stay in charge of what it may do.

Register, then sign in

Register as a public client at the registration endpoint named in https://service.thedrive.ai/.well-known/oauth-authorization-server (a name, and redirect URIs if you have a browser; PKCE, no secret). With a browser, the person signs in at thedrive.ai. Without one, use the device grant: show the person the eight-letter code, they approve it at https://thedrive.ai/oauth/mcp/device, and you poll the token endpoint. Either way you then connect to https://thedriveai.fastmcp.app/mcp with the access token as a bearer, the same endpoint a chat host uses; refresh at the token endpoint before it expires.

Ask for the scopes you need

read, write, share and ask. The person sees them when they allow you, and can narrow or end the grant later in Settings → MCP; a call outside the grant is refused in words you can relay.

No account yet? Make one

A registered client can sign up on its own at https://service.thedrive.ai/api/v1/oauth/mcp/signup and gets a workspace and a claim link at once. The link shows the person what you made before they sign in, and one button makes it theirs. Until then the account is provisional: free, 1 GB, 20 agent tasks in all, nothing that reaches outside the workspace, and erased after seven days. Claiming copies its files into the person's own workspace and the agent carries on as them.

A shell and no MCP client? Use the CLI

npx @thedriveai/cli login (the person approves a code), npx @thedriveai/cli signup (no account yet; prints the claim link), then ls, tree, cat, put, mkdir, mv, rename, trash, undo, ask, or tool <name> for anything else. Nothing to install; credentials stay in ~/.config/thedrive. A skill with the whole recipe: npx skills add thedriveAI/skills, or read it at https://thedrive.ai/skills/the-drive-ai/SKILL.md.

The person approves, not you

A change that needs agreement is parked for the person to decide in The Drive AI (Settings → MCP → Waiting for you), with a notification. You are given an id to follow with approval_status; approving runs the recorded call as them. A chat host asks in its own interface instead; the person can switch either way per connection. An account you made for yourself has nobody to ask until it is claimed, so until then you confirm your own changes, and sharing is refused outright.

readAnything that only looks: find, read, list, who has access
writeChange the person's own files: propose, apply and undo changesets, save files
shareChange who can reach their files
askRun The Drive AI agent on the person's task allowance

https://service.thedrive.ai/.well-known/oauth-authorization-server

Everything an agent needs is in that document. The briefing written for agents is at thedrive.ai/agents.md.

Requirements and limits

A The Drive AI account, signed in with Google, Microsoft, Apple, or email. Sign up. An agent without one can sign itself up and hand the account to you (above).
Connected drives need the Max plan or any Team plan; workspace files work on every plan. See plans.
Copies and moves between two clouds go a folder at a time: up to 2,000 files or 2 GB, and files up to 100 MB each.
Sharing tools cover workspace files; they don't change Google, Microsoft, or Dropbox permissions.
Direct tool calls don't count as assistant tasks. agent_ask does, because it starts a full agent run.

Questions

Is there an MCP server for Google Drive, OneDrive and Dropbox?

Yes. The Drive AI MCP server gives Claude, ChatGPT and other MCP clients one set of tools across Google Drive (including shared drives), OneDrive, SharePoint, Dropbox, and The Drive AI workspace.

Can Claude or ChatGPT undo changes made through the connector?

Yes. Every change is recorded as a changeset, and changeset_undo reverses it as a whole: moves, renames, edits, and trashed files.

Do direct tool calls use assistant tasks?

No. Reading, searching, proposing, and applying changes do not count as tasks. agent_ask does, because it starts a full run of The Drive AI agent.

Do I need a Google account to connect?

No. You sign in with your The Drive AI account, whichever way it signs in: Google, Microsoft, Apple, or email. On first use you see what the assistant may do and allow it, and Settings → MCP disconnects it at any time.

Can an agent connect without a browser, or without an account?

Yes. An agent registers as a client of its own and signs in by code: it shows you eight letters, you approve them on thedrive.ai. An agent with no account can sign itself up and send you a claim link; the account stays small and sealed until you claim it, and is erased after seven days if nobody does.

Who approves what an agent changes?

You do. In Claude or ChatGPT the question appears in the chat. For an agent of its own, the change waits in Settings → MCP under Waiting for you, with a notification, until you approve or decline it.

Which plan do I need?

Any plan works with files in The Drive AI workspace. Working in connected Google Drive, OneDrive, SharePoint, or Dropbox accounts needs the Max plan or any Team plan.

A longer walkthrough is in MCP server for Google Drive, OneDrive and Dropbox.