Full read-write Claude connector for Wrike
Make Claude create tasks and keep projects current in Wrike
Stop clicking through folders to log work and update status by hand. Claude creates tasks in the right folder, sets assignees and due dates, updates fields, and moves work across the workflow where your projects already live, with deletes gated behind your approval.
Wrike is a work management platform where teams plan projects and track tasks across folders, boards, and Gantt timelines. People want Claude to do more than read status: to create and update tasks, move work forward, and keep projects current on their behalf.
What is a Wrike MCP server?
A Wrike MCP server is a small hosted service that exposes Wrike's data and actions to Claude over the Model Context Protocol, so Claude can tasks, projects, and docs inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can Wrike's current connector do today?
Wrike ships an official MCP connector for Claude, and it covers a standard tool set: look up tasks and folders, create tasks, and make common updates. It works well for general use. A custom Wrike connector goes further, with fuller coverage of custom fields, workflows, and comments plus scoped, human-in-the-loop controls shaped to how your team actually runs projects.
What does full read-write Wrike access unlock?
Full read-write Wrike access lets Claude create tasks in the right folder, set assignees and due dates, update custom fields and status, move tasks across the workflow, and post comments. The planning and status upkeep that used to mean clicking through the workspace happens where the work already lives, once you approve.
- Create a task in a chosen folder or project with an assignee, due date, and description
- Update task fields like status, priority, or custom fields from a discussion
- Move a task across the workflow as it progresses
- Add a comment or follow-up to a task to capture context
- Set or change the assignee and due dates on existing tasks
- Create subtasks to break a larger task into tracked steps
Can Claude create tasks in Wrike?
Yes. With a full read-write Wrike connector, Claude can create a task in the right folder or project, set the assignee, due date, and description, and break it into subtasks. It creates work where it belongs in your workspace, rather than only looking up tasks that already exist.
Can Claude update task status and fields in Wrike?
Claude can update task status, priority, and custom fields, move a task across the workflow as it progresses, change assignees and due dates, and post a comment to capture context. The status upkeep that meant clicking through the workspace happens in Wrike directly, once you approve the changes.
Will Claude delete or reassign Wrike tasks without my approval?
No. Destructive actions like deleting a task are gated and wait for your confirmation before they run. Routine writes such as creating a task or updating a field can flow directly, and the connector inherits your own permissions, so it never touches folders or tasks you cannot already access.
How a Wrike connector works
We build a small MCP server that authenticates to Wrike with OAuth and the narrowest scopes the work needs. Read tools (search, look up tasks and folders) and write tools (create, update, comment) are separated, and destructive actions like deleting a task require your confirmation. Claude only ever has the access your own Wrike account already has.
Frequently asked questions
Can Claude create and update Wrike tasks, not just read them?
Will Claude delete or reassign Wrike tasks without my approval?
Does the Wrike connector get more access than I have?
Related connectors
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.