Google Drive Labels integration
Google Drive Labels integration for AI agents.
Google Drive Labels integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Google Drive Labels tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
What your agents can do
Real Google Drive Labels actions, managed and audited.
Your user connects Google Drive Labels once; your agent can then secure AI-agent actions — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants Google Drive Labels access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Tools & triggers
Supported Google Drive Labels tools.
17 tools are generated from the published Google Drive Labels catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 17 tools. All published catalog entries are included in this page's server-rendered HTML.
- Drivelabels Labels Create
- Creates a label. For more information, see [Create and publish a label](https://developers.google.com/workspace/drive/labels/guides/create-label).
- labels
- Drivelabels Labels Delta
- Updates a single label by applying a set of update requests resulting in a new draft revision. For more information, see [Update a label](https://developers.google.com/workspace/drive/labels/guides/update-label). The batch update is all-or-nothing: If any of the update requests are invalid, no changes are applied. The resulting draft revision must be published before the changes may be used with Drive items.
- labels
- Drivelabels Labels Disable
- Disable a published label. For more information, see [Disable, enable, and delete a label](https://developers.google.com/workspace/drive/labels/guides/disable-delete-label). Disabling a label will result in a new disabled published revision based on the current published revision. If there's a draft revision, a new disabled draft revision will be created based on the latest draft revision. Older draft revisions will be deleted. Once disabled, a label may be deleted with `DeleteLabel`.
- labels
- Drivelabels Labels Enable
- Enable a disabled label and restore it to its published state. For more information, see [Disable, enable, and delete a label](https://developers.google.com/workspace/drive/labels/guides/disable-delete-label). This will result in a new published revision based on the current disabled published revision. If there's an existing disabled draft revision, a new revision will be created based on that draft and will be enabled.
- labels
- Drivelabels Labels Get
- Get a label by its resource name. For more information, see [Search for labels](https://developers.google.com/workspace/drive/labels/guides/search-label). Resource name may be any of: * `labels/{id}` - See `labels/{id}@latest` * `labels/{id}@latest` - Gets the latest revision of the label. * `labels/{id}@published` - Gets the current published revision of the label. * `labels/{id}@{revision_id}` - Gets the label at the specified revision ID.
- labels
- Drivelabels Labels List
- List labels. For more information, see [Search for labels](https://developers.google.com/workspace/drive/labels/guides/search-label).
- labels
- Drivelabels Labels Publish
- Publish all draft changes to the label. Once published, the label may not return to its draft state. For more information, see [Create and publish a label](https://developers.google.com/workspace/drive/labels/guides/create-label). Publishing a label will result in a new published revision. All previous draft revisions will be deleted. Previous published revisions will be kept but are subject to automated deletion as needed. For more information, see [Label lifecycle](https://developers.google.com/workspace/drive/labels/guides/label-lifecycle). Once published, some changes are no longer permitted. Generally, any change that would invalidate or cause new restrictions on existing metadata related to the label will be rejected. For example, the following changes to a label will be rejected after the label is published: * The label cannot be directly deleted. It must be disabled first, then deleted. * `Field.FieldType` cannot be changed. * Changes to field validation options cannot reject something that was previously accepted. * Reducing the maximum entries.
- labels
- Drivelabels Labels Revisions Locks List
- Lists the label locks on a label.
- labels
- Drivelabels Labels Revisions Permissions BatchDelete
- Deletes label permissions. Permissions affect the label resource as a whole, aren't revisioned, and don't require publishing.
- labels
- Drivelabels Labels Revisions Permissions BatchUpdate
- Updates label permissions. If a permission for the indicated principal doesn't exist, a label permission is created, otherwise the existing permission is updated. Permissions affect the label resource as a whole, aren't revisioned, and don't require publishing.
- labels
- Drivelabels Labels Revisions Permissions Create
- Updates a label's permissions. If a permission for the indicated principal doesn't exist, a label permission is created, otherwise the existing permission is updated. Permissions affect the label resource as a whole, aren't revisioned, and don't require publishing.
- labels
- Drivelabels Labels Revisions Permissions Delete
- Deletes a label's permission. Permissions affect the label resource as a whole, aren't revisioned, and don't require publishing.
- labels
- Drivelabels Labels Revisions Permissions List
- Lists a label's permissions.
- labels
- Drivelabels Labels Revisions UpdatePermissions
- Updates a label's permissions. If a permission for the indicated principal doesn't exist, a label permission is created, otherwise the existing permission is updated. Permissions affect the label resource as a whole, aren't revisioned, and don't require publishing.
- labels
- Drivelabels Labels UpdateLabelCopyMode
- Updates a label's `CopyMode`. Changes to this policy aren't revisioned, don't require publishing, and take effect immediately.
- labels
- Drivelabels Labels UpdateLabelEnabledAppSettings
- Updates a label's `EnabledAppSettings`. Enabling a label in a Google Workspace app allows it to be used in that app. This change isn't revisioned, doesn't require publishing, and takes effect immediately.
- labels
- Drivelabels Limits GetLabel
- Get the constraints on the structure of a label; such as, the maximum number of fields allowed and maximum length of the label title.
- limits
FAQ
Google Drive Labels integration, answered
- How do AI agents use Google Drive Labels through Open Connector?
- Your user connects Google Drive Labels once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Drive Labels tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Google Drive Labels MCP server?
- Yes. Open Connector can serve Google Drive Labels as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Drive Labels actions with credentials injected server-side.
- Where do Google Drive Labels credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Google Drive Labels — keep the keys.
Open source, self-hostable, with Google Drive Labels credentials that never leave your infrastructure. Run it from source today.