Ask Claude anything about your Google Drive.

Your files, index and embeddings never go to a Corpusly cloud. There is no Corpusly server, and all indexing and embedding happens on your own machine. The one exception: when you ask a question, Corpusly sends the relevant passages to the AI assistant you've connected (such as Claude) so it can answer, and that provider's privacy terms apply to them.

When Claude searches your Drive through Corpusly, Corpusly returns only the passages relevant to your question, and those are sent to Claude through your existing Claude connection so it can answer. Corpusly doesn't control how your AI provider processes or retains that content, so its terms and privacy settings still apply.

Claude Desktop, Claude Code and OpenClaw today, over the open Model Context Protocol (MCP). ChatGPT support is coming soon. Because Corpusly is a standard MCP server, any MCP-compatible client can connect to it.

It's a good fit for a lot of work, and if it covers yours, use it. Google publishes a Drive connector in Claude's directory, and it's genuinely handy for pulling up a document you can already name. Corpusly solves a different problem, and three differences are worth knowing. Formats: the connector's own tool definitions list the file types it can turn into text, namely Google Docs, Sheets and Slides, PDFs, Word, Excel, PowerPoint, OpenDocument and images. Plain text, Markdown, CSV, JSON, source code, notebooks, email archives, EPUB, Rich Text and HTML aren't on that list, and neither are Google Drawings or SVG; Corpusly reads all of them. Search: the connector searches Drive by keyword, so you need to guess the words in the file. Corpusly searches by meaning, so it finds the right passage when the wording is different. Access: Google's connector includes tools for creating and copying files, so it asks to write to your Drive. Corpusly only ever asks to read. That said, Corpusly still sends the passages it retrieves to Claude, where Anthropic's terms apply. What's different is that your index and everything you didn't ask about stay on your machine.

Drive search is excellent at finding a file when you know roughly what it's called. It's not built to answer a question from what's inside your files. Corpusly reads the contents, understands them semantically, and lets your assistant answer from them with citations you can open. You can ask what a contract says instead of hunting for the contract.

Corpusly is a different approach, not a rival to any one assistant. It lets you keep the assistant you already use, indexes your Drive locally instead of relying on a hosted service, reads more file types (including scanned PDFs and images via OCR), gives you transparent citations you can open, and keeps the retrieval layer under your control. If Google's built-in features fit your needs, they're a fine choice too.

Read-only. You sign in with Google and grant read access; Corpusly can never modify, move or delete anything in your Drive.

Very large. Corpusly catalogs your entire Drive in seconds, then embeds documents the moment you first search them, so you're searchable right away without waiting for a full index to finish.

Most of what real work lives in: Google Docs, Sheets, Slides and Drawings; Microsoft Word, Excel and PowerPoint, including the legacy .doc, .xls and .ppt formats and template and macro-enabled files like .docm, .xlsm and .pptm; OpenDocument (.odt, .ods, .odp, .odg) and its templates; PDFs; images; SVG; EPUB; Rich Text (.rtf); HTML; email messages and mailbox archives (.eml and .mbox); Jupyter and Colab notebooks; and plain text, Markdown, CSV, XML, YAML, source code and JSON. Corpusly reads scanned PDFs and images with built-in OCR, and skips anything it can't extract text from rather than uploading it.

Yes, both. Corpusly runs optical character recognition (OCR) on scanned, image-only PDFs and on image files such as screenshots, photographed receipts or contracts, and whiteboard snapshots, so the text locked inside them is indexed and searchable just like a native document. The OCR runs entirely on your own device, so your images and scans are never uploaded.

If your email lives in your Drive as a file, yes. Corpusly indexes both single messages (.eml) and entire mailbox archives (.mbox), including the Gmail archives Google Takeout produces. It makes the Subject, From, To and Date headers and the message body searchable, and it extracts attachments inline, so a PDF or contract attached to an email is indexed too. Corpusly reads these files from your Drive on your own machine; it doesn't connect to your live inbox or mail server.

The Model Context Protocol is an open standard that lets AI assistants connect to external tools and data. Corpusly exposes your Drive to Claude as an MCP server, so your assistant can search it directly.

The engine at the core of Corpusly, the part that indexes your Drive and runs your searches, is source-available. Anyone can read the code, run it, and check what it does; we're publishing it shortly. It's under a fair-source license rather than a classic open-source one, but none of what it does with your files is hidden. The embedding model it uses is open source and runs on your own machine. The desktop app that wraps the core in a one-click interface is a separate, closed-source product.

The core engine is free and source-available, yours to run at no cost. The full-featured desktop app is still in early access. Request an invite and we'll share its pricing as we roll out.

Right now the core runs from the command line, so if you're comfortable in a terminal you can set it up today. For everyone else, a full-featured desktop app is on the way. It does the setup for you, so you never have to touch a command line. Request early access to get it as soon as it's ready.