Skip to content
Status

Google Docs

Read and update Google Docs through Google's hosted Docs MCP server.

Sign in to the Google Cloud console with an account that can select a Google Cloud project, enable APIs, configure the Google Auth platform, and create OAuth credentials. Google does not document a Google Docs MCP-specific paid plan or license requirement. Enabling APIs requires serviceusage.services.enable, normally through Service Usage Admin or Owner. Obtain the approved support and contact addresses before you begin. If your organization restricts high-risk Drive & Docs scopes or unconfigured apps, you also need a Google Workspace administrator with the Service Settings administrator privilege.

Enable the Docs MCP APIs

  1. In the toolbar, open the resource selector.
  2. Select the Google Cloud project that will own the credentials.
  3. Open APIs & Services > API Library.
  4. In Search for APIs & Services, enter Google Docs API.
  5. Open Google Docs API.
  6. Click Enable.
  7. Return to API Library.
  8. In Search for APIs & Services, enter Google Docs MCP API.
  9. Open Google Docs MCP API.
  10. Click Enable.

If Enable is unavailable, ask the project owner for serviceusage.services.enable.

Open Google Auth platform > Branding.

Google says an OAuth consent screen cannot be removed after it is configured. Confirm the approved app name, support address, contact address, and audience before you click Get Started.

If the page says Google Auth Platform not configured yet:

  1. Click Get Started.
  2. Under App Information, enter Docs MCP Server in App name.
  3. Choose the approved User support email.
  4. Click Next.
  5. Under Audience, select Internal when every connecting user belongs to the Google Cloud project’s Google Workspace organization; otherwise select External.
  6. Click Next.
  7. Under Contact Information, enter the approved monitored address in Email address.
  8. Click Next.
  9. Under Finish, review the Google API Services User Data Policy.
  10. With organizational approval, select I agree to the Google API Services: User Data Policy.
  11. Click Continue.
  12. Click Create.

If the Google Auth platform is already configured, review the equivalent settings on Branding, Audience, and Data Access.

Add the required access:

  1. Open Data Access.
  2. Click Add or Remove Scopes.
  3. Under Manually add scopes, paste these four values:
    • https://www.googleapis.com/auth/drive.readonly
    • https://www.googleapis.com/auth/drive.file
    • https://www.googleapis.com/auth/documents.readonly
    • https://www.googleapis.com/auth/documents
  4. Click Add to Table.
  5. Click Update.
  6. Click Save.

If Audience is External and the app is in Testing, add every account that will make the first connection:

  1. Open Audience.
  2. Under Test users, click Add users.
  3. Enter the connecting accounts.
  4. Click Save.

Testing supports at most 100 test users, and each authorization expires after seven days.

Create the OAuth client

  1. Open Google Auth platform > Clients.
  2. Click Create client.
  3. Set Application type to 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 https://app.getgram.ai/mcp/remote_login_callback.

Do not add an Authorized JavaScript origins value.

Prepare secure password storage before the next action. Google says the client secret in the next dialog can be copied only once.

  1. Click Create.

Keep OAuth 2.0 client created open.

Copy the client credentials

  1. In OAuth 2.0 client created, copy Client ID to secure storage.
  2. Under Client secrets, copy Client secret.
  3. Store the secret as a password alongside the Client ID.

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

If your organization restricts high-risk Drive & Docs scopes or blocks unconfigured apps, continue to Allow the OAuth client in restricted organizations. Otherwise, continue to Speakeasy setup.

Allow the OAuth client in restricted organizations

Complete this step only when your organization’s Workspace API controls restrict high-risk Drive & Docs scopes or block unconfigured apps.

  1. Sign in to the Google Admin console with Service Settings administrator access.
  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 copied in Copy the client 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
    • Specific Google data, with the four Docs MCP scopes and any required Google sign-in scopes
  11. Click Continue.
  12. Review the settings.
  13. Click Finish.

Changes can take up to 24 hours, though they usually apply sooner. Continue to Speakeasy setup.

Add the server in Speakeasy

  1. In the Speakeasy AI Control Plane sidebar, under Connect, select Sources.
  2. Click Add Source.
  3. Choose Custom remote server.
  4. On Add a custom remote MCP server, paste https://docsmcp.googleapis.com/mcp/v1 into Remote MCP server URL.
  5. Click Add server.

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

Connect your credentials

  1. From Overview, open Settings.
  2. Under Authentication, click Configure Manually, or click Use Discovered when offered.
  3. In Attach Remote Identity Provider, set Client Type to Manual.
  4. Confirm that Redirect URI matches https://app.getgram.ai/mcp/remote_login_callback, which you entered when you created the OAuth client.
  5. In Client ID, paste the value you copied from Google.
  6. In Client Secret (optional), paste the secret you copied from Google. Google requires this value.
  7. In Scope (override), enter https://www.googleapis.com/auth/drive.readonly, https://www.googleapis.com/auth/drive.file, https://www.googleapis.com/auth/documents.readonly, https://www.googleapis.com/auth/documents.
  8. Click Attach Identity Provider.

Complete Google’s browser authorization with the intended Google Account. If the app is External and in Testing, that account must be under Test users.

This guide covers setup only. For anything beyond it — billing, tool behavior, limits — see Google’s Docs MCP documentation at https://developers.google.com/workspace/docs/api/guides/configure-mcp-server.