First-party app

Google Docs

Name: Google Docs
Author: w6w

Create, read and structurally update Google Docs documents.

stable ProductivityDocuments & Files

About

Google Docs ships in the w6w first-party pack. It declares 20 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.

App id: io.w6w.google-docs
Version: 0.2.2
Author: w6w
Licence: MIT
Categories: Productivity · Documents & Files

Overview

Google Docs creates and structurally edits documents from a workflow — not just appending text, but inserting and formatting tables, adding page breaks, turning a paragraph into a bulleted list, and managing headers, footers and named ranges the way a person editing the document by hand would.

Text itself can be inserted at a position or replaced by matching pattern across the whole document, and a full document can be read back to check its current structure before making a change. A batch-update action covers issuing several of these edits as one atomic call, matching how the underlying Docs API is actually built.

A fit for generating a document from a template — a report, a contract, a proposal — populating it with data from earlier in a workflow, or reading a document’s contents back for further processing elsewhere.

Build with Google Docs

Three routes to the same 20 actions. The Workflow tab is generated from Google Docs's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.

Actions Workflow Code MCP

Batch Update (raw)

document-batch-update

Send an arbitrary array of Google Docs `Request` objects to `documents.batchUpdate`. Use per-verb actions when possible; this is the escape hatch.

Create Document

document-create

Create a new Google Doc (optionally inside a specific Drive folder).

Create Footer

document-create-footer

Create a footer on the document.

Create Header

document-create-header

Create a header on the document.

Create Named Range

document-create-named-range

Create a named range over a start/end index within a segment.

Create Paragraph Bullets

document-create-paragraph-bullets

Apply a bullet style to a paragraph range.

Delete Footer

document-delete-footer

Delete a footer by ID (find it in `Get Document → simple = false → footers`).

Delete Header

document-delete-header

Delete a header by ID (find it in `Get Document → simple = false → headers`).

Delete Named Range

document-delete-named-range

Delete a named range by its ID, or every range with a given name.

Delete Paragraph Bullets

document-delete-paragraph-bullets

Remove bullet glyphs from a paragraph range.

Delete Positioned Object

document-delete-positioned-object

Delete a positioned object by ID.

Delete Table Column

document-delete-table-column

Delete the column containing the given cell.

Delete Table Row

document-delete-table-row

Delete the row containing the given cell.

Get Document

document-get

Retrieve a document by ID or Google Docs URL.

Insert Page Break

document-insert-page-break

Insert a page break at a location.

Insert Table

document-insert-table

Insert an empty rows × columns table at a location.

Insert Table Column

document-insert-table-column

Insert a table column to the left or right of an existing cell.

Insert Table Row

document-insert-table-row

Insert a table row above or below an existing cell.

Insert Text

document-insert-text

Insert text into a document at a specific index or at the end of a segment.

Find and Replace Text

document-replace-text

Replace every occurrence of a search string with a new string.

A workflow step names the app and the action, and the editor fills in the connection when you pick one. This is the Step shape from the workflow spec, carrying Google Docs's real ids.

{
  "manifestVersion": "2",
  "name": "google-docs-example",
  "steps": [
    {
      "id": "document-batch-update",
      "uses": {
        "app": "io.w6w.google-docs",
        "action": "document-batch-update",
        "connection": "conn_YOUR_CONNECTION_ID"
      },
      "with": {
        "documentURL": "<documentURL>",
        "requests": "<requests>"
      }
    }
  ]
}

Here are some of the things you can do

Batch Update (raw)
perform
document-batch-update
Create Document
perform
document-create
Create Footer
perform
document-create-footer
Create Header
perform
document-create-header
Create Named Range
perform
document-create-named-range

+15 more actions available

Every app-specific value here is a blank you have to fill in. An app action is reached through the connection that authenticates it, so the address is a connection id, not the app id — and connections belong to your account, so a public page cannot know yours. Create one for Google Docs, then fill in the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the parameters that action declares. The call itself is real — the shape is transcribed from the studio's own snippet builder, which prints the same kind of blanks — but nothing in it is specific to Google Docs. The Workflow tab is where this app's real ids are.

JS SDK CLI

Install

npm yarn pnpm deno

npm install @w6w/sdk

yarn add @w6w/sdk

pnpm add @w6w/sdk

deno add npm:@w6w/sdk

Code

import { W6wClient, isActionRun } from "@w6w/sdk";

// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();

const envelope = await client.run({
  urn: "conn_YOUR_CONNECTION_ID",
  action: "document-create",
  payload: {
    title: "<value>",
    // folderId: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);

Install the CLI

npm install -g @w6w/cli

CLI

w6w run conn_YOUR_CONNECTION_ID --action document-create --payload '{"title":"<value>"}'

Give an AI agent Google Docs — without giving it Google Docs's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.

One tool call

{
  "name": "w6w_invoke",
  "arguments": {
    "ref": "app:io.w6w.google-docs#document-batch-update",
    "input": {
      "documentURL": "<documentURL>",
      "requests": "<requests>"
    }
  }
}

Every tool names its target with a single ref. The app: form above doesn't name a connection at all — the host resolves which of the caller's Google Docs connections to sign with, and refuses rather than guesses when the answer is ambiguous.

What the agent gets

Credentials it can't read

The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.

A tool surface scoped to the caller

Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.

A durable workflow in one call

Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.

Health-aware discovery

Google Docs's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.

The MCP surface is part of the hosted platform. Google Docs itself is MIT, and the runtime that executes it is source-available (FSL).

Request MCP access

Health checks

Google Docs declares its own checks, so its health is a property of the app rather than something the host guesses at.

service

Google Docs platform status

Open incidents for Google Docs on the Google Workspace Status Dashboard. Unauthenticated and unsigned.

quota