Can I use Wrike as a CLI?

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

Can I expose Wrike through MCP?

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

Where are Wrike credentials stored?

Wrike credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Wrike MCP tools?

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

productivity

Wrike CLI for AI Agents

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

Wrike CLI Setup

Wrike can be configured headlessly with `kosmokrator integrations:configure wrike`.

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

Credentials

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

Key	Env var	Type	Required	Label
`access_token`	`WRIKE_ACCESS_TOKEN`	Secret `secret`	yes	Access Token

Command Patterns

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

Generic CLI call

kosmo integrations:call wrike.wrike_create_task '{"folderId":"example_folderId","title":"example_title","description":"example_description","importance":"example_importance","status":"example_status","dates":"example_dates","assignees":"example_assignees"}' --json

Provider shortcut

kosmo integrations:wrike wrike_create_task '{"folderId":"example_folderId","title":"example_title","description":"example_description","importance":"example_importance","status":"example_status","dates":"example_dates","assignees":"example_assignees"}' --json

Discovery

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

Discovery commands

kosmo integrations:docs wrike --json
kosmo integrations:docs wrike.wrike_create_task --json
kosmo integrations:schema wrike.wrike_create_task --json
kosmo integrations:search "Wrike" --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.

`wrike.wrike_create_task`

Create a new task in Wrike.

Write write

Parameters: folderId, title, description, importance, status, dates, assignees

Generic call

kosmo integrations:call wrike.wrike_create_task '{"folderId":"example_folderId","title":"example_title","description":"example_description","importance":"example_importance","status":"example_status","dates":"example_dates","assignees":"example_assignees"}' --json

Shortcut

kosmo integrations:wrike wrike_create_task '{"folderId":"example_folderId","title":"example_title","description":"example_description","importance":"example_importance","status":"example_status","dates":"example_dates","assignees":"example_assignees"}' --json

`wrike.wrike_get_task`

Get detailed information about a Wrike task.

Read read

Parameters: id

Generic call

kosmo integrations:call wrike.wrike_get_task '{"id":"example_id"}' --json

Shortcut

kosmo integrations:wrike wrike_get_task '{"id":"example_id"}' --json

`wrike.wrike_update_task`

Update an existing Wrike task.

Write write

Parameters: task_id, title, description, status, importance, dates_due

Generic call

kosmo integrations:call wrike.wrike_update_task '{"task_id":"example_task_id","title":"example_title","description":"example_description","status":"example_status","importance":"example_importance","dates_due":"example_dates_due"}' --json

Shortcut

kosmo integrations:wrike wrike_update_task '{"task_id":"example_task_id","title":"example_title","description":"example_description","status":"example_status","importance":"example_importance","dates_due":"example_dates_due"}' --json

`wrike.wrike_list_tasks`

List tasks in Wrike with optional filters.

Read read

Parameters: folderId, status, importance, limit, nextPageToken

Generic call

kosmo integrations:call wrike.wrike_list_tasks '{"folderId":"example_folderId","status":"example_status","importance":"example_importance","limit":1,"nextPageToken":"example_nextPageToken"}' --json

Shortcut

kosmo integrations:wrike wrike_list_tasks '{"folderId":"example_folderId","status":"example_status","importance":"example_importance","limit":1,"nextPageToken":"example_nextPageToken"}' --json

`wrike.wrike_add_comment`

Add a comment to a Wrike task.

Write write

Parameters: task_id, text

Generic call

kosmo integrations:call wrike.wrike_add_comment '{"task_id":"example_task_id","text":"example_text"}' --json

Shortcut

kosmo integrations:wrike wrike_add_comment '{"task_id":"example_task_id","text":"example_text"}' --json

`wrike.wrike_get_project`

Get detailed information about a Wrike project.

Read read

Parameters: id

Generic call

kosmo integrations:call wrike.wrike_get_project '{"id":"example_id"}' --json

Shortcut

kosmo integrations:wrike wrike_get_project '{"id":"example_id"}' --json

`wrike.wrike_list_projects`

List projects in Wrike with optional filters.

Read read

Parameters: status, limit, nextPageToken

Generic call

kosmo integrations:call wrike.wrike_list_projects '{"status":"example_status","limit":1,"nextPageToken":"example_nextPageToken"}' --json

Shortcut

kosmo integrations:wrike wrike_list_projects '{"status":"example_status","limit":1,"nextPageToken":"example_nextPageToken"}' --json

`wrike.wrike_create_folder`

Create a new folder in Wrike.

Write write

Parameters: title, parent_id, description

Generic call

kosmo integrations:call wrike.wrike_create_folder '{"title":"example_title","parent_id":"example_parent_id","description":"example_description"}' --json

Shortcut

kosmo integrations:wrike wrike_create_folder '{"title":"example_title","parent_id":"example_parent_id","description":"example_description"}' --json

`wrike.wrike_get_folder`

Get detailed information about a Wrike folder.

Read read

Parameters: folder_id

Generic call

kosmo integrations:call wrike.wrike_get_folder '{"folder_id":"example_folder_id"}' --json

Shortcut

kosmo integrations:wrike wrike_get_folder '{"folder_id":"example_folder_id"}' --json

`wrike.wrike_list_folders`

List folders in Wrike with optional filters.

Read read

Parameters: limit, nextPageToken

Generic call

kosmo integrations:call wrike.wrike_list_folders '{"limit":1,"nextPageToken":"example_nextPageToken"}' --json

