How to Connect Google Docs to Claude?

Before you start

You need a SourcetoMCP account with a brand created, a Claude account, and a Google account with edit rights on the documents in question. View-only access is enough to read a document but every formatting and template operation will fail against it, which is a confusing way to find out.

Connect Google Docs to SourcetoMCP

1. 1From your dashboard, go to Connectors → Add a connection.
2. 2Find the Google Docs card and select Connect.
3. 3Sign in with the Google account that can open the documents you want. SourcetoMCP asks for Google's drive.file permission, which covers individual files you choose and nothing else in your Drive.
4. 4Select + Choose documents from Google Drive. Tick every document you expect to work with in one pass, since each visit to the picker grants only what you select during it.
5. 5Pick one or more documents and confirm. Each becomes its own entry on your Connections page.

Add more at any point by repeating the flow. Access is per file and it is not inherited, so a document in the same folder stays out of reach until you pick it too.

Add SourcetoMCP as a connector in Claude

Claude adds every custom connector the same way, under Customize then Connectors. These steps are that flow pointed at SourcetoMCP.

1. 1In SourcetoMCP, open Connect an agent from the dashboard sidebar and copy your server address (it looks like https://sourcetomcp.com/api/mcp).
2. 2In Claude, open Customize, then Connectors.
3. 3Select +, then Add custom connector.
4. 4Paste in your server address. You can leave Advanced settings alone, because SourcetoMCP runs its own OAuth and never needs a client ID or secret from you.
5. 5Click Add.
6. 6The first time Claude uses it, you'll be asked to sign in to SourcetoMCP and approve access, the same OAuth approval you'd see connecting any other app. After that it reconnects on its own.

On a Team or Enterprise plan, only an Owner can add a connector, from Organization settings, then Connectors. Everyone else then opens Customize → Connectors and clicks Connect to sign in with their own SourcetoMCP account, so each person only ever reaches the sources their own account can see.

Ask Claude about your documents

Adding the connector makes it available, and you still switch it on per conversation. In a chat, select the + button, choose Connectors, and toggle SourcetoMCP on.

Claude reads the document's real structure, headings, paragraphs, tables and named ranges, rather than a flattened copy of the text. That is what lets it edit a specific part instead of rewriting the whole file. Try something like:

1. 1Summarise the decisions section of this document.
2. 2Add a row to the pricing table for the enterprise tier.
3. 3Put the client name in the header and today's date in the footer.
4. 4Turn the third paragraph into a bulleted list.
5. 5Set the page margins to 2cm all round.

What Claude actually reads

A document comes back as its structure rather than as plain text: paragraphs with their styles, headings, tables with each row's start position, headers, footers and any named ranges. That is why Claude can restyle one paragraph or add a row to the third table without rewriting the file. It also explains the main failure mode, which is asking for several positional edits at once. Each insertion moves everything after it, so the positions from the first read go stale. Ask for one change, then let it re-read.

Filling a template

The most useful pattern here is a document you already designed, with named ranges marking the parts that change. Claude replaces the content of a named range without touching the formatting around it, so a contract or a report template keeps its styling while the details get swapped. Ask it to create the named ranges once, then reuse them on every run.

A note on write actions

Docs leans heavily towards writing: 23 of its 27 operations change the document. Claude can delete a content range, drop a table row, or replace an image, and those edits land in the Google file rather than in a SourcetoMCP staging copy, so there is no undo on our side. Google's version history under File then Version history is the way back. One thing it cannot do is target a specific tab in a multi-tab document, so keep template work in single-tab files for now.

Troubleshooting

The document isn't in the picker: the picker only lists files the signed-in Google account can already open. Share the document with that account in Google Drive first, then reopen the picker.

A table edit hit the wrong row: rows are addressed by their start position in the document, not by what the first cell says. Ask Claude to read the table back before it changes a specific row.

There is no Connectors option under Customize: on Team and Enterprise plans an Owner adds connectors for the whole organisation. Ask an Owner to add it from Organization settings → Connectors, and it will then show up for you to connect.

Claude won't let you add another connector: Free accounts can keep one custom connector at a time. Remove the one you have, or move to Pro or Max.

Revoking access

Access follows the Google file, not just our record of it. If someone removes your Google account from a shared document, the connection stops returning anything even though it still appears on your Connections page, so tidy it up from there when that happens. For a clean break, remove the connector in Claude under Customize → Connectors.

Still stuck?

Reach us at [email protected].