Google Drive MCP: Google's server, and Drive folders as ad creatives

Yes, and by two routes. The Google Drive MCP server Google runs is at https://drivemcp.googleapis.com/mcp/v1, documented under Configure the Drive MCP server and published as a Developer Preview, available through the Google Workspace Developer Preview Program. The same address sits behind the Google Drive connector in Claude's directory, made by Google, marked Anthropic verified, added in March 2026, with Sign-in required as its only setup.

Google's guide describes the server as a standardized way for AI agents to read data (search files, retrieve metadata, read file content), take action (create files, download content) and respect security, inheriting the permissions of the signed-in user. Authentication is OAuth 2.0 with two scopes, drive.readonly and drive.file. The guide names Google Antigravity and Claude as the clients it documents, and gives a generic recipe for any client that takes a server URL, Streamable HTTP and OAuth.

Google Drive is not in google/mcp, the GitHub repository that lists Google's official MCP servers: that list is Google Cloud products plus an open-source Workspace server for Docs, Sheets, Slides, Calendar and Gmail. Drive's server lives instead in the Workspace developer documentation, next to dedicated servers for Gmail, Docs, Sheets, Slides, Calendar, Chat and the People API, each with its own tools and its own googleapis.com host.

Google's guide lists eight tools: copy_file, create_file, download_file_content, get_file_metadata, get_file_permissions, list_recent_files, read_file_content and search_files. The connector page in Claude's directory lists eleven, adding share_file, trash_file and update_file. Its description is the plain version: find documents without the exact name, read and analyze Google Docs, Sheets, Slides and PDFs, upload files to Drive, and organize files scattered across a Drive.

It writes. create_file and copy_file are in both lists; update_file, share_file and trash_file on the directory page change, share or bin a file. Google's own page is explicit about the risk: a client with these tools can read, modify and delete data in your Google account, so Google asks you to connect only trusted applications, to avoid processing documents from unverified sources, and to review every action the client takes.

What it does not hold is anything about advertising. A Drive folder of statics and videos is a list of files to Google's server, with a name, a type and permissions; nothing says which ratio each file has, which ones already ran as ads, or what they returned. That is the part Adrails reads.

• Reads: file search, recent files, metadata, permissions, Docs, Sheets, Slides and PDF content
• Writes: create, copy, update, share and trash files, within the signed-in user's permissions
• Scopes: drive.readonly and drive.file; status: Developer Preview

Adrails connects Google Drive as a creative source, not as a tool server. In Adrails, open Integrations, choose Google Drive and allow read-only access in the Google window; Adrails asks Google for drive.readonly and nothing more. Or ask your assistant for a setup link with integrations_connect, valid for 10 minutes and opened by an owner or admin.

Adrails reads only the folders you point to, and only when you use them. The drive_folder tool takes a folderId, or a query to find folders whose name contains a word, and returns every image and video down to three folder levels with its path, ratio, pixel size, duration and file size, grouped the way Adrails would use them in ads. Adrails keeps the identifiers, names and types of the files, not copies of their content, and never changes, moves or deletes anything in Drive; you can revoke the access from your Google account permissions at any time.

There is no sync schedule because there is nothing to sync: Drive is read on request, where Shopify orders or Triple Whale figures are refreshed on a cadence. integrations_status lists the connection with the other sources of the workspace, and integrations_disconnect revokes it.

The reason to read a Drive folder is to launch from it. launch_brief is the first step of any new Meta launch: pass what the person said or chose, with source set to drive_folder and the folderId, and it returns what a clean launch still needs as questions with options: the ad account, where the ads go, then objective, pixel and event, countries, languages, budget, dates, Page, EU beneficiary, link and copy. Two more inputs, formats (send_missing or as_is) and layout (one_ad_set, ad_set_per_ad or campaign_per_ad), fix how the files are prepared and how the campaign is laid out.

When nothing is missing, campaigns_launch takes the complete brief and returns a proposal with a review link, not a campaign. Applied in Adrails, it sends the Drive files to the ad account, then builds the campaign, ad sets and ads, all paused. campaigns_launch_activate is a second proposal that switches on what the launch created and lists every budget that starts spending. Nothing reaches Meta before the review, and what Adrails creates starts paused.

Around the launch, campaign_media lists the images and videos an ad account already holds on Meta or Google Ads, or uploads one PNG, JPEG or GIF of at most 512,000 bytes; larger files and videos go through the uploader in Campaigns. creative_insights then groups the Meta ads by the image or video they use, across ads and accounts, with performance, winners, fatigue and repeated use, which is how the folder's creatives are judged once they have spent. The launch tools serve Meta Ads today and, once your workspace can connect it, Google Ads.

• List the folder with ratio, size and duration: drive_folder
• Ask what the launch still needs: launch_brief with source drive_folder
• Send the files and build everything paused: campaigns_launch, a proposal

Connect Google's server when the work is in the files: find the brief, read the offer sheet, pull last quarter's figures out of a Sheet, save a summary as a new Doc, share it with the team. It is the complete tool set for a Drive, and it writes, so take Google's advice and keep it away from documents you do not trust.

Connect Adrails when the folder is the starting point of a campaign: which creatives are there and in which ratios, which to group into one ad set, what a launch still needs, and later which of those ads is fatiguing. Adrails never writes to Drive, and a launch is a proposal you apply in Adrails; the campaign starts paused, and a budget move is capped at 30% per change.

Both at once is a natural setup in Claude: the two servers do not overlap. Ask Google's server for the brief, ask Adrails to list the folder and prepare the launch, and let the assistant carry the brief's claims into the copy. Each server signs in on its own account, Google's with drive.readonly and drive.file, Adrails with drive.readonly only.

For Google's server, the short route is the directory: open the Google Drive connector in Claude, choose Add to Claude and sign in with Google. The long route is Google's guide, for Claude Enterprise, Pro, Max or Team: create an OAuth client in your Google Cloud project with https://claude.ai/api/mcp/auth_callback as the redirect URI, enable the Google Drive API and the Google Drive MCP API, then add a custom connector in Claude with https://drivemcp.googleapis.com/mcp/v1 as the server URL and the client ID and secret under Advanced settings. Any other client takes the same URL, Streamable HTTP and OAuth 2.0.

For Adrails, add https://adrails.ai/api/mcp as a custom connector in Claude under Customize, then Connectors, keeping Use Claude's published identity; run claude mcp add --transport http adrails https://adrails.ai/api/mcp in Claude Code; in ChatGPT, turn on Developer mode and add a custom MCP server with OAuth as its authentication. Sign in to Adrails, choose the workspace and the permissions, and allow access. A launch needs Prepare advertising changes and an owner or admin role.

Then connect Google Drive inside Adrails, under Integrations, with read-only access, or ask the assistant for a setup link with integrations_connect. Mention a folder by name: drive_folder finds it from the query and lists what it holds, and launch_brief with source drive_folder starts the questions. The first proposal arrives with its review link, and nothing has been applied until you open it.

• Google's server: Add to Claude from the directory, or the URL plus your own OAuth client
• Adrails: https://adrails.ai/api/mcp as a custom connector, OAuth sign-in
• Google Drive in Adrails: Integrations, read-only access, folders read on request