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

Use the Wrike CLI for coding agents with headless JSON commands, schema discovery, credentials, and permission controls.

14 functions 10 read 4 write Bearer token auth

Submit Wrike feedback View package source

Wrike CLI for Coding Agents

Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

Use this pattern when another coding agent needs exact commands and schema discovery. The Wrike CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Wrike CLI for Coding Agents
kosmokrator integrations:configure wrike --set access_token="$WRIKE_ACCESS_TOKEN" --enable --read allow --write ask --json
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

Discovery Before Execution

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

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

Useful Wrike CLI Functions

Function	Type	Parameters	Description
`wrike.wrike_create_task`	Write	folderId, title, description, importance, status, dates, assignees	Create a new task in Wrike.
`wrike.wrike_get_task`	Read	id	Get detailed information about a Wrike task.
`wrike.wrike_update_task`	Write	task_id, title, description, status, importance, dates_due	Update an existing Wrike task.
`wrike.wrike_list_tasks`	Read	folderId, status, importance, limit, nextPageToken	List tasks in Wrike with optional filters.
`wrike.wrike_add_comment`	Write	task_id, text	Add a comment to a Wrike task.
`wrike.wrike_get_project`	Read	id	Get detailed information about a Wrike project.
`wrike.wrike_list_projects`	Read	status, limit, nextPageToken	List projects in Wrike with optional filters.
`wrike.wrike_create_folder`	Write	title, parent_id, description	Create a new folder in Wrike.
`wrike.wrike_get_folder`	Read	folder_id	Get detailed information about a Wrike folder.
`wrike.wrike_list_folders`	Read	limit, nextPageToken	List folders in Wrike with optional filters.
`wrike.wrike_get_space`	Read	space_id	Get detailed information about a Wrike space.
`wrike.wrike_list_spaces`	Read	limit	List spaces in Wrike.
`wrike.wrike_list_contacts`	Read	limit	List contacts in Wrike.
`wrike.wrike_get_current_user`	Read	none	Get the currently authenticated Wrike user.

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

CI Wrike CLI for CI. Cron Jobs Wrike CLI for cron jobs. Shell Scripts Wrike CLI for shell scripts. Headless Automation Wrike CLI for headless automation.