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.
How to read this pageEach 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.
Tool availabilityYour 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.
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 | Resource Allocation | Get a proposed assignee for every task in a project, folder or set of tasks, based on availability, skills and task requirements | 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, create_approval, update_approval, set_approval_decision |
🧭 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. |
🔎 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”. |
📖 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. |
🏗️ 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. |
👥 Staff — intelligent resource allocation
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.
- 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). - 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 and skill and other requirements only applies to tasks assigned to job roles or where task requirements 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 dashboard in chat or a staffing board in Klaxoon.
✅ 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
- Call
prepare_attachmentwith anattachmentobject matching the source type. - For
FILE, PUT the raw file bytes toupload.urlbeforeupload.expiresAt, using every header inupload.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. - For
READY, no byte upload is needed. PassattachmentIddirectly toadd_attachments_to_item, a comment'sattachmentIds, or a request-form attachment field. ForFILE, 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.
⚙️ Configure & govern — metadata & approvals
Understand the workspace's structure, manage approval requests, and make your own review decisions.
| 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 approvalIds, including their status, reviewers and decisions. To find approvals on an item, use search_approvals with itemId. |
search_approvals | Read | Filter approvals by status, reviewer and dates, or scope to approvals directly on one item with itemId. Page through matches with pageSize and nextPageToken; itemId does not recurse into children. |
create_approval | Write | Create an approval on a task, folder or project, choose reviewers and the attachments to review, and configure the decision strategy and automatic completion. |
update_approval | Write | Edit an approval with action EDIT and nonempty changes, cancel it with CANCEL, or finish a decided approval with FINISH. CANCEL and FINISH do not accept edit changes; FINISH does not cast a decision. |
set_approval_decision | Write | Approve, reject or reset your own decision on an existing approval with APPROVE, REJECT or RESET. You must be an assigned approver. A decision may automatically finish the approval and trigger configured follow-up actions. |
Approval workflow and limits
- Find and inspect: Use
search_approvalsto find an approval, thenget_approvalswith itsapprovalIdsto inspect it. The updated get contract accepts approval IDs only; item lookup belongs in search. For search pagination, follownextPageTokenwhiletruncatedis true. When a token is supplied, it drives the next page and other filters are ignored. - Response values: Approval enums use uppercase values such as
PENDING,APPROVED,FILES_ONLYandREGULAR. Read each tool's discovered schema for the values accepted by its filters and actions. - Your decision:
set_approval_decisionacts as the authenticated user, who must be an assigned reviewer. It does not make a decision on another reviewer's behalf. A decision cannot be reset after the approval has finished. - Decision versus completion: With automatic completion enabled, a decision can finish the approval and trigger configured follow-up actions. If automatic completion is disabled, an approval can have a decided outcome with
finished=false; useupdate_approvalwithFINISHto close it when permitted. Finishing applies the outcome without casting a new decision. - Decision strategy:
FIRST_DECISION_WINSuses the first reviewer's decision.WAIT_ALL_WITH_VETOwaits for every reviewer to decide, then produces a rejected outcome if any reviewer rejected. The automatic-completion settings control whether the decided approval is also finished. - Files chosen for review: An approval's
attachmentIdsare an explicit subset of the item's attachments. Adding a file to the item does not add it to an existing approval; useupdate_approvalwithaddAttachmentIdsseparately. AFILES_ONLYapproval needs files added to the approval itself before it can leave Draft. Per-file review decisions are not supported by the current MCP tools; use Wrike's review UI for those decisions. - Connector availability: The updated approval tools may reach clients at different times. Refresh or reconnect and check administrator action controls if mutation tools are missing or the read tools still expose the older contract. Use the parameters actually discovered by your client.
Try asking“Which approvals are still waiting on me, and how long have they been pending?”
“Approve the campaign approval on {task} as me.”
“Reject the approval on {task} with feedback that the pricing needs correction.”
“Reset my decision on this approval so I can review the updated material.”
See these tools in actionFor 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. To connect a client, start from the Wrike MCP Server Overview.
Updated 2 days ago