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

Problems with the default pre-configured Wrike MCP available in Claude, ChatGPT, and Gemini

The connector is available or published by an administrator, but is not visible to users

• Make sure you have checked all available connectors. Sometimes the list is shuffled or reordered alphabetically after a connector is connected.
• Test with more than one user to confirm that the issue is not specific to a single user.

Some tools are not available in the MCP

• Check whether the tool you are interested in is listed here: MCP List of tools
• Check with the AI administrator to confirm that all required tools are enabled for the account on the AI assistant administration side.

Problems with a custom Wrike MCP that you set up manually using OAuth configuration data

I do not have access to “Apps & Integrations” or cannot create a new app

• Make sure you have the required API permissions in Wrike. The Account Owner always has these permissions.

I cannot set up a custom connector

• Check whether “Developer Mode” needs to be enabled to connect a custom connector.
• You may need support from the AI administrator if you do not have sufficient permissions to set up a custom MCP.

Authentication error with OAuth

• Make sure that the browser opened during authentication is the one where you are logged in to Wrike.
• Make sure that the redirect URLs are configured correctly for the OAuth client.
• If you experience re-authentication issues, try switching the MCP server URL from streamable HTTP (https://mcp.wrike.com/app/mcp/stream) to SSE by changing the Server URL to: https://mcp.wrike.com/app/mcp/sse.
• Contact your AI assistant administrator so they can check whether the connector’s OAuth configuration is set up correctly.

Authentication error with Permanent Access Token

• Verify that the Permanent Access Token is set correctly in the AI assistant configuration.
• Generate a new token if the current one is not working.
• Generate a new App if the current one is not working, and then generate a 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 assistant’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