Google Docs integration for AI agents.
Google Docs integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Google Docs tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real Google Docs actions, managed and audited.
Your user connects Google Docs once; your agent can then secure AI-agent actions — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants Google Docs access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported Google Docs tools.
3 tools are generated from the published Google Docs catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 3 tools. All published catalog entries are included in this page's server-rendered HTML.
- Docs Documents BatchUpdate
- Applies one or more updates to the document. Each request is validated before being applied. If any request is not valid, then the entire request will fail and nothing will be applied. Some requests have replies to give you some information about how they are applied. Other requests do not need to return information; these each return an empty reply. The order of replies matches that of the requests. For example, suppose you call batchUpdate with four updates, and only the third one returns information. The response would have two empty replies, the reply to the third request, and another empty reply, in that order. Because other users may be editing the document, the document might not exactly reflect your changes: your changes may be altered with respect to collaborator changes. If there are no collaborators, the document should reflect your changes. In any case, the updates in your request are guaranteed to be applied together atomically.
- documents
- Docs Documents Create
- Creates a blank document using the title given in the request. Other fields in the request, including any provided content, are ignored. Returns the created document.
- documents
- Docs Documents Get
- Gets the latest version of the specified document.
- documents
Google Docs integration, answered
- How do AI agents use Google Docs through Open Connector?
- Your user connects Google Docs once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Docs tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Google Docs MCP server?
- Yes. Open Connector can serve Google Docs as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Docs actions with credentials injected server-side.
- Where do Google Docs credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Google Docs — keep the keys.
Open source, self-hostable, with Google Docs credentials that never leave your infrastructure. Run it from source today.