Skip to main content

Configure Google Workspace for MintMCP Google servers

MintMCP provides hosted MCP servers for Google Docs, Sheets, Slides, Drive, and Gmail/Calendar. Before your employees can connect, a Google Workspace admin must authorize MintMCP's OAuth apps in the Admin Console. This guide covers enabling the servers in MintMCP and granting them access in Google Workspace.

Prerequisites

  • A MintMCP admin account with access to the MCP store
  • A Google Workspace super admin account

Enable the Google MCP servers in MintMCP

The Google MCP servers are available as recommended servers in the MintMCP registry.

  1. In MintMCP, go to MCP store > Manage store.
  2. Find the Google MCP servers in the Recommended section.
  3. Click Install for each Google server you want to make available to your team.

Authorize MintMCP apps in Google Admin Console

Each Google MCP server uses a separate OAuth app. Add each client ID as an authorized app in the Google Admin Console so employees can grant access when they connect.

  1. Go to admin.google.com and sign in as a super admin.
  2. Navigate to Security > Access and data control > API controls.
  3. In the App access control card, click Manage Third-Party App Access.
  4. Click Add app > OAuth App Name Or Client ID.
  5. Enter a client ID from the table below and click Search.
ServerClient ID
Google Docs496336791713-crgjnhc1sva1pih8bsk91shu0n0ga7mc.apps.googleusercontent.com
Google Sheets496336791713-npvu2i05k4b0n7qafgkthghoftoe9rf7.apps.googleusercontent.com
Google Slides496336791713-752djahev4f6tnh7l1qs1aa2qptbdi9d.apps.googleusercontent.com
Google Drive496336791713-r8qkcs2ctoqjcngjua9d8p3mo6561g04.apps.googleusercontent.com
Gmail / Calendar496336791713-653ukqc3ais9r58jntnvr1rcfl7plc2r.apps.googleusercontent.com
  1. Select the app from the search results and click Select.
  2. Choose the organizational units to apply this policy to (typically All Users) and click Continue.
  3. Set the access level to Trusted (app can request access to all Google data).
  4. Click Configure.

Repeat steps 4–9 for each server in the table.

Restrict to specific scopes (optional)

If your organization's security policy requires scope-level control rather than full Trusted access, select Specific Google data in step 8 instead of Trusted, then click Update Google services or scopes to add only the scopes listed below for each server.

Base scopes (required for all servers)

Every Google MCP server requests these scopes for authentication:

ScopeAccess granted
openidOpenID Connect authentication
https://www.googleapis.com/auth/userinfo.emailView user email address
https://www.googleapis.com/auth/userinfo.profileView basic profile info

Per-server scopes

Add these scopes in addition to the base scopes above.

ScopeAccess granted
https://www.googleapis.com/auth/drive.readonlySearch docs, read content, get sharing info
https://www.googleapis.com/auth/drive.fileView and manage Drive files created or opened with this app
https://www.googleapis.com/auth/documentsCreate docs, append/insert/replace/delete text, format text and paragraphs, insert tables

Security considerations

  • Each employee authenticates individually with their own Google account, so tool calls are limited by their personal Google permissions.
  • Trusted access allows the MintMCP app to request any scope users consent to. Use Specific Google data if your security policy requires explicit scope approval.
  • The Gmail and Drive scopes are restricted services in Google Workspace, so an app set to Limited can't reach them — use Trusted or Specific Google data for those servers.
  • MintMCP authenticates users through per-user OAuth — no shared service account credentials are stored.

Troubleshooting

  • Users still get access denied after you authorize the app. App access changes can take time to propagate across your organization, so have the user retry after a short wait.
  • The app doesn't appear when you search by client ID. Confirm the client ID is copied exactly from the table above, including the .apps.googleusercontent.com suffix.
  • A user is blocked from Gmail or Drive even though the app is authorized. If you used the optional scope-restricted path, restricted services need the app set to Trusted or the specific scopes added under Specific Google dataLimited can't reach them.

Next steps