---
updatedAt: 2026-11-13T18:35:52.000Z
agentTools:
  projectIndex: https://developers.wrike.com/llms.txt
---

# Available tools on Wrike MCP

# Available tools on Wrike MCP

The Wrike MCP server gives AI assistants a focused, dependable set of tools for working with your Wrike workspace. Rather than one flat catalog, the tools map to the **shape of the work** an assistant actually does: it *orients* itself, *finds* the right items, *reads* the detail, then *creates*, *staffs*, *acts*, and *governs*.

<Callout icon="📘" theme="info">
  ### **How to read this page**

  Each tool is marked **Read** (only retrieves information) or **Write** (creates or changes items). Assistants chain several tools to complete a request — for example, _find_ an item, _read_ its detail, then _comment_ on it.
</Callout>

<Callout icon="📘" theme="info">
  ### Tool availability

  Your client's discovered tool list is authoritative for your connection. Connector versions and administrator controls can affect which tools are exposed. Entries marked connector-dependent should only be used when present in that list. If tools are missing, refresh or reconnect the connector and check with your administrator.
</Callout>

## The map — seven stages of work

| Stage                        | Focus                                 | What it covers                                                                                                                                                                                                                  | Tools                                                                                                                                                                                                      |
| :--------------------------- | :------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **1 · Orient**               | Cold start & navigation               | Get your bearings and see what needs attention                                                                                                                                                                                  | `search_spaces`, `get_items_children`, `get_my_inbox`                                                                                                                                                      |
| **2 · Find**                 | Search & discovery                    | Locate the right work items and people                                                                                                                                                                                          | `search_items`, `search_users`, `get_users`                                                                                                                                                                |
| **3 · Understand**           | Read the detail                       | Inspect fields, attachments, and conversation history                                                                                                                                                                           | `get_item_details`, `get_item_comments`, `get_item_history`                                                                                                                                                |
| **4 · Intake**               | Turn user inputs into structured work | Create tasks, folders, and projects. Find the right request form, read its fields, and file a request; Find matching blueprints, launch pre-built work from a blueprint                                                         | `search_requestforms`, `get_requestform`, `submit_requestform`, `prefill_requestform`, `search_blueprints`, `create_item_from_blueprint`, `get_asyncjob`, `create_task_item`, `create_project_folder_item` |
| **5 · Staff&#x20;**          | Resource Allocation                   | Get a proposed assignee for every task in a project, folder or set of tasks, based on availability, skills and [task requirements](https://help.wrike.com/hc/en-us/articles/24985720076567-Assignee-Requirements-in-Work-Items) | `recommend_resources`                                                                                                                                                                                      |
| **6 · Act & follow through** | Update & collaborate                  | Edit items in bulk, add attachments and post comments                                                                                                                                                                           | `update_items`, `create_item_comment`, `prepare_attachment`, `add_attachments_to_item`, `remove_attachment_from_item`                                                                                      |
| **7 · Configure & govern**   | Metadata & approvals                  | Work with workflows, custom fields, item types, and approvals                                                                                                                                                                   | `search_workflows`, `search_customitemtypes`, `search_item_customfields`, `get_approvals`, `search_approvals`                                                                                              |

<br />

## 🧭 Orient — cold start & navigation

Get your bearings: which spaces exist, what's inside them, and what needs your attention.

| Tool                 | Type | What you can do                                                                               |
| :------------------- | :--- | :-------------------------------------------------------------------------------------------- |
| `search_spaces`      | Read | List the spaces you belong to, or filter them by name.                                        |
| `get_items_children` | Read | Walk the hierarchy one level at a time — drill from a space into folders, projects and tasks. |
| `get_my_inbox`       | Read | Catch up on unread notifications: mentions, assignments, status changes and replies.          |

<Callout icon="🧭" theme="default">
  ### **Try asking**

  “What’s in my inbox that needs action today, and which project does each item belong to?”
</Callout>

<br />

## 🔎 Find — search & discovery

Locate the exact work and people you need, with natural-language search and precise filters.

| Tool           | Type | What you can do                                                                                                                                                                                                                                    |
| :------------- | :--- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `search_items` | Read | Search tasks, folders and projects by keyword; filter by assignee, status, dates and custom fields; scope to a space or subtree. There is no importance parameter: use get\_item\_details on matches and filter their importance values afterward. |
| `search_users` | Read | Find people or groups by name — or, with no query, surface your top collaborators.                                                                                                                                                                 |
| `get_users`    | Read | Look up specific users by id or email, or resolve “me”.                                                                                                                                                                                            |

