Wrike MCP Server Overview

Wrike offers a Model Context Protocol (MCP) server, accessible via Apps & Integrations, that enables AI assistants to access and interact with your Wrike workspace data— query projects, manage tasks, and navigate folders. It works with Microsoft Copilot, Claude, ChatGPT, Cursor, and any other MCP-compatible clients.

The Model Context Protocol (MCP) is an open standard that lets AI assistants interact with your Wrike workspace.

Why use Wrike MCP?

What can you do with Wrike MCP?

• Report & act on status — Get quick status updates on team tasks and act on them without opening Wrike
• Prioritize work — Get an overview of what's urgent based on importance and due dates
• Search & find answers — Find specific information across Wrike's folder hierarchy using natural language
• Create work structures — Set up folders, projects, and tasks through conversation
• Convert meeting notes to tasks — Turn action items into tracked Wrike tasks with assignments and due dates
• Workspace onboarding — Explore spaces, projects, custom fields, and workflows conversationally
• and much more

To see a tools that are supported on Wrike MCP, check Available tools on Wrike MCP.

Detailed setup instructions for each AI assistant

Alternative authentication: Permanent Access Token

OAuth is the standard authentication method that we recommend for the majority of the cases where you connect your AI Assistant with Wrike MCP server. This will avoid users having to manage tokens or mcp configurations, and the only thing that the user will need to do is to log in inside wrike when the authentication is triggered.

_For fully automated workflows, cloud-based coding agents that run without human interaction or individual use, the Permanent Access token can be used. _

Each user generates an App and then generates a Permanent Access Token that inherits their Wrike permissions. See Alternative Authentication Setup for step-by-step instructions.

Usage examples

Example 1: Report status

Prompt: "What tasks are assigned to Carol that are overdue?"

Result: Returns overdue tasks with title, status, due date, and links. Follow up with "Mark the first task as completed" to take action directly.

Example 2: Create work structure

Prompt: "Create a folder called 'Client: Acme Corp' in the Project Team space. Create 3 projects inside: Onboarding, Implementation, Support. For Onboarding, add tasks: Kickoff Call, Requirements Gathering, Contract Signing. Assign all to Katerina, due within 2 weeks."

Result: Complete folder/project/task structure created with assignments and due dates.

Example 3: Convert meeting notes to tasks

Prompt: "Action items from today's meeting: 1) Update Campaign brief — Susan; 2) Arrange photoshoot — Jonathan; 3) Meeting with models — Theresa. Create tasks in Marketing space, Backlog folder, assign appropriately, all due next Friday."

Result: Three tasks created with correct assignees and due dates.

Important considerations

• LLMs are non-deterministic — the same query may produce slightly different responses each time. This is normal AI behavior, not a bug in the integration.
• Be specific in your queries — include permalinks, project names, folder locations, or task details when known for best results.
• If the first response isn't perfect, refine your query with more context.

Troubleshooting

I have no access to "Apps & Integrations" or can't create a new App

• Ensure you have proper API permissions in Wrike (Account Owner always has it)
• Check your internet connection

Connector is available/published by Administrator, but not visible for Users

• Try checking if "Developer Mode" needs to be enabled to connect a custom connector
• Ensure you have looked at all the connectors available, sometimes it shuffles or reorders alphabetically once Connected
• Test with more than one user to ensure it is not a specific user issue

Authentication error with OAuth

• Disconnect the Custom connector and try and re-connecting it
• If you're seeing re-authentication problems, try switching the MCP server URL from streamable http to sse, changing the Server URL to: https://mcp.wrike.com/app/mcp/sse
• Ensure that the browser that is triggered is the one you have the Wrike login data.
• Contact your AI Assistant Administrator(s), so that they can check if OAuth configuration on the Connector is properly configured.
• (For the Admin) Delete the Wrike App and create a new one, and reconfigure the AI Assistant settings

Authentication error with Permanent Access Token

• Verify that the Permanent Access Token is properly set in the configuration of the AI Assistant
• Generate a new token if the current one isn't working
• Generate a new App if the current one isn't working, and then generate the new token

Inconsistent responses

• Remember that LLMs are non-deterministic by nature
• Add more specific context to your queries
• Use system prompts to guide the AI's understanding of Wrike

Privacy policy and terms of use

Your privacy matters. See the Wrike Privacy Policy and Wrike Terms of Use for details on how your data is handled.

• API tokens and OAuth tokens are stored locally on your device
• All communication is encrypted via HTTPS
• The MCP server only accesses data you have permissions for in Wrike
• No data is stored or cached by the MCP server

Support

• Help Center: Contact Wrike Support (live chat, request form, phone for Premium plans)
• Community: Submit feature requests through Wrike Community