Connect Google Docs

The Google Docs (MCP) connector lets skills read and edit Google Docs with search/replace, comments, and anchored inserts. Harriet runs the google-docs-mcp server in its sandbox, and edits target text anchors instead of raw character indices.

What you need

A Desktop app OAuth client from Google Cloud Console. You need its client ID and client secret.
A Harriet role that can manage provisioning; the Add connector button is disabled otherwise. See roles and permissions.
The server itself is open source at github.com/dbuxton/google-docs-mcp.

Install the connector

Open Connectors. Then select Add connector to open the catalog.
Pick Google Docs (MCP). The card carries a Sandboxed badge: Harriet runs the server with uvx straight from its GitHub repository inside an isolated sandbox; see hosted and sandboxed connectors. The wizard shows the notice "Users connect their accounts under Profile → Integrations after this skill is assigned."
Enter your OAuth client. Fill in Google OAuth client ID (a Desktop app OAuth client from Google Cloud Console) and Google OAuth client secret from the same client.
Select Install Google Docs (MCP). Harriet creates the connector and syncs the server's tools.
Create a skill, or skip. Pick a published use case or choose Skip — connector only and attach the connector from skill authoring later.

Per the catalog entry, optional Apps Script environment variables can be set later on the integration in Integration settings.

Authorize

Each person authorizes individually against Google: they connect under Profile → Integrations, and Harriet passes their token into the sandbox so edits happen as them. See per-user OAuth connections. The connection requests these Google scopes: documents, drive, drive.readonly, drive.file, script.projects, script.deployments, script.processes, plus openid email profile.

⚠️

The consent screen shows the full scope list above, including Docs, Drive, and Apps Script access. Make sure your OAuth client's consent screen is configured for those scopes before rolling out, or people's connection attempts will not go through cleanly.

Tools you get

This connector is about editing documents, not browsing storage. Per the catalog entry and the server it wraps, skills can:

Read a document before changing it (the starter skill tells the model to prefer docs_get before structural edits)
Find and replace text
Insert content before or after a text anchor
Add comments

Anchors make edits resilient: the model targets a phrase it can see rather than a character offset that shifts as the document changes. For listing and reading files across Drive, use the Google Drive connector instead.

Try it

Assign a skill that uses this connector, then ask: "In the launch plan doc, replace every mention of the old ship date with the new one and leave a comment where you changed it."