How to use Google Drive with Cursor
You want Google Drive inside Cursor so it can organize a scattered project folder, audit who can access sensitive files, prepare and share a project handoff, and retrieve Drive files for analysis — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Google Drive gateway
The gateway is the thing Cursor connects to, and it is where you decide which Google Drive tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your Google Drive tools
In the dashboard, create a gateway and pick the Google Drive tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Cursor
Cursor does not refresh MCP OAuth tokens automatically. For a persistent connection, set Authorization to “Arcade Headers” on the gateway in the dashboard.
-
Open MCP settings
Command Palette (⌘⇧P / Ctrl+Shift+P) → Open MCP Settings, then click “New MCP Server”.
-
Add the gateway to mcpServers
{ "mcpServers": { "mcp-arcade": { "url": "https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>" } } } -
Try it out
Ask Cursor to use one of your Google Drive tools.
Full Cursor guide in the docs steps verified 2026-08-13
Try these Drive prompts
Cursor can now act on your Google Drive account. Click a prompt to copy it.
Use scoped permissions and approvals to control file uploads, sharing, link access, and collaborator removal. Pair it with Contextual Access policies so an agent can organize files without changing who can access them.