> For the complete documentation index, see [llms.txt](https://docs.aisuru.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisuru.com/en/advanced-features/integrations/mcp/aisuru-mcp-which-ones-and-how-to-activate/22.-google-workspace-mcp-server.md).

# 22. Google Workspace MCP Server

By connecting Google Workspace to your agent you connect Docs, Sheets, Slides, Drive, Calendar and Gmail, always on behalf of the user who signs in with Google.

## What it can do

* Create and organise files on Google Drive
* Read and edit Docs, Sheets and Slides
* Create and view Google Calendar events
* Send emails with Gmail

## Examples

*"Create a Doc with today's meeting minutes and share it with the team."*\
\
*"Append a row with this new contact to the "Leads" Sheet."*\
\
*"Schedule a call with the client on Friday at 11."*

## How access works

Each user connects their own Google account with a secure sign-in right in the chat: the agent shows a "Sign in with Google" button, the user grants the permissions, and from then on the agent works only on that account's data.

## Configuration parameters

| Parameter                        | Required | Description                                                                                                                                                                                                                                  |
| -------------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `GOOGLE CLIENT ID`               | No       | OAuth Client ID of your own GCP app (if you want to use your own branded app). If left empty, AIsuru uses Memori's shared Google app.                                                                                                        |
| `GOOGLE CLIENT SECRET`           | No       | OAuth Client Secret of your GCP app. Required only if you set `GOOGLE_CLIENT_ID`.                                                                                                                                                            |
| `IDENTITY STRICT`                | No       | `true`/`false`. Default: `true`. Verifies the identity of the user in chat before every action.                                                                                                                                              |
| `IDENTITY STRICT GOOGLE ACCOUNT` | No       | `true`/`false`. Default: `true`. The connected Google account must match the AIsuru user's email in chat (IDENTITY STRICT must be true). If true, actions will be performed only when AIsuru account email matches the Google account email. |

### Custom parameters

No additional parameters needed.

{% hint style="warning" %}
Some features (structured editing of Docs/Sheets/Slides, sending Gmail) require "sensitive" scopes that Google approves after a review of your application. Until verification is complete those actions may be unavailable.
{% endhint %}

### Configuration parameters: your own Google Cloud app

1. Open **Google Cloud Console** and create (or pick) a project
2. Enable the needed APIs: Google Drive, Docs, Sheets, Slides, Calendar, Gmail
3. Configure the **OAuth consent screen** (app name, logo, domains, privacy policy link)
4. Create **OAuth client ID** credentials of type "Web application" with redirect URI `https://mcp.aisuru.ai/oauth/google/callback`
5. Copy the **Client ID** and **Client secret**

{% hint style="info" %}
**Note:** for normal use you don't need to create anything: the in-chat Google sign-in is enough. This setup is only for companies that want to use their **own branded Google Cloud app**.
{% endhint %}