Connect Google to V7 Go

🚧

Preview

This feature is new and evolving. Details on this page may change as we
improve it.

V7 Go connects to Google through a separate MCP server per app. Each app
is its own connector:

• Gmail
• Google Calendar
• Google Drive
• Google Docs
• Google Sheets
• Google Slides
• Google Chat
• Google Contacts

All of them authenticate through one Google Cloud OAuth client. You set
that client up once, then reuse the same Client ID and Client Secret for
every Google connector.

Personal (gmail.com) and Google Workspace accounts both work. You do not
need a Workspace subscription. The Google Cloud project is free.

If the page shows Connect

In some regions V7 already provides the OAuth client. Press Connect and
approve Google's consent screen. Skip the Google Cloud steps below unless
you choose Use your own OAuth client instead.

If the page shows a setup card

1. In Go, open Integrations → MCP Connectors and choose the Google app
   — or ask the agent in chat to use it. A connect card appears.
2. In the Google Cloud console,
   create a project or choose an existing one.
3. Enable that app's API and its MCP API. The card links the exact console
   pages (for example Gmail API and Gmail MCP API).
4. In Google Auth Platform,
   configure the OAuth consent screen and add the scopes the card lists.
5. In Clients, create an
   OAuth client of type Web application. Add the callback URI from the
   card as an authorized redirect URI.
6. Copy the Client ID and Client Secret into the card. Never paste them
   into chat. The same client works for every Google connector.
7. Press Connect and complete Google's consent screen.

When you connect a second Google app, reuse the same Client ID and Client
Secret. Still enable that app's MCP API in the same project, and add its
scopes to the consent screen if the consent screen is in production mode.

Troubleshooting

• access_denied / app not verified. The consent screen is in Testing
  and the signing-in account is not a test user. Add the account under
  Audience → Test users, or publish the app.
• redirect_uri_mismatch. The callback URI on the card is missing from
  the OAuth client's authorized redirect URIs.
• accessNotConfigured / 403 after connecting. The app's MCP API (for
  example gmailmcp.googleapis.com) is not enabled in the project that
  owns the OAuth client.
• Connected, but tools fail with insufficient scopes. Add the scopes
  from the card to the consent screen and reconnect.

Google's MCP servers are in developer preview. Retry a provider-side error
before deeper diagnosis.

For messages Go shows on the connect card, see
MCP connector errors.

FAQ

Is the connection shared? Each Google app is its own connector.
Connections follow the sharing policy on that connector page.

What can the agent do? Whatever you granted for that app — for example
read and draft Gmail, read Calendar, or search Drive. Ask "what Gmail tools
do you have?" for the live list.