Shortcut

kosmo integrations:wrike wrike_list_folders '{"limit":1,"nextPageToken":"example_nextPageToken"}' --json

`wrike.wrike_get_space`

Get detailed information about a Wrike space.

Read read

Parameters: space_id

Generic call

kosmo integrations:call wrike.wrike_get_space '{"space_id":"example_space_id"}' --json

Shortcut

kosmo integrations:wrike wrike_get_space '{"space_id":"example_space_id"}' --json

`wrike.wrike_list_spaces`

List spaces in Wrike.

Read read

Parameters: limit

Generic call

kosmo integrations:call wrike.wrike_list_spaces '{"limit":1}' --json

Shortcut

kosmo integrations:wrike wrike_list_spaces '{"limit":1}' --json

`wrike.wrike_list_contacts`

List contacts in Wrike.

Read read

Parameters: limit

Generic call

kosmo integrations:call wrike.wrike_list_contacts '{"limit":1}' --json

Shortcut

kosmo integrations:wrike wrike_list_contacts '{"limit":1}' --json

`wrike.wrike_get_current_user`

Get the currently authenticated Wrike user.

Read read

Parameters: none

Generic call

kosmo integrations:call wrike.wrike_get_current_user '{}' --json

Shortcut

kosmo integrations:wrike wrike_get_current_user '{}' --json

Function Schemas

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

wrike.wrike_create_task 7 parameters

Schema command

kosmo integrations:schema wrike.wrike_create_task --json

Parameter	Type	Required	Description
`folderId`	string	yes	Folder ID to create the task in.
`title`	string	yes	Title of the task.
`description`	string	no	Detailed description of the task.
`importance`	string	no	Task importance (High, Normal, Low).
`status`	string	no	Task status (Active, Completed, Deferred).
`dates`	object	no	Date settings object (start, due, type).
`assignees`	array	no	Array of user IDs to assign the task to.

wrike.wrike_get_task 1 parameters

Schema command

kosmo integrations:schema wrike.wrike_get_task --json

Parameter	Type	Required	Description
`id`	string	yes	The task ID.

wrike.wrike_update_task 6 parameters

Schema command

kosmo integrations:schema wrike.wrike_update_task --json

Parameter	Type	Required	Description
`task_id`	string	yes	The task ID to update.
`title`	string	no	New title for the task.
`description`	string	no	New description for the task.
`status`	string	no	New status (e.g. Active, Completed, Deferred).
`importance`	string	no	Task importance: High, Normal, or Low.
`dates_due`	string	no	New due date in YYYY-MM-DD format.

wrike.wrike_list_tasks 5 parameters

Schema command

kosmo integrations:schema wrike.wrike_list_tasks --json

Parameter	Type	Required	Description
`folderId`	string	no	Folder ID to list tasks from.
`status`	string	no	Filter by status (e.g. Active, Completed, Deferred).
`importance`	string	no	Filter by importance (e.g. High, Normal, Low).
`limit`	integer	no	Max number of tasks to return.
`nextPageToken`	string	no	Cursor for pagination from a previous response.

wrike.wrike_add_comment 2 parameters

Schema command

kosmo integrations:schema wrike.wrike_add_comment --json

Parameter	Type	Required	Description
`task_id`	string	yes	ID of the task to comment on.
`text`	string	yes	Comment text (supports Markdown).

wrike.wrike_get_project 1 parameters

Schema command

kosmo integrations:schema wrike.wrike_get_project --json

Parameter	Type	Required	Description
`id`	string	yes	The project ID.

wrike.wrike_list_projects 3 parameters

Schema command

kosmo integrations:schema wrike.wrike_list_projects --json

Parameter	Type	Required	Description
`status`	string	no	Filter by project status (Active, Completed, Deferred).
`limit`	integer	no	Max number of projects to return.
`nextPageToken`	string	no	Cursor for pagination from a previous response.

wrike.wrike_create_folder 3 parameters

Schema command

kosmo integrations:schema wrike.wrike_create_folder --json

Parameter	Type	Required	Description
`title`	string	yes	Title of the folder.
`parent_id`	string	no	Parent folder or space ID to nest the folder under.
`description`	string	no	Description of the folder.

wrike.wrike_get_folder 1 parameters

Schema command

kosmo integrations:schema wrike.wrike_get_folder --json

Parameter	Type	Required	Description
`folder_id`	string	yes	The folder ID.

wrike.wrike_list_folders 2 parameters

Schema command

kosmo integrations:schema wrike.wrike_list_folders --json

Parameter	Type	Required	Description
`limit`	integer	no	Max number of folders to return.
`nextPageToken`	string	no	Cursor for pagination from a previous response.

wrike.wrike_get_space 1 parameters

Schema command

kosmo integrations:schema wrike.wrike_get_space --json

Parameter	Type	Required	Description
`space_id`	string	yes	The space ID.

wrike.wrike_list_spaces 1 parameters

Schema command

kosmo integrations:schema wrike.wrike_list_spaces --json

Parameter	Type	Required	Description
`limit`	integer	no	Max number of spaces to return.

wrike.wrike_list_contacts 1 parameters

Schema command

kosmo integrations:schema wrike.wrike_list_contacts --json

Parameter	Type	Required	Description
`limit`	integer	no	Max number of contacts to return.

wrike.wrike_get_current_user 0 parameters

Schema command

kosmo integrations:schema wrike.wrike_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.