Every drive you own. One safe connection for your AI.

Claude's Drive connector sees one Google account. Crossdrive sees all of them, plus OneDrive and Dropbox in beta, through a single URL you host yourself.

Get it on GitHub Deploy guide

assistant · crossdrive

What it does

Every account, one connection

Connect several Google accounts and give each a label. Your assistant addresses files as work:/Finance/2026 or personal:/Taxes and searches across all of them at once.

Across clouds (BETA)

Move and copy files and whole folders between accounts, and between Google Drive, OneDrive and Dropbox, without downloading anything to your laptop. OneDrive and Dropbox support is beta and not yet tested against live accounts.

Gmail, draft-only by default

Search and read mail in each connected Gmail account, save attachments to the right folder, and prepare replies. Sending stays off until you turn it on per account.

Works from your phone

It is a remote MCP server: one URL works in Claude, ChatGPT and any MCP client, on desktop, web and the mobile apps.

Safety is in the code

These rules are enforced by the server, not by a prompt. An assistant that misreads a request still cannot get past them.

Trash only

There is no permanent-delete call in the code. Deleting means moving to the provider's trash, where you can restore it.

Read-only accounts

Mark any account read-only and the server rejects every write to it, whatever the assistant asks for.

Dry run, then undo

Most writes can be previewed with a dry run first. Moves, renames and trashes are logged with an id that undo can roll back.

Audit log

Each write is recorded with time, client, account, action and file ids. File contents and mail bodies are not logged.

Per-client consent

No client gets a token until you sign in and approve it. Clients that should only look can be given read-only access.

Content is data

Text inside files and emails is returned as untrusted data. Instructions found in a document never become tool calls on their own.

Your instance, your keys

You deploy it to your own Vercel account.
It signs in to Google with your own Google Cloud project and OAuth client.
Refresh tokens are encrypted at rest (AES-256-GCM) in storage you own.
No third-party service sits between your assistant and your files. The code is MIT licensed.

How it compares

Where it helps: if you have several Google accounts, Crossdrive puts them under one URL with labels you choose, and search fans out across them. The built-in connector sees one account per connector.
Where it is narrower: on Google it covers Drive and Gmail only, by design. For Docs editing, Sheets formulas or Calendar, use another server; running both is fine.
Where it costs more effort: you bring your own Google Cloud project and a Vercel deploy. With a single Google account and a wish to chat with your files, the built-in connector is the least work.

A fuller, sourced table is in the README.

Get started in five steps

Create a Google OAuth client in your own Google Cloud project with the Drive and Gmail APIs enabled. Step by step.
Deploy to Vercel with the deploy button in the README, attach a Blob store, and paste the client id and secret. Generate the two secrets with openssl rand -base64 32.
Add the redirect URIs <your URL>/api/google/callback and <your URL>/oauth/google-callback to the Google client, then redeploy. Open <your URL>/setup for a checklist of what is missing.
Connect your accounts at <your URL>/connect: pick a label such as work or personal and sign in. New accounts start as read + write with mail as drafts only.
Add the connector to your AI client using <your URL>/api/mcp, then ask "search all my drives for the 2026 lease". In Claude Code:

claude mcp add --transport http crossdrive https://YOUR-DEPLOYMENT.vercel.app/api/mcp

OneDrive and Dropbox support is beta and not yet tested against live accounts.

Want a hosted version?

A hosted, no-setup version is being considered. If that would be useful to you, say so in GitHub Discussions.

Tell us in Discussions