Skip to main content
Gmail Individual is a Dev Testing integration. Use it when one signed-in Google user should grant daoco access only to Gmail data available to that user during provider approval or testing. Google hosts the MCP endpoint for this connection.

Connect Gmail Individual

1

Enable Dev Testing

A workspace owner or admin must enable Dev Testing integrations in Settings -> Preview features.
2

Open the Gmail Individual card

Open Connections -> Integrations -> Dev Testing and choose Gmail Individual.
3

Approve Google OAuth

Choose Connect, sign in with the Google user, and approve Gmail read and compose scopes.
4

Verify safely

Confirm the row is healthy, then run a minimal read-only /integration proof such as listing labels. Do not prove access by reading message bodies, subjects, snippets, or recipients.

What the connection can do

Read work (search threads, read a message, list labels and drafts) runs as soon as you ask. Writing is two steps: the assistant can create a Gmail draft for review, and it can send mail (a new message, a reply, or an existing draft) once you approve that exact send in chat. Label, trash, and spam changes are not offered on this connection.

Workspace restrictions

If the Google account belongs to a restricted Workspace, a Google Workspace admin may need to trust the daoco OAuth app or allow these scopes:
daoco Google OAuth client ID:
This guide remains available for testing, but Gmail Individual is not part of the normal Mail & Calendar production category.