MCP connectorsGoogle Docs

Google Docs MCP: connect Google Docs to Claude and ChatGPT

Ask Claude or ChatGPT what the onboarding handbook says about the first week, to turn this morning’s notes into a new Doc, or to add the decisions from the leadership meeting to the end of its running log. The AI reads Google Docs with their headings, lists and tables, and gives you the link.

With Deployed OS everyone connects their own Google account. The AI opens only the documents that person can already open. With Edit access it can create a Doc in their own Drive or add text at the end of one, after they confirm the words. Existing text is never changed.

2 read actions · 2 write actions · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Google Docs in Claude and ChatGPT

Management

Minutes that end up in the right place

Paste your notes from the leadership meeting and get the decisions and owners back. Once you approve them, the AI adds them to the end of the running meeting log, dated, so the log stays current.
Sales

A first draft of the proposal

Ask for a proposal for Fjällgren Bygg based on your proposal template and the call notes. The AI creates it as a new Doc in your Drive, shared with nobody, ready for you to polish and send.
HR and operations

Policies read the way they were written

The expense policy or the onboarding handbook comes through with its headings and tables, so the answer points to the right section. New people ask in plain words and get the link to the Doc.
Projects

Briefs and plans, heading by heading

Get the outline of a long project brief first, then ask about one section: scope, open questions, the timeline table. Quicker than scrolling forty pages before the steering group.
Examples

Ask it like this

  • “Find the onboarding handbook and give me its outline.”

  • “What does our expense policy say about client dinners? Tell me which section it is in.”

  • “Add to the end of the Leadership meeting log: 3 October, we move the launch to week 46, Sara owns the press plan.”

  • “Create a Doc called “Proposal, Fjällgren Bygg” with a first draft based on my call notes above.”

  • “Read the product brief for the autumn launch and list the open questions from its table.”

  • “Which Docs have “board” in the name, who owns them and when did they last change?”

The connector

What the Google Docs MCP connector does today

  • Readsdocs_search_documents

    Finds the Google Docs you can open by words in their names. Returns name, owner, last change and link for each.

  • Readsdocs_read_document

    Reads one Google Doc you can open as text, with its headings, lists and tables and an outline of the headings. Long documents are cut at 200 KB.

  • Writesdocs_create_document

    Creates a Google Doc in your own Drive with a title and, if you want, plain text, once you have confirmed both. It is shared with nobody.

  • Writesdocs_append_text

    Adds plain text at the end of a Google Doc you may edit, once you have confirmed the text. Nothing else in the document changes and nobody is notified.

Need it to do more? We extend connectors for the companies that use them.

Security

Who sees what

Reads, plus new text
The connector finds Docs by name and reads them with headings, lists and tables. With Edit it can create a Doc or add plain text at the end of one. It cannot change or delete existing text, share a document or leave comments.
Each person’s own rights
Everyone connects their own Google account, so the AI opens what that person can open and adds text only where they may edit. A board memo shared with three people stays with those three.
Writing only with Edit access
Admins choose which groups get Google Docs, and only groups with Edit access can create documents or add text. Each write is done as the person asking, after they confirm the text, and nobody is notified.
Every call logged
Who read which document, who wrote what, when. Deployed OS shows reads and writes per connector and per person, the log can be exported, and access is revoked centrally the day someone leaves.
Setup

Set up the Google Docs connector in three steps

01
An admin creates a project in your company’s Google Cloud, sets up an internal OAuth app and turns on the Docs API. The same Google app serves Drive, Gmail, Sheets and Slides, and your company owns it. If you already have it, the admin turns on the Docs API and adds one redirect URI.
02
The admin adds the app’s Client ID and Client secret to Deployed OS, chooses which groups get Google Docs and which of them have Edit access to write.
03
Each person connects their own Google work account. From then on they just ask, in Claude, ChatGPT or Copilot.
Compared

Google Docs’s own MCP server or Deployed OS?

Google runs its own remote MCP server for Docs, one of its Workspace MCP servers, available through the Google Workspace Developer Preview Program. A developer turns it on in a Google Cloud project and connects an AI client, which can then read a document and edit it, for example by inserting or replacing text. For one person, or a developer building an agent, that is a good fit.

Deployed OS is built for the whole company: one connection for Google Docs and the rest of your tools, each person’s own login, admins choosing which groups may read and which may write, and a log of every call. The same connection works in Claude, ChatGPT and Copilot, next to your company’s skills and guardrails.

Their documentation: Google’s Docs MCP server

Questions

Google Docs MCP: common questions

Yes. Google has a remote MCP server for Docs in its Workspace Developer Preview Program, which a developer sets up in a Google Cloud project. Deployed OS gives the whole company one connection instead, with each person’s own login, access per group and a log of every call.

Only by adding. With Edit access it can create a new Doc in your own Drive, shared with nobody, or add text at the end of a Doc you may edit, when you ask and confirm the text. Text goes in plain, without formatting. It never rewrites or deletes existing text, shares a document or notifies anyone. If you want it to do more, for example add comments, we can extend it for you.

Your admin sets up Google Docs in Deployed OS once. You add your company’s Deployed OS connection in Claude, connect your own Google work account and start asking. The same connection works in ChatGPT and Copilot.

The Google Drive connector searches every file by name or content and reads a Doc as plain text, read-only. The Google Docs connector finds documents by name, reads them with headings, lists, tables and an outline, and with Edit access can write. You can turn on both.

Only the ones they can already open in Google Docs. The AI uses each person’s own Google account, so your sharing settings apply as they are, and a new Doc is shared with nobody until its owner shares it.

Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. On-premises is possible too. Documents are fetched from Google Docs when someone asks for them.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors
Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.

Poyan Karimi
You’ll hear from Poyan Karimi
Co-founder · Deployed AI