Wrike

Wrike integration connects your agents to tasks, projects, folders, spaces, contacts, and approvals in your Wrike account.

Server URL: https://mcp.wrike.com/app/mcp/stream

Setup

Navigate to Resources and click Add Resource
Select Wrike from the catalog
Provide your Wrike OAuth app credentials (see Bring your own app)
Click Add

Each user connects their own Wrike account via OAuth when they first use a Wrike tool. Sign-in goes through your SSO when configured, and Wrike role-based access controls what each user can reach. Navigate to Connections to manage linked accounts.

Credential modes

Wrike supports one mode:

Bring your own app: a Wrike OAuth app owned by your organization, registered in the Wrike App Console. Wrike does not support dynamic client registration.

See Credential modes for the full comparison.

Bring your own app

A Wrike administrator registers an OAuth app in the Wrike App Console, then returns to SecureAuth with the Client ID and Client Secret.

In your AI Security workspace, go to Resources → Add Resource → Wrike → Bring your own app and copy the redirect URI shown in the dialog.

In the Wrike App Console, open the API section:

Click + App and enter an app name (for example, <your-company> AI Gateway)
Under Redirect URLs, add the redirect URI you copied; it must use HTTPS
Copy the Client ID and Client Secret

Paste both back into the Wrike resource dialog in your AI Security workspace, then click Add.

Wrike stores account data in regional data centers. The connection works the same way in every region; users on EU-hosted accounts (app-eu.wrike.com) confirm they sign in to their own Wrike region during authorization.

Available tools

Tool	Description
`wrike_get_tasks`	Get complete information about one or more tasks by exact IDs
`wrike_search_tasks`	Search tasks with filters across the whole account, a folder, a project, or a space
`wrike_create_task`	Create a Wrike task in a folder
`wrike_update_task`	Update a Wrike task by exact ID
`wrike_batch_update_tasks`	Update up to 100 Wrike tasks at once, including custom fields, assignments, and subtask relationships
`wrike_get_task_comments`	Get task comments by exact task ID
`wrike_get_folder_project`	Get complete information about one or more folders or projects by exact IDs
`wrike_search_folder_project`	Search folders and projects with filtering and response shaping
`wrike_create_folder_project`	Create a folder or project
`wrike_update_folder_project`	Update a project or folder
`wrike_get_spaces`	Get the available spaces
`wrike_get_contacts`	Get contacts from Wrike
`wrike_get_my_contact_id`	Get the current user's contact ID
`wrike_get_approvals`	Get approvals by filter
`wrike_get_custom_fields`	Get complete information about custom fields
`wrike_search_custom_types`	Search custom item types with filters
`wrike_get_workflows`	Get workflows with custom statuses
`wrike_convert_numeric_id`	Convert a numeric ID to a Wrike ID

Required scopes

Default: full user-level API access, bounded by each user's Wrike role

Wrike write access is controlled with gateway policies rather than narrower OAuth scopes; see the examples below.

Policy examples

Read-only access: deny wrike_create_task, wrike_update_task, wrike_batch_update_tasks, wrike_create_folder_project, and wrike_update_folder_project
Task work without account metadata: allow wrike_search_tasks, wrike_get_tasks, and wrike_get_task_comments, deny wrike_get_contacts
Block bulk changes: deny wrike_batch_update_tasks