Google Drive access must be enabled for the deployment and authorized for your workspace. Google sign-in alone does not connect Drive.
From project brief to connected resource.
Create a Google Doc from plain text and track it as a resource in your project. Export supported connected Google files to a PDF stored in Drive. Open the original from the workspace and follow the relationship between the source and its output.
- Create plain-text Google Docs; rich document editing is outside this release.
- Track managed file metadata changes, including rename proposals.
- Archive an MCPBinder record without deleting the original.
- Move a connected original to Google trash only through the explicit file action.
Connect the account you intend to use.
- Open Sources & accounts under Connections in your workspace and register the Google account’s email address.
- Choose Connect Google Drive and authorize the same account in Google’s consent screen.
- Return to the workspace and confirm the account is connected.
- If an agent needs file actions, explicitly include this account and the required resource permissions in its grant.
Per-file access, with a concrete limit.
The connection requests Google’s drive.file permission. This release creates its own files; it does not include a Google Picker/import workflow to authorize arbitrary existing Drive files.
You can track and open other HTTPS file links, but adding a link alone does not give MCPBinder permission to export or trash that file. Google accounts are shared within the workspace, while each agent needs its own allowance to use provider credentials.
Queued is not the same as finished.
File actions run in the background. Wait for completion before relying on the resulting file or sharing its link. If Google access expires, reconnect the account. If creation stops for review, inspect Drive before starting another create operation.
See a project workflow