Skip to content
Status

Google Slides

Connect Google Slides data through Google's hosted Slides MCP server.

The Google Slides MCP Server is in Developer Preview. Google does not document a Google Slides MCP-specific paid plan or license requirement.

Use a Google Cloud project where you can enable services, grant project roles, configure Google Auth platform, and create OAuth credentials. Each connecting user needs access to the intended presentations. An application or security owner must also configure prompt and response screening for malicious content or prompt injection.

Sign in to the Google Cloud console. In the console toolbar, select the project that will own this configuration, and keep it selected throughout the Google Cloud steps.

Enable the Google Slides APIs

  1. Open APIs & Services > API Library.
  2. In Search for APIs & Services, search for Google Slides API.
  3. Open Google Slides API.
  4. Click Enable. If the API is already enabled, continue.
  5. Reopen APIs & Services > API Library.
  6. In Search for APIs & Services, search for Google Slides MCP API.
  7. Open Google Slides MCP API.
  8. Click Enable. If the API is already enabled, continue.

You need serviceusage.services.enable, normally through Service Usage Admin or Owner.

Grant MCP Tool User access

You need Project IAM Admin to grant project roles.

  1. Open IAM.
  2. Confirm that the same project is selected.
  3. Click Grant access.
  4. In New principals, enter a connecting user’s Google Account email.
  5. Click Select a role.
  6. Search for MCP Tool User.
  7. Select MCP Tool User.
  8. Click Save.
  9. Repeat these steps for each connecting user.

The server will apply each user’s existing Slides and Drive permissions and governance controls.

Before configuring the consent screen, obtain approved support and contact addresses. Google says an OAuth consent screen cannot be removed after it is configured.

  1. Open Google Auth platform > Branding.
  2. If the page says Google Auth Platform not configured yet, click Get Started.
  3. Under App Information, enter Slides MCP Server in App name.
  4. Choose an approved User support email.
  5. Click Next.
  6. Under Audience, select Internal when all connecting users belong to the project’s Workspace organization; otherwise select External.
  7. Click Next.
  8. Under Contact Information, enter an approved monitored Email address.
  9. Click Next.
  10. Under Finish, review the Google API Services User Data Policy.
  11. With organizational approval, select I agree to the Google API Services: User Data Policy.
  12. Click Continue.
  13. Click Create.

If Google Auth platform was already configured, retain its approved Branding and Audience.

  1. Open Data Access.

  2. Click Add or Remove Scopes.

  3. Under Manually add scopes, paste these four scope URLs:

    https://www.googleapis.com/auth/drive.readonly
    https://www.googleapis.com/auth/drive.file
    https://www.googleapis.com/auth/presentations.readonly
    https://www.googleapis.com/auth/presentations

  4. Click Add to Table.

  5. Click Update.

  6. Click Save.

For an External app in Testing:

  1. Open Audience.
  2. Under Test users, click Add users.
  3. Enter every connecting user’s email.
  4. Click Save.

An External app in Testing permits up to 100 listed test users. Each authorization expires seven days after consent; after it expires, the account remains a test user but must complete browser authorization again.

Create the OAuth client

  1. Open Google Auth platform > Clients.

  2. Click Create client.

  3. In Application type, select Web application.

  4. In Name, enter a recognizable name such as Speakeasy AI Control Plane.

  5. Under Authorized redirect URIs, click + Add URI.

  6. In URIs, enter this value:

    https://app.getgram.ai/mcp/remote_login_callback

Do not add an Authorized JavaScript origins value.

Before clicking Create, prepare an approved secret store. The next dialog permits the client secret to be copied only once.

Click Create. This opens OAuth 2.0 client created.

Copy the OAuth credentials

  1. In OAuth 2.0 client created, copy Client ID to the approved secret store.
  2. Under Client secrets, copy Client secret to the same store.

If you miss the one-time secret, delete it and create a new one before continuing.

If Workspace API controls restrict high-risk Drive and Slides scopes or block unconfigured apps, complete Allow the OAuth client in restricted organizations. Otherwise, continue to Add the server in Speakeasy.

Allow the OAuth client in restricted organizations

