Knowledge Management
Google Docs MCP connector
Connecting Google Docs to Elaichi lets Claude, ChatGPT, Cursor, and any MCP client find, read, create, and edit Google Docs documents as the person who signed in, with every change recorded in an audit log.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
6 tools
How to connect
How to connect Google Docs to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Google Docs once
-
Open Connections, choose Add connection, and pick Google Docs.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Google Docs. Google Docs's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Google Docs to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Google Docs to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Google Docs to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Google Docs to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Google Docs through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Draft a proposal from call notes
After a discovery call, ask the agent to turn your notes into a new proposal document in Google Docs, laid out under the headings your team already uses.
-
Support
Keep help articles current after a fix
When a workaround changes, ask the agent to find the right Google Docs article and rewrite the affected steps so the desk stops sending customers outdated instructions.
-
Marketing
Turn a brief into a first draft
Point the agent at a campaign brief in Google Docs and have it create a draft blog post or launch announcement in a new document, ready for a human edit.
-
People
Answer policy questions from the handbook
Ask what the parental leave policy says and get the answer pulled from the actual handbook document in Google Docs, with the wording as it currently stands.
-
Operations
Summarize a long meeting document
Drop in a meeting notes document and ask for the decisions and open actions, so people who missed the session get a short readout instead of ten pages.
-
Legal
Find every document that mentions a vendor
Ask which Google Docs documents reference a particular supplier or contract term, then open the right one and check the clause before renewal.
Try asking
- “Summarize the documents created in the handbook folder this week.”
- “Draft a launch brief document from last week's meeting notes.”
- “List documents I have edited since Monday with their titles.”
AI tools
Google Docs tools for your AI agents
6 tools are ready to call through Elaichi's MCP endpoint the moment you connect Google Docs, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Google Docs gets you
6 screens from the product, each doing one job for your Google Docs account.
The agent
Ask about documents, get answers back.
Type a question in plain language and read live Google Docs documents.
- documents
- document content
- revisions
- userinfo
Ask Elaichi to work across your apps.
Summarize the documents created in the handbook folder this week.
Draft a launch brief document from last week's meeting notes.
List documents I have edited since Monday with their titles.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor, one endpoint.
Connect any MCP client to Google Docs over OAuth, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
6 Google Docs tools, zero custom code.
Browse documents, content and userinfo tools with their resources and methods listed.
- List all Google Docs documents
- Get single Google Docs document by ID
- Create a Google Docs document
- List all Google Docs userinfo
ElaichiToolsToolboxes
Every team gets its own toolbox.
Curate one Google Docs toolbox per team and scope it to that team.
- Product
- Marketing
- Legal
- People
ElaichiToolboxesShared connections
Teammates draft docs without touching credentials.
See who connected each Google Docs account and which teams and members share it.
- Product
- Marketing
- Legal
- People Ops
ElaichiConnectionsAudit log
Every document call is on the record.
When, who, what happened, type and resource for each Google Docs call.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest ships.
Fetch documents, group them, draft a digest, get approval, post back to Google Docs.
Google Docs digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch documents
Google Docs
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Google Docs
Queued
Collections and dashboards
Document numbers arrive without anyone asking.
Four metrics, 14 days of documents created, split by team, refreshed on schedule.
Google Docs health
Refreshed 4 minutes ago · every 15 minutes · from the documents collection
Documents
1,284 ↓ 12%
Document content
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Documents created
Last 14 days
By team
Share of activity
Product 34%
Marketing 27%
Legal 21%
People Ops 18%
FAQ
Frequently asked questions
How do I connect Google Docs to Claude?
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.
Does Google Docs work with ChatGPT and Cursor as well as Claude?
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.
What can an AI agent actually do with my Google Docs data?
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.
Does connecting Google Docs give the AI access to every document in my Google workspace?
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.
Can I stop an agent from changing or overwriting things in Google Docs?
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.
What happens to a Google Docs connection when someone leaves?
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.
Put Google Docs in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.