productivityoauth2

Wrike

Wrike is a project management and collaboration tool offering customizable workflows, Gantt charts, reporting, and resource management to boost team productivity

Verdict

The Wrike MCP lets your team manage projects, tasks, and folders directly from Switchy by @mentioning it in any Space. You can create tasks in specific folders, invite users to workspaces, modify group memberships in bulk, and delete custom fields or entire folders without switching apps. Project managers and ops leads get the most value — they can triage incoming work, update task priorities, and reorganize folder structures while discussing them in chat. Setup requires OAuth with read/write access to your Wrike workspace, and destructive operations (deleting folders, custom fields) are permanent with no undo.

Common use cases

  • Create tasks from Slack threads without context switching
  • Bulk update team assignments across multiple groups
  • Invite contractors to project workspaces mid-conversation
  • Archive completed project folders during retrospectives
  • Adjust task priorities based on standup discussions

Integration

Vendor
Wrike
Category
productivity
Auth
OAUTH2
Tools
38
Composio slug
wrike

Tools

  • Bulk modify group members

    Adds or removes members for multiple wrike groups in a single request; all specified user ids must correspond to existing wrike users.

  • Create a folder

    Creates a new wrike subfolder within the specified `folderid`, optionally as a project if `customitemtypeid` is given; the folder is auto-shared with its creator.

  • Create a group

    Creates a new user group in wrike with a specified title, optionally setting members, parent group, avatar, and custom metadata.

  • Create invitation

    Invites a user to a wrike workspace by email, optionally with name, specifying either `usertypeid` or a combination of `role`/`external`; custom email subject/message available for paid accounts.

  • Create task in folder

    Creates a new task in a specified wrike folder; if setting priority with `prioritybefore` or `priorityafter`, the referenced task must be in the same folder or project.

  • Delete custom field by id
    destructive

    Permanently deletes a custom field by its id; this action is irreversible and requires a valid, existing custom field id.

  • Delete folder
    destructive

    Permanently deletes the folder specified by `folderid` and all its contents (e.g., tasks, documents, subfolders) from the wrike workspace; this irreversible action is for when the folder is no longer needed and has no active tasks or depend

  • Delete group by id
    destructive

    Permanently deletes a group by its `groupid`; this action is irreversible and does not affect user accounts that were members of the group.

  • Delete invitation
    destructive

    Permanently deletes an existing invitation, specified by its unique `invitationid`; this action cannot be undone.

  • Delete task
    destructive

    Permanently deletes a wrike task and all its associated data by its id; this action is irreversible and the task must exist.

  • Fetch all tasks

    Fetches tasks from a wrike account, allowing filtering by status, due date, and subfolder inclusion, with customizable response fields and pagination.

  • Get account information

    Retrieves detailed wrike account information, where the response content is influenced by selected fields, account subscription, and user permissions.

  • Get all custom fields

    Retrieves all custom field definitions (including id, name, type, and settings) from the wrike account; this returns the definitions themselves, not their specific values on wrike items, and is useful for obtaining custom field ids.

  • Get contacts

    Retrieves a list of wrike contacts (e.g., team members, clients, collaborators); response includes contact details but not their detailed task or project involvement.

  • Get folders

    Retrieves folders and/or projects from wrike, with filters; when using `nextpagetoken`, all other filter parameters must match the initial request.

  • Get group by id

    Retrieves detailed information for a specific wrike group using its `groupid`, optionally including 'metadata'.

  • Get specific contact information

    Retrieves detailed information for a specific wrike contact using their unique `contactid`, optionally including `metadata` and `customfields` if specified in the `fields` parameter.

  • Get specific user

    Retrieves detailed information about a specific user in wrike using their unique user id.

  • Get task by id

    Retrieves read-only detailed information for a specific wrike task by its unique id, optionally allowing specification of fields to include in the response.

  • Launch folder blueprint async

    Asynchronously launches a new project or folder structure in wrike from a specified folder blueprint, typically returning a task id to track progress.

  • Launch Task Blueprint Async

    Asynchronously launches a wrike task blueprint to create tasks/projects, requiring either `super task id` (parent task) or `parent id` (parent folder/project) for placement.

  • List Folder Blueprints

    Retrieves all account-level folder blueprints, which are templates for standardizing folder/project creation with predefined structures, custom fields, and workflows.

  • List space folder blueprints

    Lists all folder blueprints (templates for new folders/projects) within a specified wrike space, requiring a valid and accessible space id.

  • List space task blueprints

    Lists task blueprints (templates for creating tasks with consistent structures) available in a specific, accessible wrike space.

  • List subfolders by folder id

    Lists subfolders (metadata only, not their contents) for an existing wrike folder specified by `folderid`, supporting recursive descent, filtering, and pagination.

  • List Task Blueprints

    Retrieves a list of defined task blueprints (predefined task templates) from the wrike account, supporting pagination.

  • Modify folder attributes

    Modifies an existing wrike folder: updates title, description, parents (not root/recycle bin), sharing, metadata, custom fields/columns; restores, converts to project, or manages access roles.

  • Modify group

    Updates an existing wrike user group's attributes like title, members, parent, avatar, or metadata, using its `groupid` and specifying only the fields to change.

  • Modify task

    Modifies an existing wrike task by its id, allowing updates to attributes such as title, status, dates, assignees, and custom fields; `prioritybefore` and `priorityafter` are mutually exclusive, and parent folder ids for `addparents`/`remov

  • Query invitations

    Retrieves all active invitations in wrike, useful for viewing and auditing pending invitations or managing user onboarding.

  • Query workflows

    Fetches a list of all workflows with their detailed information from the wrike account; this is a read-only action and does not support pagination or filtering through its parameters.

  • Retrieve custom field by id

    Retrieves a wrike custom field's detailed information (e.g., type, possible values for dropdowns), properties, and metadata; the `customfieldid` must correspond to an existing custom field.

  • Retrieve list of groups

    Retrieves a list of user groups from the wrike account, supporting metadata filtering, pagination, and inclusion of specific fields; this is a read-only operation.

  • Update account metadata

    Updates or adds custom key-value metadata to the wrike account, useful for integrations, storing app-specific data, or mapping external system identifiers.

  • Update a specific user

    Updates specified profile attributes (e.g., account id, role, external status) for an existing wrike user; unspecified fields remain unchanged.

  • Update custom field by id

    Updates properties of an existing wrike custom field by its id, such as its title, type, scope, or sharing settings.

  • Update invitation

    Updates a pending wrike invitation (`invitationid`) to resend it or change user's role/type (use `usertypeid` over deprecated `role`/`external`).

  • Update metadata on a specific contact

    Updates metadata, job role, or custom fields for an existing wrike contact specified by `contactid`; if `jobroleid` is provided, it must be a valid id.

Setup

Setup guide

  1. 11. Open your Switchy workspace settings and navigate to the Integrations tab. 2. Search for Wrike in the MCP directory and click Connect. 3. You'll be redirected to Wrike's OAuth consent screen — sign in with an account that has admin or full access to your workspace. 4. Grant the requested permissions (read and write access to folders, tasks, groups, custom fields, and user invitations). 5. After authorizing, you'll return to Switchy where the connection status shows as active. 6. Open any Space and type '@Wrike create a task in folder' followed by a folder ID to test the connection. 7. If the task appears in your Wrike workspace within seconds, the integration is working. 8. To find folder IDs for future prompts, use '@Wrike list folders' or check the URL when viewing a folder in Wrike's web app.

What teammates see: by default, memories from Wrike are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Create Task from Discussion

@Wrike create a task in folder IEAAAAAQG4 titled 'Review Q2 budget proposal' with description 'Finance team flagged three line items needing clarification' and due date 2024-12-20
Open in a Space →

Invite External Reviewer

@Wrike create invitation for email consultant@example.com with name 'Alex Chen' as external collaborator with limited access role
Open in a Space →

Reorganize Project Structure

@Wrike create a folder named 'Design Assets - Phase 2' under parent folder IEAAAAAQH7 and mark it as a project
Open in a Space →

Bulk Update Team Access

@Wrike bulk modify group members for group KGAAAAAQ by adding user IDs KUAAAAAB, KUAAAAAC, KUAAAAAD to grant them access to the product roadmap
Open in a Space →

Clean Up Deprecated Fields

@Wrike delete custom field by id JUAAAAAQIEAAAAAQ since we've migrated sprint tracking to the new system and this field causes confusion
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@wrike show me all high-priority tasks in the Q1 Launch folder that are overdue or due this week

Output

Found 7 tasks in the Q1 Launch folder matching your criteria. High-priority overdue: 'Finalize pricing page copy' (due 3 days ago, assigned to Sarah), 'Security audit sign-off' (due yesterday, assigned to Mike). High-priority due this week: 'App Store screenshots' (due Thursday, assigned to Design team), 'Press release draft' (due Friday, unassigned), plus 3 others. All tasks are currently in 'In Progress' or 'Active' status. This is an illustrative example based on typical Wrike folder structures.

Notes

This read-heavy example demonstrates folder-scoped task filtering by priority and date range. Requires OAuth scope to read tasks and folder metadata. Wrike's API returns task objects with status, dates, and assignees — the MCP surfaces these in natural language. Useful for daily standups or sprint reviews.

Prompt

@wrike create a task called 'Update API documentation' in the Engineering folder, assign it to Jordan, and set the due date to next Friday

Output

Created task 'Update API documentation' (ID: IEAAAAAQKQABCDEF) in the Engineering folder. Assigned to Jordan Chen, due date set to Friday, January 17, 2025. The task is auto-shared with you as creator and inherits the folder's default workflow status ('New'). You can adjust priority, add subtasks, or attach files by mentioning this task ID in follow-up prompts. This is an illustrative example of a successful task creation.

Notes

This write example shows task creation with assignment and scheduling. Side-effect: the task now exists in your Wrike workspace and Jordan will receive a notification. Requires OAuth scope for task creation and user lookup. If Jordan's name is ambiguous or they lack folder access, the MCP will prompt for clarification.

Prompt

@wrike summarize all completed tasks in the Marketing folder from the last two weeks and draft a progress update for the team

Output

Reviewed 14 completed tasks in the Marketing folder (Jan 1–14, 2025). Key deliverables: 3 blog posts published, 2 email campaigns sent (open rates 24% and 31%), 1 webinar landing page launched, social media calendar finalized for Q1. Blockers resolved: vendor contract signed, design assets approved. Draft update: 'Strong two-week sprint — content pipeline is ahead of schedule, email engagement up 18% vs. December. Webinar registration opens Monday; let's push for 200 sign-ups by end of month.' This synthesis is illustrative, based on typical marketing task metadata.

Notes

This synthesis example pairs Wrike's task data with AI reasoning to generate a team update. The MCP fetches completed tasks by date range and folder, then the AI summarizes themes and drafts prose. Useful for weekly reports or stakeholder emails. Accuracy depends on task titles and descriptions being descriptive — vague task names yield vague summaries.

Use-case deep-dives

Agency client onboarding at scale

When Wrike's OAuth wins for repeatable client setups

A 12-person creative agency onboards 3-5 new clients per month, each needing a folder tree, custom fields for deliverable status, and a client-specific user group. Wrike's MCP is the right call here because the OAuth scope lets you script the entire setup—create folder, create group, bulk add members, set custom fields—without manual clicking through 38 steps per client. The "create invitation" tool even handles adding the client's PM to their workspace with a branded email. The threshold: if your onboarding checklist is under 10 steps or you onboard fewer than 2 clients per quarter, the OAuth dance isn't worth it; just use Wrike's UI. But at agency scale, this MCP turns a 45-minute manual process into a 90-second Switchy prompt. Worth the OAuth setup if you're onboarding more than once a month.

Sprint retrospective task cleanup

Bulk folder deletion for post-sprint hygiene

A 6-person dev team runs two-week sprints and creates a temporary Wrike folder for each sprint's ad-hoc tasks—bug triage, design feedback, deployment checklists. At retro, they want to archive completed work and delete the folder to keep the workspace clean. Wrike's MCP handles this cleanly: the "delete folder" tool nukes the folder and all nested tasks in one call, no manual recursion. The catch: this is irreversible, so you need a human in the loop to confirm the folder ID before deletion. If your team keeps sprint folders for historical reference, this scenario doesn't apply—Wrike's archive feature is better. But if you treat sprint folders as disposable scratch space, the MCP saves 10 minutes of click-delete-confirm per sprint. Best for teams running 20+ sprints per year who value a tidy workspace over historical breadcrumbs.

Customer support ticket routing

When Wrike's task creation beats a dedicated helpdesk

A 4-person B2B SaaS support team uses Wrike as their ticket system because their product roadmap already lives there. Incoming support emails trigger a Zapier webhook that hits Switchy, which uses the Wrike MCP to create a task in the "Support Inbox" folder, set priority relative to existing tickets, and assign it based on custom field rules (e.g., "Enterprise" customers go to the senior rep). This works because Wrike's 38 tools include priority ordering and custom field writes, so you can encode triage logic without leaving the MCP. The limit: if you're handling more than 50 tickets per week, Wrike's lack of SLA tracking and canned responses will hurt—switch to Zendesk. But for low-volume B2B support where context-switching to a separate tool is worse than missing helpdesk features, the Wrike MCP keeps tickets in the same workspace as your roadmap. Best for teams under 100 customers.

Frequently asked

What can the Wrike MCP do in Switchy?

The Wrike MCP lets your AI agents create tasks, folders, and projects, manage user groups, invite team members, and modify custom fields—all without leaving your Switchy workspace. It covers the full lifecycle of work management, from setting up folder hierarchies to bulk-editing group memberships. Think of it as giving your AI direct access to Wrike's project structure and user administration.

Do I need admin access to connect Wrike via OAuth?

You need sufficient permissions to authorize the OAuth scopes Wrike requests—typically workspace admin or owner rights. Regular users can't grant access to create groups, delete folders, or invite new members. If you're not an admin, ask your Wrike workspace owner to connect it in Switchy. The connection is workspace-wide, so one admin authorization covers the whole team.

Can the Wrike MCP delete tasks or just folders?

The MCP includes a tool to permanently delete folders and all their contents—tasks, documents, subfolders—in one irreversible action. There's no standalone delete-task tool in the representative set, but deleting the parent folder removes everything inside. For safer workflows, move tasks to an archive folder instead of deleting them outright.

How does this compare to using Wrike's API directly?

Wrike's API requires you to write code, manage OAuth tokens, and handle pagination and rate limits yourself. The MCP abstracts that into plain-English tool calls your AI can execute—no scripting, no token refresh logic. You lose some low-level control (like custom retry strategies), but you gain speed and simplicity for routine project management tasks.

Who on the team should connect the Wrike MCP?

Your Wrike workspace admin or owner should connect it, since many tools—creating groups, inviting users, deleting folders—require elevated permissions. Once connected, any Switchy team member can ask the AI to use Wrike tools within their permission scope. The connection doesn't count against Wrike seat limits; it's an OAuth app, not a user license.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.