Can I use Google Docs as a CLI?

Yes. KosmoKrator exposes a Google Docs CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Google Docs through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Google Docs tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Google Docs credentials stored?

Google Docs credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Google Docs MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Google Docs MCP, CLI, and Lua Integration for AI Agents

Google Docs integration docs for AI agents: MCP gateway setup, Google Docs CLI commands, Lua API reference, credentials, and function schemas.

7 functions 5 read 2 write Manual OAuth token auth

Submit Google Docs feedback View package source

Google Docs for agents

Credentials can be configured manually in web or CLI hosts.

Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.

Machine-Readable Metadata

integration_slug: google-docs
route_slug: google-docs
package: google-docs
auth_strategy: oauth2_manual_token Manual OAuth token
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true
supports_multi_account: true

Quick Links

Lua APIAgent-facing namespace and function reference. Google Docs CLIHeadless setup and direct function calls. Google Docs MCPMCP gateway setup for external clients. Submit feedbackReport missing tools, auth problems, wrong docs, or runtime issues. ContributeAdd tools or improve metadata in the integrations repo.

Google Docs MCP Client Matrix

Use these pages when a specific agent client or framework needs copy-pasteable MCP setup for Google Docs.

Google Docs CLI Matrix

Use these pages for direct Google Docs CLI workflows in scripts, CI, cron, and agent wrappers.

CI Google Docs CLI for CI. Cron Jobs Google Docs CLI for cron jobs. Shell Scripts Google Docs CLI for shell scripts. Headless Automation Google Docs CLI for headless automation. Coding Agents Google Docs CLI for coding agents.

Function Catalog

Function	Type	Parameters	Description
`google-docs.gdocs_list_documents`	Read `read`	3	List Google Docs documents visible to the authenticated user. Returns document IDs, names, owners, and modification times. Supports pagination and custom Drive API query filters.
`google-docs.gdocs_get_document`	Read `read`	1	Get the full content and structure of a Google Docs document by its ID. Returns the document title, body content (paragraphs, text runs), and styling information.
`google-docs.gdocs_create_document`	Write `write`	1	Create a new Google Docs document with a given title. Returns the document ID and a link to edit the document in the browser.
`google-docs.gdocs_batch_update`	Write `write`	2	Send batch update requests to a Google Docs document. Supports inserting text, updating text styles, creating paragraphs, and other document modifications. Each request in the array is a Google Docs API request object.
`google-docs.gdocs_list_permissions`	Read `read`	2	List all permissions (sharing settings) for a Google Docs document. Returns who has access, their roles (owner, writer, reader), and their email addresses.
`google-docs.gdocs_get_permission`	Read `read`	2	Get details of a specific permission for a Google Docs document. Returns the permission type, role, and email address for a single permission entry.
`google-docs.gdocs_get_current_user`	Read `read`	0	Get the authenticated Google user's profile information. Returns user ID, email address, display name, and profile picture URL. Use this to verify which Google account is being used.