CommsConnector
Google Drive
List, read, export, upload and share Google Drive files from Claude or ChatGPT via the Tulina MCP server, with each person authorizing their Google account.
Official site: drive.google.com
What it can do
4 read/2 write
- 01Read
List and search files and folders with a Drive query
- 02Read
Read a file, with PDFs and spreadsheets returned as text and CSV
- 03Read
Export a Google Doc, Sheet or Slides deck as markdown, CSV, xlsx, pptx or docx
- 04Write
Upload a file and convert it to a Google Doc, Sheet or Slides deck
- 05Write
Create folders, rename, move and delete files
- 06Read
List, grant and revoke who can access a file
Most of what a team knows is in a file somebody saved to Drive: the proposal template, the signed contract, the notes from last week's call. The Tulina connector lets an agent find those files, read them and put new ones back, under the Google account of the person who authorized it, then use what it read in the CRM, the inbox or a spreadsheet in the same conversation.
Does Google Drive have an MCP server?
Yes. Google documents a remote Drive MCP server at
drivemcp.googleapis.com. On the pages we read on 31 October
2026 it is part of the Google Workspace Developer Preview Program, so access
needs a membership in that program. It signs in with OAuth 2.0 and exposes
eight tools: search_files, list_recent_files, get_file_metadata,
read_file_content, download_file_content, create_file, copy_file and
get_file_permissions. Google lists Claude as a client, on its Enterprise,
Pro, Max or Team plans, through a custom connector.
Does Google support MCP?
For Workspace, Google's documentation describes one remote MCP server per product, covering Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat and Classroom, all marked as a developer preview. Setting one up means a Google Cloud project with the matching APIs enabled, an OAuth consent screen and an OAuth client created for an AI agent.
How do you connect Google Drive to Claude and ChatGPT?
Through Tulina's own MCP server, with no Cloud project of your own:
- In Tulina, open the Google Drive card and choose Authorize Google Drive. Google asks for the Drive scope only, on the account you pick.
- Repeat for a second account if you work across two; each call names the account it uses, and Tulina refuses a call rather than guess.
- Add
https://mcp.tulina.ai/mcpto Claude or ChatGPT and sign in with your Tulina account. The MCP page has the same link.
Google's Drive MCP server and Tulina's Drive connector
| Google's Drive MCP server | Tulina's Drive connector | |
|---|---|---|
| Status on the pages read | Developer preview, by membership | Available in Tulina |
| Setup | Cloud project, two APIs enabled, consent screen, OAuth client | One authorization on the Drive card |
| Scopes asked | drive.readonly and drive.file | The Drive scope |
| Read and search | search_files, read_file_content, list_recent_files | drive_file with list, metadata, download, export |
| Create and copy | create_file, copy_file | upload with conversion, create_folder |
| Rename, move, delete | Not among its eight tools | update and delete, which moves a file to the trash |
| Sharing | get_file_permissions | drive_access: list, grant, revoke |
| Next to your other tools | Google Drive | Drive plus the CRM, inbox and spreadsheet connectors |
If Drive is the only system in play and your Workspace admin is in the preview, Google's server is the shorter path. Tulina earns its place when a file is one step in longer work, such as reading a proposal from Drive, checking the deal in the CRM and drafting the reply in Gmail.
What you can ask it
"List the contracts modified this month in the Clients folder." The agent lists the folder with a date query and returns names, modification times and links.
"Read the Acme kickoff notes and write the three follow-ups." The agent exports the Google Doc as markdown, reads it and drafts the follow-ups. A spreadsheet comes back as CSV per tab, and a PDF as its extracted text.
"Share the proposals folder read-only with jane@example.com." The agent
grants the reader role through drive_access and says whether Google sent a
notification.
What runs on its own: a weekly sweep of a folder for new files can summarise them in Slack, and a sheet the team keeps in Drive can be read and updated through Google Sheets. The rest of the Google suite is in Google Workspace.
What the Drive connector can't do
- It acts as one Google account at a time, with that account's rights. An account that has not authorized Drive is refused, naming the card.
- A Google Doc, Sheet or Slides deck has no binary content to download. Read it
with
export;downloadis for uploaded files. - A spreadsheet read is bounded: 200 rows per tab by default and 5,000 at most, and the result says when it was truncated.
- Upload fetches a file of up to 25 MB, and only some types convert to a Google format.
deletemoves a file to the trash and cannot be undone through the API. Sharing changes live in a separate tool on purpose.- There is no tool for comments or revision history.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Google Drive once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Google Drive at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Google Drive returns something usable instead of something generic.
Processes that run on Google Drive
None published yet.