Set Up Google Drive and Google Docs Connectors

MCP Connectors is a Beta feature for environments with UnqorkAI. A connector sends the content it retrieves to the model the Build Agent runs on. Test each connector and verify the Build Agent's results before you rely on it.

This guide walks you through setting up the Google Drive and Google Docs MCP Connectors. With these connectors, the Build Agent can find files in Google Drive and read or edit Google Docs. Use this guide if you are the administrator who adds connectors for your environment.

Most of the setup happens in Google . You create a sign-in client there, then give its details to Unqork. Plan for a wait in the middle, because Google must approve your project for its preview program.

Before You Begin

You need the following:

• Access to the Google Cloud console with permission to create a project, turn on APIs, and create an OAuth client. OAuth is the standard sign-in method these connectors use.
• A Creator role in Unqork that has the Create permission for Services. You need this permission to add a connector.
• The list of Creators who will use the connectors, if they are not all in your Google Workspace organization.

You can use one Google Cloud project and one OAuth client for both Google Drive and Google Docs. The project must join Google's preview program only once.

Step 1: Create a Google Cloud Project

A Google Cloud project holds the settings for your connectors.

1. In the Google Cloud console, create a project. Give it a name that is easy to recognize, like Unqork Build Agent.
2. Open the project's Dashboard. Under Project info, copy the Project number. You need it in the next step.

Step 2: Join the Google Workspace Developer Preview

The Google Drive and Google Docs MCP servers are only available to projects in Google's preview program.

1. Go to the Google Workspace Developer Preview Program page.
2. Apply with the Project number value you copied in step 1.
3. Wait for Google to confirm that your project is in the program. Do not continue until you receive the confirmation.

Step 3: Turn On the APIs

Each connector needs two APIs: the product's main API and its MCP API. In the Google Cloud console, go to APIs & Services > Library. Search for each API and select Enable.

Turn on both APIs for each connector. If only the MCP API is on, every request to a Google Doc fails with Permission denied.

Step 4: Set Up the Consent Screen

The consent screen is the page Creators see when they sign in with Google. It tells them which app is asking for access.

1. In the Google Cloud console, go to Google Auth Platform > Branding. Select Get Started.
2. In App name, enter the name Creators should see when they sign in. Select a User support email.
3. Under Audience, select one of the following options:
   • Select Internal if every Creator is in your Google Workspace organization.
   • Select External if some Creators are outside your organization. Then go to Audience > Test users, select Add users, and add each Creator's email address.
4. Enter a contact email address. Accept the Google API Services: User Data Policy, then select Create.

You do not need to add anything under Data Access. Unqork asks Google for the access it needs when each Creator connects.

Step 5: Create the OAuth Client

The OAuth client is what Unqork uses to sign Creators in to Google. Before you begin this step, find your redirect URI in Unqork. A redirect URI is the web address where Google sends a Creator after they sign in to Google.

To find the redirect URI:

1. In Unqork, navigate to Administration > Environment Settings > Build Agent > MCP Connectors.
2. Select Add Connector, then select Add Connector on the Google Drive card.
3. In the Authorization section, copy the redirect URI. Keep the dialog open, or select Cancel and come back to it in step 6.

The redirect URI follows this pattern, with your environment's address in place of {designer-domain}:

https://{designer-domain}/fbu/uapi/quill/mcp-connectors/oauth/callback

To create the OAuth client:

1. In the Google Cloud console, go to Google Auth Platform > Clients. Select Create Client.
2. For Application type, select Web application. Enter a Name for the client.
3. Under Authorized redirect URIs, select + Add URI. Paste the redirect URI you copied from Unqork.
4. Select Use this client for an AI-powered agent.
5. Select Create.
6. Copy the Client ID and the Client secret.

The client secret works like a password. Paste it only into the Unqork Authorization fields. Do not save it in a file, a ticket, a chat message, or a screenshot.

Step 6: Add the Connector in Unqork

Repeat these steps for each connector you want: once for Google Drive and once for Google Docs. You can use the same OAuth client for both.

1. Navigate to Administration > Environment Settings > Build Agent > MCP Connectors.
2. Select Add Connector. On the Google Drive or Google Docs card, select Add Connector.
3. Enter a Name, Title, and Description.
4. In the Authorization section, check that the redirect URI matches the one you added in Google Cloud.
5. Paste the OAuth client ID and the OAuth client secret.
6. Under Share To, choose Environment or Workspaces.
7. Select Create Connector.
8. In Step 3 of 3: Select Tools, select Connect and sign in with your Google account. Signing in loads the tool list.
9. Keep the default tools, or change them. Then select Save Tools.

Until you save an OAuth client, Creators cannot connect to a Google connector. For what each tool setting means, see Choose Tools.

Step 7: Connect and Test as a Creator

Each Creator connects their own Google account. The Build Agent can only reach the files and Docs that Creator can open in Google.

1. In the Build Agent chat, select (Add files or connectors), then select Manage Connectors.
2. On the Google Drive or Google Docs row, select Connect. Sign in with Google.
3. Send a test request to the Build Agent. Requests to try include:
   • For Google Drive, try "List my five most recent Drive files."
   • For Google Docs, paste a link to a Doc and ask for a summary.

Creating, copying, or editing a file or Doc always asks the Creator first. See Connect to Outside Systems for the full Creator steps.

Troubleshooting

Google Docs Requests Fail With Permission Denied

The Google Docs API is probably off. Turn on both docs.googleapis.com and docsmcp.googleapis.com for the project. See Step 3: Turn On the APIs.

Google Rejects the Sign-In

Check the OAuth client in Google Cloud. The redirect URI must match the one in the Unqork Authorization section exactly. The Use this client for an AI-powered agent option must be selected.

A Creator Cannot Sign In

If the consent screen's audience is External, add the Creator's email address under Audience > Test users.