Integration

Google Docs integration

Google Docs API for creating, reading, and editing Google Docs documents programmatically. Create blank documents, fetch the full structured content of a document, and apply rich batch edits - insert and replace text, format paragraphs and text runs, manage lists, tables, headers/footers, and named ranges. Ideal for document generation, templating, mail-merge style automation, and content extraction workflows.

Connect Google Docs How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Google Docs.Built from the 3 Google Docs tools below, on the connection you add once.

Common Google Docs use cases

reading document text for processing or analysis
filling a template document with data (mail merge)
generating documents from templates programmatically
creating draft reports for downstream editing
inserting generated text and headings into a doc
computing character indexes before applying edits
producing documents from automation workflows
find-and-replace placeholders across a document
extracting content for export or search indexing
creating per-customer documents in a loop

What you can do with Google Docs

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

batch_update_documentBatch update documentPOSTApplies an ordered batch of edits to a Google Docs document: insert/delete/replace text, update text and paragraph styles, insert tables and images, create bullets and named ranges, and more. Validated atomically - if any request is invalid, nothi...
create_documentCreate documentPOSTCreates a new blank Google Docs document with the given title. Returns the new documentId and an empty body. Use this first, then call batch_update_document to insert text and formatting. The document is created in the authenticated user's Google ...
get_documentGet documentGETRetrieves the full structured content of a Google Docs document by ID. Returns the title, revisionId, and the body as an ordered array of structural elements (paragraphs, tables, section breaks) with character index ranges. Essential for reading d...

Use Google Docs from Claude Code, Cursor or Codex

Connect Google Docs in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google Docs operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Google Docs

Create your workspace
Sign up free. Nothing to install.
Connect Google Docs once
Add your Google Docs connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Google Docs integration FAQ

What can you do with the Google Docs integration?

LiveContext exposes 3 operations on Google Docs, covering document. Common uses include reading document text for processing or analysis, filling a template document with data (mail merge) and generating documents from templates programmatically.