Can I use Google Drive Activity as a CLI?

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

Can I expose Google Drive Activity through MCP?

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

Where are Google Drive Activity credentials stored?

Google Drive Activity 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 Drive Activity MCP tools?

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

productivity

Google Drive Activity CLI for AI Agents

Use the Google Drive Activity CLI from KosmoKrator to call Google Drive Activity tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Google Drive Activity CLI Setup

Google Drive Activity can be configured headlessly with `kosmokrator integrations:configure google-drive-activity`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure google-drive-activity --enable --read allow --write ask --json
kosmokrator integrations:doctor google-drive-activity --json
kosmokrator integrations:status --json

Credentials

Authentication type: Manual OAuth token oauth2_manual_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

No credentials are required.

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call google-drive-activity.google_drive_activity_activity_query '{}' --json

Provider shortcut

kosmo integrations:google-drive-activity google_drive_activity_activity_query '{}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

kosmo integrations:docs google-drive-activity --json
kosmo integrations:docs google-drive-activity.google_drive_activity_activity_query --json
kosmo integrations:schema google-drive-activity.google_drive_activity_activity_query --json
kosmo integrations:search "Google Drive Activity" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`google-drive-activity.google_drive_activity_activity_query`

Activity Query (POST /v2/activity:query).

Write write

Parameters: none

Generic call

kosmo integrations:call google-drive-activity.google_drive_activity_activity_query '{}' --json

Shortcut

kosmo integrations:google-drive-activity google_drive_activity_activity_query '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

google-drive-activity.google_drive_activity_activity_query 0 parameters

Schema command

kosmo integrations:schema google-drive-activity.google_drive_activity_activity_query --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.