Can I use Google Chat as a CLI?

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

Can I expose Google Chat through MCP?

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

Where are Google Chat credentials stored?

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

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

communication

Google Chat CLI for Headless Automation

Use the Google Chat CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Manual OAuth token auth

Submit Google Chat feedback View package source

Google Chat CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Google Chat CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Google Chat CLI for Headless Automation
kosmokrator integrations:configure google-chat --set access_token="$GOOGLE_CHAT_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call google-chat.google_chat_list_spaces '{"pageSize":1,"pageToken":"example_pageToken"}' --json

Discovery Before Execution

Agents and scripts can inspect Google Chat docs and schemas before choosing a function.

kosmo integrations:docs google-chat --json
kosmo integrations:docs google-chat.google_chat_list_spaces --json
kosmo integrations:schema google-chat.google_chat_list_spaces --json
kosmo integrations:search "Google Chat" --json
kosmo integrations:list --json

Useful Google Chat CLI Functions

Function	Type	Parameters	Description
`google-chat.google_chat_list_spaces`	Read	pageSize, pageToken	List Google Chat spaces the authenticated user belongs to. Returns space names, display names, and types. Supports pagination with pageSize and pageToken.
`google-chat.google_chat_get_space`	Read	name	Get details about a specific Google Chat space. Returns the space name, display name, type, and other metadata.
`google-chat.google_chat_list_messages`	Read	parent, pageSize, pageToken	List messages in a Google Chat space. Returns message text, sender info, and creation timestamps. Supports pagination with pageSize and pageToken.
`google-chat.google_chat_get_message`	Read	parent, name	Get a specific message from a Google Chat space. Returns the full message including text, cards, sender, and annotations.
`google-chat.google_chat_create_message`	Write	parent, text, cardsV2	Send a message to a Google Chat space. Supports plain text and card-based rich messages (cardsV2). Either text or cardsV2 must be provided.
`google-chat.google_chat_list_memberships`	Read	parent, pageSize, pageToken	List members (human users and bots) in a Google Chat space. Returns member names, display names, and roles. Supports pagination with pageSize and pageToken.
`google-chat.google_chat_get_current_user`	Read	parent	Get the authenticated user's membership details in a Google Chat space. Returns the user's display name, role, and membership state.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Google Chat CLI Pages

CI Google Chat CLI for CI. Cron Jobs Google Chat CLI for cron jobs. Shell Scripts Google Chat CLI for shell scripts. Coding Agents Google Chat CLI for coding agents.