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

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

7 functions 5 read 2 write Manual OAuth token auth

Submit Google Tasks feedback View package source

Google Tasks CLI Setup

Google Tasks can be configured headlessly with `kosmokrator integrations:configure google-tasks`.

# 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-tasks --set access_token="$GOOGLE_TASKS_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor google-tasks --json
kosmokrator integrations:status --json

Credentials

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

Key	Env var	Type	Required	Label
`access_token`	`GOOGLE_TASKS_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`GOOGLE_TASKS_URL`	URL `url`	no	API Base URL

Call Google Tasks Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call google-tasks.gtasks_list_task_lists '{
  "maxResults": 1,
  "pageToken": "example_pageToken",
  "showCompleted": true,
  "showHidden": true
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:google-tasks gtasks_list_task_lists '{
  "maxResults": 1,
  "pageToken": "example_pageToken",
  "showCompleted": true,
  "showHidden": true
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities 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

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Google Tasks.

`google-tasks.gtasks_list_task_lists`

Read read

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.

Parameters: maxResults, pageToken, showCompleted, showHidden

Generic CLI call

kosmo integrations:call google-tasks.gtasks_list_task_lists '{"maxResults":1,"pageToken":"example_pageToken","showCompleted":true,"showHidden":true}' --json

Provider shortcut

kosmo integrations:google-tasks gtasks_list_task_lists '{"maxResults":1,"pageToken":"example_pageToken","showCompleted":true,"showHidden":true}' --json

`google-tasks.gtasks_get_task_list`

Read read

Get a specific task list by its ID in Google Tasks. Returns the task list title, ID, and other metadata.

Parameters: id

Generic CLI call

kosmo integrations:call google-tasks.gtasks_get_task_list '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:google-tasks gtasks_get_task_list '{"id":"example_id"}' --json

`google-tasks.gtasks_create_task_list`

Write write

Create a new task list in Google Tasks. Provide a title for the new list.

Parameters: title

Generic CLI call

kosmo integrations:call google-tasks.gtasks_create_task_list '{"title":"example_title"}' --json

Provider shortcut

kosmo integrations:google-tasks gtasks_create_task_list '{"title":"example_title"}' --json

`google-tasks.gtasks_list_tasks`

Read read

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.

Parameters: list_id, maxResults, pageToken, showCompleted, dueDate

Generic CLI call

kosmo integrations:call google-tasks.gtasks_list_tasks '{"list_id":"example_list_id","maxResults":1,"pageToken":"example_pageToken","showCompleted":true,"dueDate":"example_dueDate"}' --json

Provider shortcut

kosmo integrations:google-tasks gtasks_list_tasks '{"list_id":"example_list_id","maxResults":1,"pageToken":"example_pageToken","showCompleted":true,"dueDate":"example_dueDate"}' --json

`google-tasks.gtasks_get_task`

Read read

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.

Parameters: list_id, id

Generic CLI call

kosmo integrations:call google-tasks.gtasks_get_task '{"list_id":"example_list_id","id":"example_id"}' --json

Provider shortcut

kosmo integrations:google-tasks gtasks_get_task '{"list_id":"example_list_id","id":"example_id"}' --json

`google-tasks.gtasks_create_task`

Write write

Create a new task in a Google Tasks list. Provide a title, and optionally notes and a due date.

Parameters: list_id, title, notes, due

Generic CLI call

kosmo integrations:call google-tasks.gtasks_create_task '{"list_id":"example_list_id","title":"example_title","notes":"example_notes","due":"example_due"}' --json

Provider shortcut

kosmo integrations:google-tasks gtasks_create_task '{"list_id":"example_list_id","title":"example_title","notes":"example_notes","due":"example_due"}' --json

`google-tasks.gtasks_get_current_user`

Read read

Get information about the currently authenticated Google user. Useful for verifying the connected account.

Parameters: none

Generic CLI call

kosmo integrations:call google-tasks.gtasks_get_current_user '{}' --json

Provider shortcut

kosmo integrations:google-tasks gtasks_get_current_user '{}' --json

Function Schemas

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

`google-tasks.gtasks_list_task_lists`

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.

Operation: Read read
Schema command: kosmo integrations:schema google-tasks.gtasks_list_task_lists --json

Parameter	Type	Required	Description
`maxResults`	integer	no	Maximum number of task lists to return per page (default: 20, max: 100).
`pageToken`	string	no	Token for the next page of results from a previous list call.
`showCompleted`	boolean	no	Whether to show completed tasks in the response (default: true).
`showHidden`	boolean	no	Whether to show hidden task lists (default: false).

`google-tasks.gtasks_get_task_list`

Get a specific task list by its ID in Google Tasks. Returns the task list title, ID, and other metadata.

Operation: Read read
Schema command: kosmo integrations:schema google-tasks.gtasks_get_task_list --json

Parameter	Type	Required	Description
`id`	string	yes	The task list ID (use "list_task_lists" to find IDs).

`google-tasks.gtasks_create_task_list`

Create a new task list in Google Tasks. Provide a title for the new list.

Operation: Write write
Schema command: kosmo integrations:schema google-tasks.gtasks_create_task_list --json

Parameter	Type	Required	Description
`title`	string	yes	The title of the new task list (e.g., "Work Projects", "Shopping List").

`google-tasks.gtasks_list_tasks`

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.

Operation: Read read
Schema command: kosmo integrations:schema google-tasks.gtasks_list_tasks --json

Parameter	Type	Required	Description
`list_id`	string	yes	The task list ID (use "list_task_lists" to find IDs). Use "@" for the default list.
`maxResults`	integer	no	Maximum number of tasks to return per page (default: 20, max: 100).
`pageToken`	string	no	Token for the next page of results from a previous list call.
`showCompleted`	boolean	no	Whether to include completed tasks (default: true).
`dueDate`	string	no	ISO 8601 timestamp to filter tasks due before this date (e.g., "2026-04-30T00:00:00.000Z").

`google-tasks.gtasks_get_task`

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.

Operation: Read read
Schema command: kosmo integrations:schema google-tasks.gtasks_get_task --json

Parameter	Type	Required	Description
`list_id`	string	yes	The task list ID (use "list_task_lists" to find IDs).
`id`	string	yes	The task ID (use "list_tasks" to find task IDs).

`google-tasks.gtasks_create_task`

Create a new task in a Google Tasks list. Provide a title, and optionally notes and a due date.

Operation: Write write
Schema command: kosmo integrations:schema google-tasks.gtasks_create_task --json

Parameter	Type	Required	Description
`list_id`	string	yes	The task list ID (use "list_task_lists" to find IDs). Use "@" for the default list.
`title`	string	yes	The title of the task (e.g., "Buy groceries").
`notes`	string	no	Notes or description for the task.
`due`	string	no	Due date in RFC 3339 format (e.g., "2026-04-30T00:00:00.000Z").

`google-tasks.gtasks_get_current_user`

Get information about the currently authenticated Google user. Useful for verifying the connected account.

Operation: Read read
Schema command: kosmo integrations:schema google-tasks.gtasks_get_current_user --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.