<Callout icon="🔎" theme="default">
  ### **Try asking**

  “Find the active tasks assigned to me in the Marketing space that are due this week.”
</Callout>

<br />

## 📖 Understand — read the detail

Go deep on the items that matter: their fields, people, attachments and conversations.

| Tool                | Type | What you can do                                                                                                                                                                                                  |
| :------------------ | :--- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `get_item_details`  | Read | Read up to five items at once: status, custom fields, assignees and attachments, including linked external files. Descriptions default to a 500-character preview; pass fullDescriptions=true for the full text. |
| `get_item_comments` | Read | Read comments with authors and timestamps, up to 200 comments per response. Check truncated; pass a top-level commentId as rootCommentId to read its thread separately.                                          |
| `get_item_history`  | Read | Read field-change history with timestamps, authors and typed changes. Choose requestedChanges and a date range; follow nextPageToken while truncated is true.                                                    |

<Callout icon="📖" theme="default">
  ### **Try asking**

  “Summarise the comment thread on this task into decisions, open questions and owners.”
</Callout>

<br />

## 🏗️ Intake — turn user inputs into structured work

Convert meeting notes, briefs and conversations into structured, assigned, scheduled work.

| Tool                         | Type  | What you can do                                                                                                                                                                                                               |
| :--------------------------- | :---- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `create_task_item`           | Write | Create one or many tasks; set assignee, dates, duration and status; nest them as subtasks.                                                                                                                                    |
| `create_project_folder_item` | Write | Create folders, projects and project-based custom item types. Set project owners and status; folders support neither. Set project dates afterward through update\_items.                                                      |
| `search_blueprints`          | Read  | Find reusable Wrike blueprints                                                                                                                                                                                                |
| `create_item_from_blueprint` | Write | Create a new task, folder, project, custom item, or item tree from an existing Wrike blueprint.                                                                                                                               |
| `search_requestforms`        | Read  | Query available Wrike request forms                                                                                                                                                                                           |
| `get_requestform`            | Read  | Retrieve the pages, fields, options, and rules of an existing Wrike request form                                                                                                                                              |
| `prefill_requestform`        | Read  | Connector-dependent: when exposed, generate a URL with prefilled request-form values without submitting it. If absent, use get\_requestform to collect answers and submit\_requestform to create the work.                    |
| `submit_requestform`         | Write | Submits a Wrike request form and creates the task or project configured by that form.                                                                                                                                         |
| `get_asyncjob`               | Read  | Read an async job by jobId. Poll about every five seconds while IN\_QUEUE or IN\_PROGRESS; stop on COMPLETED or FAILED. Report errorMessage on failure; do not resubmit the original creation request while it is processing. |

<Callout icon="🏗️" theme="default">
  ### **Try asking**

  “I want to run a new {website project}, here is my {brief}. Help me create it in Wrike.”
</Callout>

<br />

## 👥 Staff — intelligent resource allocation&#x20;

Decide who does the work. Your assistant proposes an assignee for every task, explains each pick, and applies them only after you approve.

| Tool                  | Type | What you can do                                                                                                                                                                                                     |
| :-------------------- | :--- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `recommend_resources` | Read | Propose assignees for tasks based on availability, workload, skills and job roles; compare staffing options and see explanations, workload impact and unfilled assignments. Does not assign people or change tasks. |

**Before you start**

