## Google Slides integration

Google Slides is Google's online presentation editor for consumer and Google Workspace accounts.

Agen.co connects through Google's own hosted Slides MCP server as an **Official** connector, so your AI agents use the same presentation read and update tools Google exposes to MCP clients. Google Slides has no In-house connector, so this is the only way to connect it.

Prerequisites
- Membership in the [Google Workspace Developer Preview Program](https://developers.google.com/workspace/preview). The Google Slides MCP server is a Developer Preview feature. You apply with your Google Workspace account and the Google Cloud project you use for this connector, and Google registers that project, usually within a couple of days, so apply before you start.
- A Google Cloud project where you can enable APIs, configure the Google Auth Platform, and create OAuth clients.


### Connect to Google Slides

#### Enable the APIs

In [Google Cloud Console](https://console.cloud.google.com/apis/library), select your project and enable both the **Google Slides API** and the **Google Slides MCP API**. Google requires both for the MCP server.

#### Set up the OAuth consent screen

1. Go to **Google Auth Platform** → **Branding**. If you see **Google Auth Platform not configured yet**, click **Get Started**, enter an app name and a support email, and click **Next**.
2. Under **Audience**, select **Internal**. If you can't select it, select **External**. Finish the wizard and click **Create**.
3. If you selected **External**, open **Audience** and, under **Test users**, click **Add users** and add every Google account that will connect. Other accounts can't complete sign-in while the app is in testing.
4. Open **Data Access** → **Add or Remove Scopes**. Under **Manually add scopes**, paste the four scopes below, click **Add to Table**, click **Update**, then click **Save**. If the project already has Google Docs or Google Sheets set up, the Drive scopes are already in the table, and adding them again is harmless.


| Scope | What it allows |
|  --- | --- |
| `https://www.googleapis.com/auth/presentations.readonly` | Read the user's presentations |
| `https://www.googleapis.com/auth/presentations` | Edit the user's presentations |
| `https://www.googleapis.com/auth/drive.readonly` | Read the user's Google Drive files |
| `https://www.googleapis.com/auth/drive.file` | Access Drive files the user opens or creates with the app |


#### Copy the callback URLs from Agen.co

1. In the Agen.co portal, go to **Connectors** → **My connectors** and click **Add connector**.
2. Search for `Google Slides` and select it. The **Add Google Slides** panel opens.
3. Copy both read-only URLs at the bottom of the panel:
  - **Callback URL**: completes the initial OAuth handshake between Agen.co and your OAuth client.
  - **Gateway callback URL**: used by the Agen.co MCP gateway for per-user authorization at runtime.


Leave this panel open. You return to it after creating the OAuth client. See [How to get your Redirect URL](/agen-for-work/connectors/redirect-url) for what these URLs are.

#### Create the OAuth client

1. In Google Cloud Console, make sure the same project is selected, then go to **Google Auth Platform** → **Clients** → **Create client**. The client must belong to the project where you enabled the **Google Slides MCP API**: Google checks API enablement against the project that owns the credential, so a client from another project fails without a clear error.
2. Set **Application type** to **Web application** and enter a name (for example, `Agen.co Google Slides MCP`). Leave **Use this client for an AI-powered agent** cleared.
3. Under **Authorized redirect URIs**, click **Add URI** and add **both** URLs you copied from Agen.co.
4. Click **Create**, then copy the **Client ID** and **Client Secret**. Google shows the secret only at creation, so copy it now. If you lose it, add a new secret from the client's detail page.


#### Connect Google Slides in Agen.co

1. Return to the **Add Google Slides** panel you left open and fill in the fields:


| Field | Required | Description |
|  --- | --- | --- |
| **Instance Slug** | Yes | Namespaces this instance. It prefixes each imported tool as `slug__tool`, so a second instance of the same connector needs its own slug. Use lowercase kebab-case, for example `google-slides`. You can change it later from the connector's settings. |
| **Client ID** | Yes | The Client ID of the OAuth client you created. |
| **Client Secret** | Yes | The Client Secret of the OAuth client you created. |


1. Click **Connect**. You're redirected to Google to sign in and approve access.
2. Back in Agen.co, the panel shows **Select the tools to import from Google Slides.** with a toggle for each tool, all on by default. Turn off any tool you don't want, then click **Add**. The connector is created and its tools imported only when you click **Add**, even if the Google sign-in page reported success.
3. After you create a [policy](/agen-for-work/policies/overview) for the tools, the first tool call a user makes returns a one-time authorization link instead of data. The user opens it and approves access with their own Google account. This per-user step uses the **Gateway callback URL** you registered, and each user does it once.


### Capabilities

Once connected, Google Slides appears under **My connectors** with four tools:

| Area | What it covers |
|  --- | --- |
| **Reading** | Reading a whole presentation, reading a single slide, and optionally including comments |
| **Thumbnails** | Getting a thumbnail image URL, with its width and height, for a single slide |
| **Updating** | Applying a batch of changes to a presentation, such as adding slides, inserting or replacing text, adding shapes, tables, and images, and managing comments |


### Provider limitations

- **Only existing presentations.** The server can't create a presentation file or search for one. Agents need the presentation's ID, which is the part of its URL between `/d/` and `/edit`. Slides within a presentation can be added through an update.
- **Changes are sent as a batch.** The update tool takes a list of Google Slides batch requests, so an agent needs to build requests in Google's format rather than describe the change in words.


Every tool call fails with a Developer Preview error
If every tool call fails with `Access to this tool requires that your Google Cloud project (<project number>) is enrolled in the Google Workspace Developer Preview Program`, the Google Cloud project that owns your OAuth client isn't registered in the Google Workspace Developer Preview Program. Without registration, sign-in, tool import, policy creation, and per-user authorization all still succeed, and then every tool call fails. Google registers the project you applied with, so make sure your OAuth client belongs to that project. See **Prerequisites** above.

Enabling the Google Slides connector isn't enough on its own. Tool calls remain denied until you create a [policy](/agen-for-work/policies/overview) that grants access to the specific tools you want to expose.

### Additional resources

- [Google Slides MCP server setup](https://developers.google.com/workspace/slides/api/guides/configure-mcp-server)
- [Google Slides API documentation](https://developers.google.com/workspace/slides/api/reference/rest)
- [Google Cloud Console](https://console.cloud.google.com/)
- [Setting up OAuth 2.0](https://developers.google.com/identity/protocols/oauth2/)
- [How to get your Redirect URL](/agen-for-work/connectors/redirect-url)