Google Docs MCP connector

First, connect Google Docs in Elaichi. Google Docs connects over OAuth, so you sign in with your own Google account in the usual pop-up window, and there is no client ID or secret to generate and no application to register. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and Google Docs is ready to use.

Yes. Once Google Docs is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Google Docs once, and every client you add afterward picks it up without a second setup.

With Google Docs connected, an agent can list the documents you have access to, open a specific document and read its full text, create a new document, and make edits to an existing one such as inserting, replacing, or restructuring text. In practice that means asking for a summary of a long document, drafting a proposal from your notes, or updating a help article after a process changes. It works only with documents your Google account can already open.

No. When Google Docs is connected through Elaichi, the agent works inside the access of the person who signed in, so it can only see documents that person could already open in Google Docs, and sharing rules on each document still apply. Elaichi can narrow that access further, for example by allowing reading but not editing, but it can never widen it beyond what the person already has.

Yes. One person connects Google Docs in Elaichi and shares the connection with a team, and nobody else on that team ever handles a credential or signs in to Google separately. Each person still signs in to Elaichi as themselves, so every read or edit in Google Docs is recorded against the individual who made it, not against a shared account.

Yes. Restrictions in Elaichi work per action, so you can let an agent search and read Google Docs documents while blocking it from creating or editing them. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client at all, so no prompt, however worded, can reach it.

When a person is offboarded in Elaichi, their access to Google Docs through Elaichi ends at once, across every client they used. A shared Google Docs connection keeps working for everyone else on the team, so nobody has to reconnect. If you ever want to remove Google Docs entirely, disconnecting it once in Elaichi removes it from every client at the same time.

Yes. Google Docs is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Yes. Both let Claude, ChatGPT or Cursor use Google Docs. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Google Docs call.

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Google Docs: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.