Wrike MCP Server
Connect Wrike to your AI agents with the Wrike MCP server.
Updated
What is Wrike MCP?
The Wrike MCP server is a Model Context Protocol server that connects Wrike to AI agents and assistants as a set of tools. With it connected, an agent can work with Wrike (project management — tasks, folders, projects, and team workflows) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses a bearer token, so you point your client at the server URL, authorize once, and the Wrike tools become available to the model.
Connect the Wrike MCP server
Connect Wrike MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Wrike MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (a bearer token) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Wrike tool to confirm the connection is live.
Connect Wrike MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Wrike
Provide the Wrike MCP server URL or command and complete authentication.
- 3
Test
Reference Wrike from chat to confirm Cursor can reach the tools.
Sample use cases
Triage incoming tasks by urgency and assign to team members
The agent reads new tasks, classifies priority based on content and due dates, and routes them to the right assignee.
Generate a weekly sprint progress report from task data
The agent pulls completed, in-progress, and blocked tasks and formats a summary for stakeholders.
Create tasks from meeting notes or Slack messages
The agent parses action items and creates corresponding Wrike tasks with descriptions and due dates.
Track overdue tasks and nudge assignees
A scheduled agent checks for tasks past their due date and sends reminders to the responsible team members.
Audit workload distribution across team members
The agent tallies open tasks per person and flags imbalances so managers can rebalance before bottlenecks form.
Auto-tag and categorize incoming requests as Wrike tasks
The agent reads task descriptions, applies relevant tags and folders, and moves tasks into the correct project workflow.
Surface blocked tasks and escalate to project leads
The agent identifies tasks with dependency blockers or stalled status and notifies the project lead with context.
Using Wrike MCP with Gamut
On Gamut, the Wrike MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Wrike and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What is the Wrike MCP server?
It is a Model Context Protocol server that exposes Wrike to AI agents as tools, so they can manage projects, tasks, folders, and team workflows through natural-language commands.
How do I connect the Wrike MCP server?
Point your MCP client (Claude, Cursor, or Gamut) at the Wrike MCP server URL and authenticate with a bearer token. See the official documentation for the exact URL and scopes.
Can I use Wrike MCP with Gamut?
Yes — Gamut supports the Wrike MCP server, so your agents can use it as a tool in automated, triggered workflows.
Can the agent create and modify tasks in Wrike?
Yes. Depending on the bearer token's scopes, the agent can create, update, assign, and close tasks. Use a token with limited write permissions if you want to restrict what the agent can change.
Does it support Wrike's custom fields and workflows?
The MCP server works through Wrike's API, which supports custom fields, statuses, and workflow transitions. The agent can read and set custom field values when the API grants access.
Which Wrike plan is required for MCP access?
The MCP server connects through Wrike's API, which is available on Business and higher plans. Check Wrike's current plan comparison for API access details.
Is the Wrike MCP server read-only or read-write?
It supports both, scoped by the bearer token you provide. For monitoring and reporting, use a read-only token. For task creation and updates, grant write access to the specific resource types your agent needs.