Can I use Google Tasks as a CLI?

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

Can I expose Google Tasks through MCP?

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

Where are Google Tasks credentials stored?

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

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

productivity

Google Tasks CLI for Headless Automation

Use the Google Tasks 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 Tasks feedback View package source

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

Command Shape

# Google Tasks CLI for Headless Automation
kosmokrator integrations:configure google-tasks --set access_token="$GOOGLE_TASKS_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call google-tasks.gtasks_list_task_lists '{"maxResults":1,"pageToken":"example_pageToken","showCompleted":true,"showHidden":true}' --json

Discovery Before Execution

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

kosmo integrations:docs google-tasks --json
kosmo integrations:docs google-tasks.gtasks_list_task_lists --json
kosmo integrations:schema google-tasks.gtasks_list_task_lists --json
kosmo integrations:search "Google Tasks" --json
kosmo integrations:list --json

Useful Google Tasks CLI Functions

Function	Type	Parameters	Description
`google-tasks.gtasks_list_task_lists`	Read	maxResults, pageToken, showCompleted, showHidden	List all task lists for the authenticated user in Google Tasks. Returns task list IDs and titles that can be used to manage tasks within each list.
`google-tasks.gtasks_get_task_list`	Read	id	Get a specific task list by its ID in Google Tasks. Returns the task list title, ID, and other metadata.
`google-tasks.gtasks_create_task_list`	Write	title	Create a new task list in Google Tasks. Provide a title for the new list.
`google-tasks.gtasks_list_tasks`	Read	list_id, maxResults, pageToken, showCompleted, dueDate	List tasks in a specific task list in Google Tasks. Returns task titles, IDs, status, due dates, and notes. Use "list_task_lists" first to find the task list ID.
`google-tasks.gtasks_get_task`	Read	list_id, id	Get a specific task by its ID from a task list in Google Tasks. Returns the task title, notes, due date, status, and other details.
`google-tasks.gtasks_create_task`	Write	list_id, title, notes, due	Create a new task in a Google Tasks list. Provide a title, and optionally notes and a due date.
`google-tasks.gtasks_get_current_user`	Read	none	Get information about the currently authenticated Google user. Useful for verifying 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 Tasks CLI Pages

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