Wrike MCP Server Overview
Connect your AI assistant to Wrike to find work, understand project context, create and update items, and take action without switching between tools.
Wrike MCP works with Claude, ChatGPT, Microsoft Copilot, Gemini, and other MCP-compatible clients.
MCP is an open standard that allows AI assistants to securely use tools and data from external applications. Wrike MCP gives compatible AI assistants a structured way to work with your Wrike workspace while respecting your existing Wrike permissions.
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. Create work out of Blueprints or by submitting a Request Form
- 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
Custom MCP connections
If your AI client does not provide an official Wrike integration, connect directly to the Wrike MCP server:
https://mcp.wrike.com/v2
Wrike MCP v2 uses Streamable HTTP.
For interactive connections, OAuth 2.0 is recommended. An administrator creates the Wrike OAuth application once, and individual users authenticate using their own Wrike accounts.
For testing, automation, or non-interactive environments, you can alternatively use a Permanent Access Token.
Permanent Access Token authentication →
Permissions and security
Wrike MCP respects your existing Wrike permissions.
Connecting an AI assistant does not give it unrestricted access to your Wrike account. The assistant can only access data and perform actions available to the Wrike user who authenticated the connection.
Additional restrictions may also be applied by administrators in the AI platform you use.
All communication with the Wrike MCP server uses HTTPS.
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
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.
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.
- Check that your Server URL is exactly https://mcp.wrike.com/v2. MCP v2 is served over streamable HTTP only, so there is no SSE endpoint to fall back to. The older https://mcp.wrike.com/app/mcp/stream and https://mcp.wrike.com/app/mcp/sse URLs point to MCP v1 and do not serve the v2 tool set.
- 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.
Some tools are missing, or new tools don't appear after an update
The Wrike MCP server exposes a fixed set of tools — you don't add or remove individual tools per connection. Your AI client caches that tool list the first time it connects, so after Wrike ships new tools (for example, the v1 → v2 update), your client may keep showing the old list until you refresh it. This is standard MCP client behavior, not specific to Wrike.
To load the latest tools, refresh the Wrike connector in your client:
| AI client | How to refresh |
|---|---|
Claude / Claude Code | Disconnect and reconnect the Wrike connector (Settings → Connectors). In Claude Desktop, restart the app. An older connection may appear as a "Custom" connector until you re-add it. |
ChatGPT (personal / custom) | Settings → Connectors → your Wrike connector → Refresh. |
ChatGPT (Business / Enterprise) | An admin refreshes it: Workspace Settings → Apps → the Wrike app → Action control → Refresh. New tools are disabled by default and shown as a diff — the admin must enable them. Until then, a changed tool can error. |
Microsoft Copilot Studio | On the agent's Tools tab, make sure Allow all is on (when it's off, newly added tools are off by default — enable them individually). If the old list persists, remove the Wrike MCP tool and add it again (Add a tool → Model Context Protocol), then Publish the agent. |
Gemini Enterprise | An administrator reconnects the Wrike connector for the organization. |
Cursor / VS Code | Reload the window, or restart the editor. |
| Other MCP clients | Check the client's documentation for how to refresh the MCP tool list (usually disconnect/reconnect or restart). |
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
Learn more
Available tools on Wrike MCP
See the complete set of Wrike data and actions available to AI assistants.
Typical Use Cases of Wrike MCP
Explore practical workflows such as project status reporting, work intake, meeting follow-up, and task management.
Connect Wrike MCP as a custom connector
Configure Wrike manually in an MCP-compatible client.
Permanent Access Token authentication
Use token-based authentication for testing, automation, and non-interactive environments.
Updated about 19 hours ago