Google Workspace
Search mail and Drive through the Google Workspace MCP servers, and choose which AI agents can send or edit
An agent with Google Workspace can search mail, read Drive files, and find free time, but it can also send Chat messages, delete calendar events, and edit Docs and Sheets. One resource covers Gmail, Drive, Calendar, Chat, People, Sheets, Docs, and Slides. Adding Google Workspace here puts each tool behind a policy rule and records each call in the audit log, so you decide which agents can message, schedule, or edit and which can only read.
Credential modes
Google Workspace supports bring your own app only. Google does not support dynamic client registration, and its Workspace scopes are classed as sensitive and restricted, so your organization registers its own OAuth client in a Google Cloud project you control and supplies the client ID and secret. Owning the client keeps consent, scope review, and revocation inside your own tenant. See Credential modes for how the modes compare.
Before you begin
- Google Cloud – permission to create a project under your Cloud organization. The project needs your Cloud organization as its parent to use the Internal consent audience. It may also need a billing account, if Enable the APIs returns a billing error.
- Developer Preview – Google's acceptance of that project. You apply during setup, and acceptance usually takes about a day.
- Google Workspace accounts – one for every user who will use these tools. Consumer Gmail accounts can connect, but the Chat and directory tools only return data for Workspace accounts.
- Google Workspace super admin – to configure the OAuth consent screen and trust the OAuth client in the Admin console.
- Agent Authority administrator – to add the resource.
Administrator setup and per-user consent
Setup has two parts:
- Administrator setup – an administrator completes Create the Cloud project through Add Google Workspace in Agent Authority once, for the whole organization.
- Per-user consent – each user signs in to Google once, in Connect your Google account, before their own tool calls run.
Setup
Keep three consoles open
Setup moves between Google Cloud, the Google Admin console, and the Agent Authority console. You do most of the work in Google, copy a redirect URI from Agent Authority in Create the OAuth client, and return there to paste the credentials in Add Google Workspace in Agent Authority.
1. Create the Cloud project
Create the project under your Cloud organization. The organization parent is what makes the Internal consent audience available in Configure the Google Auth Platform.
-
Sign in to console.cloud.google.com with an account in your Workspace organization, and open Cloud Shell, which has the gcloud CLI built in. Or run the commands in a terminal on your own computer, after you install the gcloud CLI.
-
List your organizations and note the
ID:gcloud organizations list -
Create the project with that organization as its parent. Choose both values first:
PROJECT_ID– starts with a letter; 6 to 30 lowercase letters, digits, or hyphens, not ending in a hyphen. You can't change it later, or reuse an ID from a deleted project. For example,sa-aa-gws.PROJECT_NAME– the display name; 4 to 30 characters. For example,SA Agent Authority GWS.
The
--set-as-defaultflag switches Cloud Shell to the new project:gcloud projects create PROJECT_ID --name="PROJECT_NAME" --organization=ORG_ID --set-as-default -
Confirm the project is
ACTIVEunder your organization, and note the project number. You need it to enroll in the Workspace Developer Preview.gcloud projects describe PROJECT_ID --format="value(projectId,projectNumber,lifecycleState,parent.id)"
2. Enroll in the Workspace Developer Preview
Google offers the Workspace MCP servers only to projects enrolled in its Developer Preview Program. Google takes about a day to approve your application. You can do the rest of the setup while you wait.
-
Open developers.google.com/workspace/preview, and sign in with an account on your Workspace domain.
-
Click Apply to join the Developer Preview Program.
-
In the form, enter:
- Workspace email – the account to grant access. Gmail addresses, service accounts, and Google Groups are not accepted.
- Google Cloud project number – the number you noted in Create the Cloud project, not the project ID.
-
Submit the form.
Google sends a confirmation email when the project is registered.
Until registration is confirmed, every tool call fails
While registration is pending, calls fail with The caller does not have permission, no matter which scopes you publish, whether the client is
trusted, or how valid the token is. Submitting the form is not enough: wait
for the confirmation email before you test tool calls.
3. Enable the APIs
Every Workspace product needs two services enabled: its product API and its MCP service.
The gateway sends each tool call to the product's MCP service, so that product's tools fail until its MCP service is enabled.
People (Google's contacts and directory product) is the one exception: people.googleapis.com serves both.
Run the commands below, or enable the services under APIs & Services → Library.
If Cloud Shell prints Regional Access Boundary … Gaia id not found after a command, you can ignore it.
The command still succeeds.
- Enable the product API for each product:
gcloud services enable gmail.googleapis.com --project=PROJECT_ID gcloud services enable drive.googleapis.com --project=PROJECT_ID gcloud services enable calendar-json.googleapis.com --project=PROJECT_ID gcloud services enable chat.googleapis.com --project=PROJECT_ID gcloud services enable people.googleapis.com --project=PROJECT_ID gcloud services enable sheets.googleapis.com --project=PROJECT_ID gcloud services enable docs.googleapis.com --project=PROJECT_ID gcloud services enable slides.googleapis.com --project=PROJECT_ID - Enable the MCP service for each product.
These are separate from the product APIs, and they are the ones most often missed.
gcloud services enable gmailmcp.googleapis.com --project=PROJECT_ID gcloud services enable drivemcp.googleapis.com --project=PROJECT_ID gcloud services enable calendarmcp.googleapis.com --project=PROJECT_ID gcloud services enable chatmcp.googleapis.com --project=PROJECT_ID gcloud services enable sheetsmcp.googleapis.com --project=PROJECT_ID gcloud services enable docsmcp.googleapis.com --project=PROJECT_ID gcloud services enable slidesmcp.googleapis.com --project=PROJECT_ID gcloud services enable people.googleapis.com --project=PROJECT_ID # serves both the product API and MCP - Confirm that every service from both lists is enabled:
gcloud services list --enabled --project=PROJECT_ID | grep -iE "gmail|drive|calendar|chat|people|sheets|docs|slides"
Two services are easy to get wrong
- Calendar's product API is
calendar-json.googleapis.com, notcalendar.googleapis.com. - People has no separate MCP service:
people.googleapis.comserves both. - Every other MCP service is named
<product>mcp.googleapis.com.
If an enable command fails with a billing error
Link a billing account to the project under Billing → Link a billing account, then run the command again.
Configure the Chat app
Google's Workspace MCP documentation says the Chat MCP server needs a Chat app configured in the same project. Under APIs & Services → Google Chat API → Configuration, set an app name and avatar, and leave interactive features disabled, because the gateway doesn't receive Chat events. Without a Chat app, expect the Chat tools to fail. The other Google Workspace products don't depend on it.
4. Configure the Google Auth Platform
A new project runs a setup wizard before you can create a client.
-
In the Cloud Console, open Google Auth Platform.
Check that the project picker shows your
PROJECT_ID. -
Click Get started.
-
Complete each wizard step:
- App Information – enter the App name users see on the consent screen, for example
SA Agent Authority Google Workspace. Then choose a User support email. - Audience – choose one:
- Internal – every user who connects is in your Workspace organization. Google skips its verification review and the Cloud Application Security Assessment (CASA).
- External – you connect accounts outside your organization. The restricted Workspace scopes trigger verification and a CASA. While the app is in Testing, only the test users you list can connect.
- Contact Information – enter the Email address Google uses to notify you about project changes.
- Finish – select I agree to the Google API Services: User Data Policy, click Continue, then Create.
- App Information – enter the App name users see on the consent screen, for example
On a project that is already configured, change these settings under Branding and Audience.
5. Create the OAuth client
One OAuth client serves every Google Workspace product, so you create it once.
- In Google Cloud, go to Google Auth Platform → Clients → Create client.
- Fill in the client:
- Application type – select Web application.
- Name – enter a name, for example
SecureAuth Agent Authority Google Workspace. Only the Cloud Console shows it. - Authorized redirect URIs – click Add URI, and paste the Redirect URI from MCP Servers & Tools → Add Resource → Google Workspace in Agent Authority.
It has the form
https://oauth.aisecurity.services.<region>.connect.secureauth.com/auth/callback. - Use this client for an AI-powered agent – optional. The connection works with it cleared.
- Click Create, then copy the Client ID and Client secret.
Copy the client secret before you close the dialog
You can't view the secret again after you close it. Store it securely, or click Download JSON.
6. Publish the scopes
Users can consent only to scopes you publish here. Publish the full set so every Google Workspace tool works.
-
Go to Google Auth Platform → Data Access → Add or remove scopes.
-
Select every scope under Required scopes.
The list shows only scopes for the APIs you enabled in Enable the APIs.
Don't use the select-all checkbox. It also selects unrelated scopes, such as BigQuery and
cloud-platform. -
For a scope that isn't in the list, paste it under Manually add scopes, then click Add to table.
-
Click Update, then Save.
A scope missing from Data Access fails consent for everyone
Every scope the resource requests must be present on Data Access, or
consent fails with invalid_scope.
7. Trust the app in the Admin console
Google Workspace blocks these scopes for every user until you trust the OAuth client, even after a user consents. One trust covers every Google Workspace product, because they share one client.
- In the Google Admin console, go to Security → Access and data control → API controls → Manage App Access → Configure new app.
- Search for the Client ID from Create the OAuth client, and select the app.
- Set the access:
- Scope – keep the top organizational unit to cover all users, or select the organizational units whose users connect.
- Access to Google Data – select Trusted.
- Click Continue, review the summary, and click Finish.
If the setting shows Overridden for an organizational unit, check that it covers the connecting user, or set Trusted at the top organizational unit.
Each connecting user in your organization must be Active, with a Google Workspace or Cloud Identity license.
Test once, after the change applies
Admin changes usually take a few minutes, and Google allows up to 24 hours. Make one change, wait, then test once.
8. Add Google Workspace in Agent Authority
Give Agent Authority your OAuth client, so it can connect your users to Google Workspace. The catalog already holds the product endpoints, OAuth URLs, and scopes, so you enter only the client credentials.
-
In the Agent Authority console, go to MCP Servers & Tools → Add Resource → Google Workspace.
-
Check that the Redirect URI matches the one on your OAuth client.
-
Paste the Client ID and Client Secret.
-
Leave Token endpoint authentication on Auto-detect.
-
Click Add.
Agent Authority adds every Google Workspace product and its tools under one resource.
An Admin setup required dialog links back to this guide. You've completed the setup, so click Close.
-
Go to Agent Access, and check that a rule allows the Google Workspace tools.
Agents see only the tools a rule allows. Every organization starts with an Allow all rule, which covers them unless you've changed it.
Connect your Google account
Each user, starting with you, connects their own Google account once, so their tool calls run with their own Google permissions. A user connects in either of two ways:
- From the user portal – go to Connections and click Connect next to Google Workspace.
- From an agent – the first time the agent calls a Google Workspace tool, the gateway returns a sign-in link. The user opens it and signs in with their Workspace account.
Google's consent screen lists every permission you published. The user reviews it and clicks Allow.
The page confirms Connected to Google Workspace!, and Connections shows Google Workspace as Connected.
Each user's own Workspace permissions control what they can reach. The gateway doesn't widen access beyond what the user could already do in Google Workspace.
Users need to reconnect after you change the setup
If you edit the resource, publish new scopes, or trust the client after users connect, their connections keep the old permissions. Each user needs to reconnect: in the user portal, go to Connections, click Disconnect next to Google Workspace, then click Connect.
Verify the connection
A test request confirms your agent reaches Google Workspace through the gateway.
-
Ask your agent one of these:
-
Quick check – confirms the connection works.
Show my Google Workspace profileYour name and email mean the connection works.
-
Full check – confirms each product answers, including a write.
Using Google Workspace, list my Gmail labels, my next three calendar events, and my most recent Drive files, then create a spreadsheet named Connector Test and write hello in cell A1.Results from each product mean every product is connected.
The request creates a real spreadsheet, so delete Connector Test from Drive afterwards.
-
-
In the Agent Authority console, go to MCP Servers & Tools → Google Workspace, and check that each tool call appears under Recent Activity.
Each call is also recorded in the audit log.
Connect to some upstreams only
Each Google Workspace product is an upstream. Connect an agent to only the upstreams it needs, and it sees only their tools, which keeps its tool list short. Both options work only once Google Workspace is added to Agent Authority.
-
When you connect an agent – in the Agent Authority Connect your agent dialog, pick Google Workspace under Connect to. An Upstreams picker then appears: pick one or more. See Connect an agent.
-
In the gateway URL – append
?upstreams=with one or more upstream IDs, separated by commas:https://your-gateway-url/gateway/mcp/googleworkspace?upstreams=gmail,drive
The upstream IDs are gmail, drive, calendar, chat, people, sheets, docs, and slides.
An unknown ID returns 404.
Available tools
The tools below ship with the catalog entry, so they appear in tool lists and policy pickers as soon as the resource is installed. Each tool is routed to the Google MCP server that serves it. When the first user connects, the gateway refreshes the tool definitions from those servers, so the tools in the console can differ.
Gmail
| Tool | Tags | Description |
|---|---|---|
search_threads | read-only | Search email threads with Gmail query syntax (from:, to:, subject:, label:, is:, has:, newer_than:); returns snippets |
get_thread | read-only | Get an email thread by ID, including its messages |
get_message | read-only | Get a single email message by ID |
create_draft | write | Create a draft email, optionally as a reply on an existing thread |
list_drafts | read-only | List draft emails with Gmail-syntax query filtering and pagination |
list_labels | read-only | List all labels in the account; use to resolve label IDs before the labeling tools |
create_label | write | Create a label; supports nested labels, with parents created automatically |
label_thread | write | Add labels to an entire thread, current and future messages |
unlabel_thread | write | Remove labels from an entire thread |
label_message | write | Add labels to a specific message |
unlabel_message | write | Remove labels from a specific message |
apply_sensitive_thread_label | destructive | Trash or mark as spam an entire thread |
apply_sensitive_message_label | destructive | Trash or mark as spam a specific message |
get_draft | read-only | Get a single draft by ID, including its message content |
update_message_labels | write | Add and remove labels on a message in one call |
trash_thread | destructive | Move a thread to Trash |
untrash_thread | write | Restore a thread from Trash |
trash_message | destructive | Move a message to Trash |
untrash_message | write | Restore a message from Trash |
mark_thread_spam | destructive | Mark a thread as spam |
unmark_thread_spam | write | Remove a thread from spam |
mark_message_spam | destructive | Mark a message as spam |
unmark_message_spam | write | Remove a message from spam |
Gmail has no send tool. Agents can draft mail, and a person sends it from Gmail.
Drive
| Tool | Tags | Description |
|---|---|---|
search_files | read-only | Search files by title, full text, MIME type, modified or created time, parent, owner, and sharing |
list_recent_files | read-only | List recent files, sorted by recency or last modification |
get_file_metadata | read-only | Get general metadata for a file |
get_file_permissions | read-only | List the permissions of a file |
read_file_content | read-only | Read a text representation of a file (Docs, Sheets, Slides, PDF, Office formats, images), optionally with inlined comments |
download_file_content | read-only | Download a file's content as a base64-encoded string, with an export format for Google-native files |
create_file | write | Create or upload a file, including empty Docs, Sheets, Slides, and folders |
copy_file | write | Copy a file, optionally with a new title and parent folder |
Calendar
| Tool | Tags | Description |
|---|---|---|
list_calendars | read-only | List the user's calendars; use to resolve a calendar name to its ID |
list_events | read-only | List events on a calendar with optional time range, text, and event-type filters |
search_events | read-only | Semantic search of events on the user's primary calendar |
get_event | read-only | Get a single event by ID |
suggest_time | read-only | Suggest free time slots across the given attendees' calendars |
create_event | write, external | Create an event, with attendees, recurrence, Google Meet, reminders, and attachments supported |
update_event | write, external | Update an event; unset fields are left unchanged |
delete_event | destructive, external | Delete an event |
respond_to_event | write, external | Accept, tentatively accept, or decline an invitation |
Chat
| Tool | Tags | Description |
|---|---|---|
search_conversations | read-only | Find conversations by participants or display name; lists all memberships when no filters given |
list_messages | read-only | List messages in a space, DM, or group DM, optionally scoped to a thread or time range |
search_messages | read-only | Search messages by keyword and filters across all accessible spaces, or within one conversation |
send_message | write, external | Send a Markdown-formatted message, optionally into an existing thread |
People
| Tool | Tags | Description |
|---|---|---|
search_directory_people | read-only | Search the organization's Workspace directory for people |
search_contacts | read-only | Search the user's personal contacts |
get_user_profile | read-only | Get the signed-in user's own profile (name and email) |
Sheets
| Tool | Tags | Description |
|---|---|---|
get_spreadsheet | read-only | Get a spreadsheet's structure and content, with optional grid data |
get_values | read-only | Read a range of values from a spreadsheet |
update_values | write | Write values to a range of a spreadsheet |
update_formulas | write | Set formulas in a range of a spreadsheet |
insert_dimension | write | Insert rows or columns into a sheet at a given index |
update_spreadsheet | destructive | Apply spreadsheets.batchUpdate requests: formatting, pivot tables, charts, merges, conditional formatting, and sheet management |
Docs
| Tool | Tags | Description |
|---|---|---|
read_doc | read-only | Read a JSON representation of a document (text plus structure); the document ID is the Drive file ID |
update_doc | destructive | Apply documents.batchUpdate requests: insert, replace, and delete text, styling, tables, and images |
Slides
| Tool | Tags | Description |
|---|---|---|
read_presentation | read-only | Read a presentation's structure and slides |
read_slide_page | read-only | Read a single slide of a presentation |
read_slide_page_thumbnail | read-only | Get a thumbnail image of a single slide |
update_presentation | destructive | Apply presentations.batchUpdate requests: create slides, insert and style text and shapes, and edit layout |
None of the editor servers creates files.
Create new Docs, Sheets, and Slides with Drive's create_file, then edit them by ID with the tools above.
Required scopes
Add all 31 to the OAuth consent screen under Data Access, in Publish the scopes.
This is the same list the gateway sends in the authorize request.
All except the three identity scopes take the https://www.googleapis.com/auth/ prefix.
- Identity –
openid,email,profile - Gmail –
gmail.modify,gmail.readonly,gmail.compose,gmail.labels - Drive –
drive,drive.readonly,drive.file - Calendar –
calendar,calendar.readonly,calendar.events,calendar.events.readonly,calendar.events.freebusy,calendar.freebusy,calendar.calendarlist,calendar.calendarlist.readonly - Chat –
chat.spaces.readonly,chat.messages.readonly,chat.messages.create,chat.memberships.readonly,chat.users.readstate.readonly - People –
contacts.readonly,contacts.other.readonly,directory.readonly,userinfo.profile,userinfo.email - Editors –
spreadsheets,documents,presentations
The set is deliberately narrower than what Google offers.
It excludes https://mail.google.com/ (permanent deletion), the Gmail settings scopes (mail forwarding and delegation), gmail.send, the Chat space and membership write scopes, and contact write access, none of which any shipped tool needs.
It also excludes gmail.metadata:
a token carrying that scope is forced into metadata-only mode by the Gmail API even when fuller read scopes are granted, which breaks message search and message bodies.
Scopes are requested at connect time, so a user's consent screen lists exactly the access above. Narrowing further is possible by removing tools, but a scope removed while its tool ships means that tool fails at call time.
Reference values
The values this integration uses, for quick lookup. The catalog fills in the endpoints and OAuth URLs, so you don't enter them.
| Product | Upstream ID | Product API | MCP endpoint |
|---|---|---|---|
| Gmail | gmail | gmail.googleapis.com | https://gmailmcp.googleapis.com/mcp/v1 |
| Drive | drive | drive.googleapis.com | https://drivemcp.googleapis.com/mcp/v1 |
| Calendar | calendar | calendar-json.googleapis.com | https://calendarmcp.googleapis.com/mcp/v1 |
| Chat | chat | chat.googleapis.com | https://chatmcp.googleapis.com/mcp/v1 |
| People | people | people.googleapis.com | https://people.googleapis.com/mcp/v1 |
| Sheets | sheets | sheets.googleapis.com | https://sheetsmcp.googleapis.com/mcp/v1 |
| Docs | docs | docs.googleapis.com | https://docsmcp.googleapis.com/mcp/v1 |
| Slides | slides | slides.googleapis.com | https://slidesmcp.googleapis.com/mcp/v1 |
| Setting | Value |
|---|---|
| Credential mode | Bring your own app |
| OAuth client | Web application, under Google Auth Platform → Clients |
| Redirect URI | https://oauth.aisecurity.services.<region>.connect.secureauth.com/auth/callback (copy it from Agent Authority) |
| Authorize URL | https://accounts.google.com/o/oauth2/v2/auth |
| Token URL | https://oauth2.googleapis.com/token |
| Grant type | Authorization code |
| Identity scopes | openid, email, profile |
| Consent audience | Internal, for a project under your Cloud organization |
| Admin trust | Security → Access and data control → API controls → Manage App Access, set to Trusted |
| Developer Preview | developers.google.com/workspace/preview |
Policy examples
Rules are evaluated top to bottom and the first match wins. Allow rules on their own restrict nothing: your org starts with a seeded Allow all rule, so any tool your allows don't cover still falls through to it. A restrictive recipe needs a catch-all deny scoped to this resource, ordered below the allows. New rules are inserted at the top of the list, so create them in reverse order or drag them into place. See Policies.
- Read-only access.
Allow
search_*,get_*,list_*, andread_*, then deny*below them. - Block anything that leaves the org.
Deny
send_messageandcreate_draftabove any allow rules. - Block destructive operations.
Deny
delete_event,apply_sensitive_thread_label, andapply_sensitive_message_label. - Mail triage without calendar changes.
Allow
search_threads,get_thread,get_message, and*_label*, then deny*_event, then deny*. - Drive reads but no writes.
Allow
search_files,list_recent_files,get_file_*, andread_file_content, then denycreate_file,copy_file, anddownload_file_content. - Allow full access for a specific agent.
Scope an allow rule for
*to that agent on this MCP server. - Block destructive tools.
Add a deny rule with the built-in
destructivetag (Tools pill) for this resource (MCP pill).
Tool patterns are case-sensitive and match exactly unless they contain *, so the lowercase snake*case patterns above (get*_, not Get_) are what match Google Workspace tool names.
Next steps
Your agents can now reach Gmail, Drive, Calendar, Chat, People, Sheets, Docs, and Slides through one resource, with every call recorded. Next, decide which agents can only read and which can send, delete, or edit, and write that as a policy.
- Create a policy – start from the read-only pattern in Policy examples.
- Connections – manage the Google accounts your users have linked.
Appendix: all Google Workspace scopes
Google's full scope set for each product, for reference. The gateway requests only the scopes under Required scopes, so publish those. That section also explains why the rest are left out.
Gmail
https://mail.google.com/
https://www.googleapis.com/auth/gmail.modify
https://www.googleapis.com/auth/gmail.readonly
https://www.googleapis.com/auth/gmail.compose
https://www.googleapis.com/auth/gmail.drafts
https://www.googleapis.com/auth/gmail.send
https://www.googleapis.com/auth/gmail.insert
https://www.googleapis.com/auth/gmail.labels
https://www.googleapis.com/auth/gmail.metadata
https://www.googleapis.com/auth/gmail.settings.basic
https://www.googleapis.com/auth/gmail.settings.sharing
https://www.googleapis.com/auth/gmail.addons.current.action.compose
https://www.googleapis.com/auth/gmail.addons.current.message.action
https://www.googleapis.com/auth/gmail.addons.current.message.metadata
https://www.googleapis.com/auth/gmail.addons.current.message.readonlyDrive
https://www.googleapis.com/auth/drive
https://www.googleapis.com/auth/drive.readonly
https://www.googleapis.com/auth/drive.file
https://www.googleapis.com/auth/drive.metadata
https://www.googleapis.com/auth/drive.metadata.readonly
https://www.googleapis.com/auth/drive.appdata
https://www.googleapis.com/auth/drive.activity
https://www.googleapis.com/auth/drive.activity.readonly
https://www.googleapis.com/auth/drive.meet.readonly
https://www.googleapis.com/auth/drive.photos.readonly
https://www.googleapis.com/auth/drive.scripts
https://www.googleapis.com/auth/drive.apps.readonlyCalendar
https://www.googleapis.com/auth/calendar
https://www.googleapis.com/auth/calendar.readonly
https://www.googleapis.com/auth/calendar.events
https://www.googleapis.com/auth/calendar.events.readonly
https://www.googleapis.com/auth/calendar.events.freebusy
https://www.googleapis.com/auth/calendar.freebusy
https://www.googleapis.com/auth/calendar.calendarlist
https://www.googleapis.com/auth/calendar.calendarlist.readonly
https://www.googleapis.com/auth/calendar.settings.readonly
https://www.googleapis.com/auth/calendar.events.owned
https://www.googleapis.com/auth/calendar.app.createdChat
https://www.googleapis.com/auth/chat.spaces
https://www.googleapis.com/auth/chat.spaces.readonly
https://www.googleapis.com/auth/chat.messages
https://www.googleapis.com/auth/chat.messages.readonly
https://www.googleapis.com/auth/chat.messages.create
https://www.googleapis.com/auth/chat.messages.reactions
https://www.googleapis.com/auth/chat.memberships
https://www.googleapis.com/auth/chat.memberships.readonly
https://www.googleapis.com/auth/chat.users.readstate.readonlyPeople
https://www.googleapis.com/auth/contacts
https://www.googleapis.com/auth/contacts.readonly
https://www.googleapis.com/auth/contacts.other.readonly
https://www.googleapis.com/auth/directory.readonly
https://www.googleapis.com/auth/userinfo.profile
https://www.googleapis.com/auth/userinfo.emailSheets
https://www.googleapis.com/auth/spreadsheetsDocs
https://www.googleapis.com/auth/documentsSlides
https://www.googleapis.com/auth/presentations