Google Docs

Live

OAUTH 2.0

DOCS

Files & Documents

Every document, proposal, and runbook your team writes lives in Google Docs. Google Docs MCP gives your agent authenticated access to documents scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Google Docs account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Google Docs
agent · Acme Q3
Run
Find all proposal documents updated this week and summarize the key sections.
S
gdocs_documents_list
79ms
Document agent
4 proposals updated this week. Acme Enterprise (pricing + SOW updated Oct 29), Globex Renewal (exec summary revised Oct 28), Initech Expansion (scope added Oct 27), Umbrella New (full draft Oct 25).
Sources: 4 documents, this week
googledocsmcp
4 documents
18:29
Message Claude...

Tools your document agent reaches for on Google Docs, scoped per user.

CALL ANY TOOL
Get, create, and update Google Docs, list accessible documents, and share with collaborators.
googledocs_apply_text_style
Apply text style
Apply character formatting (bold, italic, underline, strikethrough, font size) to a range of text in a Google Doc. Only the attributes you set are changed.
Parameters
Name
Type
Required
Description
document_id
string
Required
The ID of the Google Doc to edit
end_index
integer
Required
End index of the range to format (exclusive)
start_index
integer
Required
Zero-based start index of the range to format (inclusive)
bold
boolean
Optional
Set text to bold (true) or non-bold (false)
font_size_pt
number
Optional
Font size in points
italic
boolean
Optional
Set text to italic (true) or non-italic (false)
schema_version
string
Optional
Optional schema version to use for tool execution
strikethrough
boolean
Optional
Set text to struck through (true) or not (false)
tool_version
string
Optional
Optional tool version to use for execution
underline
boolean
Optional
Set text to underlined (true) or not (false)
googledocs_copy_document
Copy document
googledocs_create_comment
Create comment
googledocs_create_document
Create document
googledocs_create_named_range
Create named range
googledocs_create_paragraph_bullets
Create paragraph bullets
googledocs_delete_comment
Delete comment
googledocs_delete_content_range
Delete content range
googledocs_delete_named_range
Delete named range
googledocs_delete_paragraph_bullets
Delete paragraph bullets
googledocs_export_document
Export document
googledocs_insert_inline_image
Insert inline image
googledocs_insert_page_break
Insert page break
googledocs_insert_table
Insert table
googledocs_insert_text
Insert text
googledocs_list_comments
List comments
googledocs_list_documents
List documents
googledocs_read_document
Read document
googledocs_replace_all_text
Replace all text
googledocs_reply_to_comment
Reply to comment
googledocs_resolve_comment
Resolve comment
googledocs_update_document
Update document
googledocs_update_paragraph_style
Update paragraph style
Build your Agent
Drop the toolkit in, point it at the user, and your document agent can use Google Docs from the first run.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["googledocs"], toolNames: ["gdocs_document_get", "gdocs_document_create", "gdocs_document_update"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["googledocs"], toolNames: ["gdocs_document_get", "gdocs_document_create", "gdocs_document_update"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["googledocs"], toolNames: ["gdocs_document_get", "gdocs_document_create", "gdocs_document_update"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/googledocs",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Google Docs.
Search & recall
Copy the prompt
Copied
Find all documents with [keyword] in the title.
Copy the prompt
Copied
Get the content of [document name].
Copy the prompt
Copied
List all documents updated this week.
Copy the prompt
Copied
Find proposals shared with [email].
Action & creation
Copy the prompt
Copied
Create a new document titled [title].
Copy the prompt
Copied
Add a section to [document]: [text].
Copy the prompt
Copied
Replace all instances of [old text] with [new text] in [document].
Copy the prompt
Copied
Share [document] with [email] as editor.
Reporting & drafts
Copy the prompt
Copied
Summarize the key points of [document].
Copy the prompt
Copied
List all headings in [document].
Copy the prompt
Copied
Compare [doc A] and [doc B] for differences.
Copy the prompt
Copied
Find documents with open comments.
SEE HOW AUTH WORKS
Users authorize Google Docs once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Google Docs
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Google Docs
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Google Docs
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Google Docs
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other document agents and MCP connectors. Working code, live demos, fork what fits.
SUPPORT
Support ticket automation (Google ADK)
Google ADK agent that classifies Zendesk tickets, pulls Notion context, and posts to Slack. End-to-end ticket handoff.
ENGINEERING
Engineering standup agent
Aggregate GitHub and GitLab activity, link to Jira, and post a daily standup digest to Slack. No async updates.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Google Docs today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Google Docs as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.
Where is the Google Docs oauth 2.0 stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.
Can I limit what the agent is allowed to do in Google Docs?
Yes. Pass a tool name filter to listScopedTools so the document agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Google Docs.
What happens when a user revokes Google Docs access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Can the agent write to docs the user has view-only access to?
No. Write operations require editor access. View-only access blocks all mutations. The agent inherits the exact edit rights the user has on each document.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""googledocs"": {
""url"": ""https://mcp.scalekit.com/googledocs"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.googledocs]
url = ""https://mcp.scalekit.com/googledocs""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""googledocs"": {
""url"": ""https://mcp.scalekit.com/googledocs"",
""type"": ""http""
}
}
}