Connect Google Drive to OpenCode
Give OpenCode governed access to Google Drive’s 16 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Google Drive to OpenCode in four steps
Admins approve the server once. Everyone in OpenCode then gets it through the same governed connection.
- 1
Approve Google Drive in Runlayer
Add Google Drive from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect OpenCode to Runlayer
Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Google Drive’s 16 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
OpenCode setup guide - 3
Sign in to Google Drive
Sign in the way Google Drive requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Google Drive from OpenCode
Google Drive’s approved tools appear in OpenCode. Every call is checked against policy and recorded.
Tools
16 Google Drive tools in OpenCode
Runlayer policy decides which of these OpenCode users can call. 5 read data only and 1 can change or delete data.
Copy file
Create a copy of a file in Google Drive.
Create doc from markdown
Create a beautifully formatted Google Doc from markdown content.
Create file
Create a new file in Google Drive with text or base64-encoded content.
Create folder
Create a new folder in Google Drive to organize files.
Delete file
Delete a file or folder by moving it to trash.
Fetch file
Fetch a file from Google Drive using its Google Drive file ID (don't use exa nor brave to read files).
Get metadata
Get detailed metadata about a specific file or folder, including size, ownership, sharing status, modification dates, and more.
List folder
List all files and folders within a specific folder.
Control
What Runlayer can see and stop in OpenCode
Some controls apply to every client at the gateway. Others depend on what OpenCode exposes to Runlayer.
Gateway policy (available)
Every Google Drive call from OpenCode passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.
Frequently asked questions
Connect more