Knowledge Management
Google Docs
Connect Google Docs once and hand every teammate a governed MCP endpoint with 6 tools ready to call from Claude, ChatGPT, Cursor, or any MCP client, inside the same permissions they already have, with every call checked and logged.
Automations & dashboards
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 ship on the Black plan.
Automations
Put Google Docs work on a schedule.
A trigger starts a sequence of steps: call a Google Docs tool, transform the result, branch, wait, and ask a person when it matters.
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
Report on Google Docs without asking.
Collections hold your own data, written by an automation and read by a dashboard that refreshes on a schedule.
Google Docs health
Refreshed 4 minutes ago · every 15 minutes · from the documents collection
Documents
1,284 ↓ 12%
Documentses
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Documents created
Last 14 days
By workspace
Share of activity
Engineering 34%
Product 27%
Support 21%
Sales 18%
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.
list_all_googledocs_documents
List Google Drive documents (Google Docs files). Returns an array of file objects including id, name, and mimeType, filtered to documents only.
get_single_googledocs_document_by_id
Get a single Google Drive document by id. Returns the full file metadata object. Required: id.
create_a_googledocs_document
Create a new Google Docs document. Returns the created document object including its document id and title. Required: title.
list_all_googledocs_userinfo
Retrieves basic profile information about the authenticated user in Google Calendar. The response includes essential details such as the user's unique identifier (sub), full name (name), first name (given_name), last name (family_name), profile picture URL (picture), and email address (email).
list_all_googledocs_document_content
Get a Google document by page_id. Returns the full document object including its body content, title, and revision metadata. Required: page_id.
googledocs_document_content_batch_update
Apply one or more structured updates to a Google document identified by document_id. Returns the document id and an array of replies corresponding to each applied request. Required: document_id and requests.
No tools match your search.
How it works
From Google Docs account to governed MCP endpoint
Connect
Link a Google Docs account through Elaichi's hosted connect flow. Credentials are vaulted, so nobody, including the AI, ever sees them.
Compose
The connection becomes a toolbox instantly. Curate which Google Docs tools are exposed, rename them, or freeze arguments.
Authorize
Point Claude, ChatGPT, Cursor, or any MCP client at the one Elaichi endpoint and sign in with OAuth, governed by roles, restrictions, and audit logs.
Put your agents to work in the tools you already use
Start a 14-day Gold trial. Connect a product, curate a toolbox, and paste a governed MCP endpoint into Claude, ChatGPT, or Cursor in minutes.