Use this step only when Workspace API controls restrict high-risk Drive and Slides scopes or block unconfigured apps. You need Service Settings administrator access.

  1. Sign in to the Google Admin console.
  2. Open Security > Access and data control > API controls.
  3. Click Manage App Access.
  4. Under Configured apps, click Configure new app.
  5. Enter the Client ID from Copy the OAuth credentials.
  6. Click Search.
  7. Select the matching app.
  8. Select the organizational units whose users will connect.
  9. Click Continue.
  10. Choose the access approved by the security owner: Trusted, or Specific Google data with the four Slides MCP scopes and any required Google sign-in scopes.
  11. Click Continue.
  12. Review the settings.
  13. Click Finish.

Google says changes can take up to 24 hours, though they usually apply sooner. Continue to Add the server in Speakeasy.

Add the server in Speakeasy

  1. In the Speakeasy AI Control Plane sidebar, under MCP Gateway, select MCP.

  2. Click Add new to open Add MCP server.

  3. Choose Hosted remotely.

  4. On New remote MCP server, paste this URL into MCP server URL:

    https://slidesmcp.googleapis.com/mcp/v1

  5. Click Verify connectivity, then Save.

This creates the hosted MCP server and opens its Overview page. Transport is read-only.

Connect your credentials

Open the server’s Settings (from Overview for a hosted remote server, or Configure MCP settings after a catalog addition).

Choose an authentication provider

  • If Authentication is unconfigured, choose Use Discovered when available; otherwise choose Configure Manually.
  • If authentication is configured but no provider is attached, use Connected services > Add provider.
  • If the intended provider is already attached, use its existing controls. Do not attach a duplicate; check its client against the requirements below and skip Verify and attach.

In Attach Remote Identity Provider, the provider selector defaults to Select existing when the project has issuers. Select the appropriate existing Google provider and skip new-provider setup.

New provider only

  1. Choose Add new and enter Issuer URL:

    https://accounts.google.com/

  2. Confirm the auto-derived Slug is unique in the project.

  3. Discovery runs automatically for a seeded issuer URL. After typing or changing the URL, click Discover only if offered.

  4. Review the endpoints, or enter these Google OAuth values if discovery does not populate them.

    Authorization endpoint:

    https://accounts.google.com/o/oauth2/v2/auth

    Token endpoint:

    https://oauth2.googleapis.com/token

Choose a session client

  • Reuse: Under Session Client, choose Select existing when available and select the appropriate Google OAuth client. Skip credential entry; continue to Check client requirements.
  • Create: Choose Add new when available and set Client Type to Manual. For a new provider, complete the new-client form below.

New session client only

  1. Paste the Client ID from Copy the OAuth credentials.
  2. Paste the Client Secret from Copy the OAuth credentials into Client Secret (optional). Google’s web client requires this generated secret.

Check client requirements

For both new and reused clients, verify the Google app’s approved audience and publishing status. An External app in Testing must list each connecting account under Test users. Reusing a client does not require entering its credentials again.

Confirm the selected client includes the required scopes below. For a new client, configure Scope (override); for a reused client, inspect the read-only Scope value. If it does not match, choose Add new to create a correctly scoped client; the attach sheet cannot edit a reused client.

For a new client, enter this value:

https://www.googleapis.com/auth/drive.readonly,https://www.googleapis.com/auth/drive.file,https://www.googleapis.com/auth/presentations.readonly,https://www.googleapis.com/auth/presentations

Verify and attach

  1. Confirm that the callback URL registered with the provider is https://app.getgram.ai/mcp/remote_login_callback. For a new manual client, also compare it with the sheet’s displayed Redirect URI. The existing-client selection does not display that field; check the registered callback in the provider’s app settings instead.
  2. Click Attach Identity Provider.

For the provider-side callback setting, see Create the OAuth client.

At first connection, complete Google’s browser authorization with an account granted MCP Tool User in Grant MCP Tool User access and access to the intended presentations. An External app in Testing also requires that account under Test users.

For anything beyond setup — billing, tool behavior, or limits — see Google’s Slides MCP documentation.