Wrike MCP Server Overview | Develop your own integration on the Wrike API

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?

Productivity boost — Manage Wrike tasks without switching contexts from your AI assistant
Easy setup — Connect through simple OAuth, with one-click sign-in, for supported AI tools including Microsoft Copilot, ChatGPT, Claude, and others
Access to your data — AI assistants can read and write your Wrike data without manual exports or copy-pasting
Optimized for AI — Built specifically for AI agents with efficient data formatting

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

Authentication and setup for administrator

All user permissions from Wrike are automatically enforced. The MCP server respects the same security boundaries as your workspace — users can only access data they have permission to view in Wrike.

OAuth 2.0 (recommended)

Step 1: Create a Wrike App (administrator, one-time per organization) on Apps & Integrations

A user with access to Apps & Integrations (preferably the account owner) performs this setup once:

In Wrike, click your profile icon and select Apps & Integrations
Click the API tab
Click Create new app
Fill in the app details:

App name — e.g., "Wrike MCP Integration"
App description — e.g., "Wrike App necessary to connect the Wrike MCP to AI assistants"

The OAuth Client ID and Secret key are generated automatically. Copy them securely — you will need them in the next step.
Under Redirect URLs, add the redirect URL(s) for your AI assistant(s) of choice:

Claude: https://claude.ai/api/mcp/auth_callback
ChatGPT: https://chatgpt.com/connector_platform_oauth_redirect
Microsoft Copilot: https://global.consent.azure-apim.net/redirect

You can add multiple redirect URLs to support several AI assistants from the same Wrike app.
Leave the remaining settings unchanged and click Save

Note: Unlike Permanent Access Tokens, OAuth apps are organization-wide — any user in the account can authenticate through them. The admin creates the app once; individual users authenticate with their own Wrike credentials.

Step 2: Configure the AI assistant (administrator, one-time per organization)

As an account owner or administrator of the AI assistant platform (Claude, Microsoft Copilot, ChatGPT, or any other AI assistant with the enterprise account), register the Wrike MCP server with the following details from Step 1:

Connector/App Name: make it clear to your users that this is the way to connect to Wrike, e.g. Wrike MCP or Wrike Connector
MCP server URL: https://mcp.wrike.com/app/mcp/sse
Select OAuth as Authentication method
OAuth Client ID — from your Wrike app
OAuth Client Secret — from your Wrike app

Then click Create or Save. You may also have to enable/publish the the Connector so that all users (or a subset of them) can see the connector on their enterprise account.

See the detailed setup instructions for each AI assistant:

Claude
ChatGPT
Microsoft Copilot
Other MCP clients (Cursor, custom clients, etc.)

Setup instructions on the end-user side

Once the administrator has configured the AI assistant, each user simply:

Opens their AI assistant (Claude, Copilot, ChatGPT, etc.)
Goes to Settings > Connectors (or equivalent)
Searches for the Wrike MCP connector and clicks Connect
Completes a one-click OAuth login with their Wrike account
Their personal Wrike permissions are applied automatically

Alternative authentication: Permanent Access Token

For fully automated workflows, cloud-based coding agents that run without human interaction or individual use, the Permanent Access token can be used. Not recommended for enterprise team deployments.

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 to https://mcp.wrike.com/app/mcp/stream
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

Your privacy matters. See the Wrike Privacy Policy 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