* **Availability:** Pinnacle and Apex plans.&#x20;
* **MCP v2 only:** Server URL `https://mcp.wrike.com/v2`. Refresh or reconnect your connector so the tool appears (see the [refresh table in the overview](https://developers.wrike.com/docs/wrike-mcp-server-overview)).
* **Your data:** Recommendations are only as good as what's in the workspace. Tasks need effort estimates and dates, and people need their work schedules set up. Matching on [job roles](https://help.wrike.com/hc/en-us/articles/1500005128221-Assigning-and-Unassigning-Tasks-From-Job-Roles) and [skill and other requirements](https://help.wrike.com/hc/en-us/articles/23711685828759-Custom-Fields-in-User-Profiles-in-Wrike) only applies to tasks assigned to job roles or where [task requirements](https://help.wrike.com/hc/en-us/articles/24985720076567-Assignee-Requirements-in-Work-Items) are filled in.
* **Connector request limits:** Follow the current tool description. It specifies up to 150 explicit task IDs and 30 explicit user or group IDs. If the tool reports that the task scope or candidate pool is too large, ask the user to narrow it. These input limits are distinct from counts of proposed assignment slots.
* **Optional skills:** show results as a <Anchor target="_blank" href="https://github.com/wrike/agent-skills/tree/main/skills">dashboard in chat or a staffing board in Klaxoon</Anchor>.

<Callout icon="👥" theme="default">
  ### **Try asking**

  “Recommend assignees for the tasks in {project}, but only from the {group name} group.”
</Callout>

<br />

## ✅ Act & follow through — update & collaborate

Move work forward: update items in bulk and keep the conversation going.

| Tool                          | Type  | What you can do                                                                                                                                                                                                                                            |
| :---------------------------- | :---- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `update_items`                | Write | Edit title, description, status, dates and custom fields; add or remove assignees and parents; convert an item's type; apply the same change to up to 20 items at once.                                                                                    |
| `create_item_comment`         | Write | Post a comment on any task, folder or project and @-mention teammates.                                                                                                                                                                                     |
| `prepare_attachment`          | Write | Prepare an attachment object for a file, cloud-storage file, DAM asset, web link or whiteboard. Returns an attachmentId; it does not attach anything to an item. FILE returns PENDING\_UPLOAD with a signed PUT URL and headers. Other types return READY. |
| `add_attachments_to_item`     | Write | Bind 1–10 prepared attachment IDs to an existing work item. FILE attachments must already be uploaded; READY attachments can be bound directly. Only use IDs that have not already been added to an item.                                                  |
| `remove_attachment_from_item` | Write | Remove an attachment and every version using its itemId and attachmentId from get\_item\_details. Wrike files are deleted; links, cloud files and DAM assets are unlinked without deleting the external content.                                           |
| `add_whiteboard_to_item`      | Write | Connector-dependent: use only when exposed. With the general attachment tools, prepare type WHITEBOARD with a board URL or whiteboardUUID, then bind the returned attachmentId with add\_attachments\_to\_item.                                            |
| `remove_whiteboard_from_item` | Write | Connector-dependent: use only when exposed. With the general attachment tools, find the board attachment through get\_item\_details and unlink it using remove\_attachment\_from\_item.                                                                    |

### Attachment workflow

1. Call `prepare_attachment` with an `attachment` object matching the source type.
2. For `FILE`, PUT the raw file bytes to `upload.url` before `upload.expiresAt`, using every header in `upload.headers`, including the returned Content-Type. Do not send multipart form data, JSON or Base64. If the PUT outcome is unknown, retry the same upload URL rather than preparing another attachment.
3. For `READY`, no byte upload is needed. Pass `attachmentId` directly to `add_attachments_to_item`, a comment's `attachmentIds`, or a request-form attachment field. For `FILE`, do this after the upload succeeds.

For whiteboards, use `attachment: {type: "WHITEBOARD", url: "..."}` or `attachment: {type: "WHITEBOARD", whiteboardUUID: "..."}`; provide exactly one of the URL or UUID.

<Callout icon="✅" theme="okay">
  ### **Try asking**

  “Mark these three tasks complete and leave a comment tagging the owner for review.”
</Callout>

<br />

## ⚙️ Configure & govern — metadata & approvals

Understand the workspace's structure and stay on top of sign-offs.

| Tool                       | Type | What you can do                                                                                    |
| :------------------------- | :--- | :------------------------------------------------------------------------------------------------- |
| `search_workflows`         | Read | Find workflows and their custom statuses, including the status ids needed to set or filter status. |
| `search_customitemtypes`   | Read | Find a custom item type and its id, ranked by how often it's used.                                 |
| `search_item_customfields` | Read | Find custom fields by name, with their type and any select-list options.                           |
| `get_approvals`            | Read | Look up approvals by id, or list the approvals on a given item — status, approvers and decisions.  |
| `search_approvals`         | Read | Filter across approvals by status, approver and due date.                                          |

<Callout icon="⚙️" theme="default">
  ### **Try asking**

  “Which approvals are still waiting on me, and how long have they been pending?”
</Callout>

<br />

<Callout icon="🧭" theme="default">
  ### **See these tools in action**

  For end-to-end scenarios that chain these tools together — meeting-to-work, daily inbox review, weekly status reports, client QBRs and more — see [Typical Use Cases of Wrike MCP](https://developers.wrike.com/docs/typical-use-cases-of-wrike-mcp). To connect a client, start from the [Wrike MCP Server Overview](https://developers.wrike.com/docs/wrike-mcp-server-overview).
</Callout>