Can I use Google Forms as a CLI?

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

Can I expose Google Forms through MCP?

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

Where are Google Forms credentials stored?

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

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

productivity

Google Forms CLI for Headless Automation

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

7 functions 5 read 2 write Manual OAuth token auth

Submit Google Forms feedback View package source

Google Forms 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 Forms CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Google Forms CLI for Headless Automation
kosmokrator integrations:configure google-forms --set access_token="$GOOGLE_FORMS_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call google-forms.gforms_list_forms '{"pageSize":1,"pageToken":"example_pageToken","filter":"example_filter"}' --json

Discovery Before Execution

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

kosmo integrations:docs google-forms --json
kosmo integrations:docs google-forms.gforms_list_forms --json
kosmo integrations:schema google-forms.gforms_list_forms --json
kosmo integrations:search "Google Forms" --json
kosmo integrations:list --json

Useful Google Forms CLI Functions

Function	Type	Parameters	Description
`google-forms.gforms_list_forms`	Read	pageSize, pageToken, filter	List Google Forms owned by the authenticated user. Returns form IDs, titles, and metadata. Supports pagination and filtering.
`google-forms.gforms_get_form`	Read	id	Get the full details of a specific Google Form, including its questions, layout, and settings.
`google-forms.gforms_create_form`	Write	info, title, description, documentTitle	Create a new Google Form. Provide a title and optional description. The form will appear in the authenticated user's Google Drive.
`google-forms.gforms_list_responses`	Read	id, pageSize, pageToken, filter	List responses submitted to a Google Form. Returns answers, timestamps, and respondent metadata. Supports pagination and filtering by date.
`google-forms.gforms_get_response`	Read	form_id, id	Get a specific form response by ID. Returns all answers, the submission timestamp, and respondent metadata.
`google-forms.gforms_create_response`	Write	id, answers	Submit a response to a Google Form. Provide answers keyed by question ID. Use get_form first to discover question IDs and their types.
`google-forms.gforms_get_current_user`	Read	none	Get the authenticated Google user's profile — email, display name, and profile photo. Use this to verify the connected account.

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 Forms CLI Pages

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