Skip to main content
Google Workspace connections are an ApexGenius private preview built on Google’s official hosted MCP servers where available and official Google REST APIs elsewhere. Each product is a separate connection so you can grant only the scopes and account access needed for that product.
Google Developer Preview.Google Workspace MCP servers are currently part of the Google Workspace Developer Preview Program. ApexGenius keeps these providers unavailable until the Cloud project is enrolled, both the base API and MCP service are enabled, OAuth is configured, and a live connection test passes.

​
Supported connections

Tasks, Forms, and Meet use their official Google REST APIs because Google does not currently publish hosted MCP servers for those products. The gateway reads each server’s live operation catalog. Use apex_search_tools to find the exact Google operation, then run it through the matching read or write call tool. This keeps the public ApexGenius surface at three tools without freezing Google’s Developer Preview catalog into ApexGenius code.

​
Connect a product

  1. In ApexGenius, open Connections.
  2. Select the Google Workspace product you want.
  3. Choose Connect and authorize the requested Google scopes.
  4. Return to the connection details and refresh resources.
  5. Confirm the connected Google account and leave the resource enabled.
  6. Run a read-only smoke test before using any write-capable tool.
Repeat the flow only for the products you need. A Gmail connection does not grant Drive, Sheets, Calendar, Tasks, Forms, or Meet access.

​
Google Cloud setup

The developer app must enable both layers for each selected product:
  • Base APIs: Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat, and People.
  • MCP services: Gmail MCP, Drive MCP, Docs MCP, Sheets MCP, Slides MCP, Calendar MCP, Chat MCP, and People MCP.
  • Direct APIs when selected: Google Tasks API, Google Forms API, and Google Meet REST API.
Google Chat also requires a Chat app configuration. External OAuth apps must add test users while the consent screen remains in Testing.

​
Review and security

Gmail, Drive, Forms, and some Meet scopes can be sensitive or restricted. Public production access can require Google verification, and storing or transmitting restricted-scope data can require an annual security assessment. Meet access must also fit Google’s approved use cases. Provider approval is separate from ApexGenius deployment. Google warns that content read through an MCP server can contain indirect prompt injection. ApexGenius therefore treats remote content as untrusted, review-gates the generic call tool, and records write attempts without putting credentials into audit payloads.

​
Official Google documentation

Google documentation is authoritative for Developer Preview eligibility, OAuth scopes, supported tools, approved use cases, API behavior, and verification requirements.
Last modified on August 28, 2026