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 MCP Integration for Generic MCP Clients

Connect Wrike to Generic MCP Clients through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

14 functions 10 read 4 write Bearer token auth

Submit Wrike feedback View package source

Connect Wrike to Generic MCP Clients

Connect any stdio-compatible MCP client to local KosmoKrator integration tools.

Register kosmo mcp:serve as the command for a local stdio MCP server. The gateway is local, scoped to this integration, and starts with --write=deny so MCP clients can inspect read-capable tools without receiving write access by default.

Wrike MCP Config for Generic MCP Clients

Start with read-only write policy and expand only for trusted projects.

{
  "mcpServers": {
    "kosmokrator-wrike": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=wrike",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=wrike --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Wrike instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Wrike Tools Visible to MCP clients

MCP clients sees stable MCP tool names generated from the Wrike integration catalog.

MCP tool	Source function	Type	Description
`integration__wrike__wrike_create_task`	`wrike.wrike_create_task`	Write	Create a new task in Wrike.
`integration__wrike__wrike_get_task`	`wrike.wrike_get_task`	Read	Get detailed information about a Wrike task.
`integration__wrike__wrike_update_task`	`wrike.wrike_update_task`	Write	Update an existing Wrike task.
`integration__wrike__wrike_list_tasks`	`wrike.wrike_list_tasks`	Read	List tasks in Wrike with optional filters.
`integration__wrike__wrike_add_comment`	`wrike.wrike_add_comment`	Write	Add a comment to a Wrike task.
`integration__wrike__wrike_get_project`	`wrike.wrike_get_project`	Read	Get detailed information about a Wrike project.
`integration__wrike__wrike_list_projects`	`wrike.wrike_list_projects`	Read	List projects in Wrike with optional filters.
`integration__wrike__wrike_create_folder`	`wrike.wrike_create_folder`	Write	Create a new folder in Wrike.
`integration__wrike__wrike_get_folder`	`wrike.wrike_get_folder`	Read	Get detailed information about a Wrike folder.
`integration__wrike__wrike_list_folders`	`wrike.wrike_list_folders`	Read	List folders in Wrike with optional filters.
`integration__wrike__wrike_get_space`	`wrike.wrike_get_space`	Read	Get detailed information about a Wrike space.
`integration__wrike__wrike_list_spaces`	`wrike.wrike_list_spaces`	Read	List spaces in Wrike.
`integration__wrike__wrike_list_contacts`	`wrike.wrike_list_contacts`	Read	List contacts in Wrike.
`integration__wrike__wrike_get_current_user`	`wrike.wrike_get_current_user`	Read	Get the currently authenticated Wrike user.

Related Wrike Pages

Wrike CLIUse direct JSON commands instead of MCP discovery. Wrike MCPFull gateway reference and MCP tool names. KosmoKrator for MCP clientsClient-level gateway setup.