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 Gateway for AI Agents

Expose Google Docs tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.

7 functions 5 read 2 write Manual OAuth token auth

Submit Google Docs feedback View package source

Google Docs MCP Gateway

Expose Google Docs to MCP clients with `kosmokrator mcp:serve --integration=google-docs`.

If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server. The gateway exposes only the selected integration in the example below.

curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

kosmokrator mcp:gateway:install --integration=google-docs --write=deny --json

{
  "mcpServers": {
    "kosmokrator-google-docs": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=google-docs",
        "--write=deny"
      ]
    }
  }
}

Serve Manually

kosmokrator mcp:serve --integration=google-docs --write=deny

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names:

MCP tool	Source function	Type
`integration__google_docs__gdocs_list_documents`	`google-docs.gdocs_list_documents`	Read `read`
`integration__google_docs__gdocs_get_document`	`google-docs.gdocs_get_document`	Read `read`
`integration__google_docs__gdocs_create_document`	`google-docs.gdocs_create_document`	Write `write`
`integration__google_docs__gdocs_batch_update`	`google-docs.gdocs_batch_update`	Write `write`
`integration__google_docs__gdocs_list_permissions`	`google-docs.gdocs_list_permissions`	Read `read`
`integration__google_docs__gdocs_get_permission`	`google-docs.gdocs_get_permission`	Read `read`
`integration__google_docs__gdocs_get_current_user`	`google-docs.gdocs_get_current_user`	Read `read`

Write Access

Start with --write=deny for read-only MCP clients. Use --write=ask or --write=allow only when the client and workspace are trusted.