TL;DR: Connect your favorite AI assistant (Claude, ChatGPT, Copilot, Gemini, Cursor) directly to your Wrike workspace in about 15 minutes. Contact your AI admin to get approval, verify your Wrike permissions, choose your connection method (Marketplace OAuth or Custom v2 URL), authenticate in your active Wrike browser session, and start managing tasks directly through natural language prompts.
Hello Community! 👋
The Wrike MCP server lets an AI assistant work directly in your Wrike workspace (pull your overdue tasks, update statuses, turn meeting notes into assigned work) without you switching tools. It works with Claude, ChatGPT, Microsoft Copilot, Google Gemini, Cursor, and any other MCP-compatible client.
Setup takes about 15 minutes if you have admin rights on both sides. Here's the process 👇
Step 1: Contact Your AI Assistant Administrator
Start here, not in a settings menu. The connection has two sides (your AI assistant and Wrike) and in most organizations you won't have admin rights on both.
Find whoever manages Claude, Microsoft Copilot, Google Gemini, or ChatGPT for your company. Depending on where you work, that's IT, a security or governance team, or whoever owns the AI vendor relationship.
If you don't know who to ask, submit an IT ticket. Include the name of the AI assistant your team uses, a link to the Wrike MCP Server Overview, and one concrete thing you want to do with it. "Pull my overdue tasks and update statuses without opening Wrike" gets approved. "Connect Wrike to AI" gets questions.
Ask them three things:
- Is the Wrike connector already available?
- Can I connect it myself or does an admin publish it?
- Are there security requirements to clear first?
(If it's already published, skip to step 4.)
Step 2: Confirm Your Wrike Access
The MCP server inherits the permissions you already have. It cannot see a space, project, or task you couldn't already open yourself. Connecting it doesn't widen anyone's access (tell your security team that first).
For the marketplace connectors, a Wrike login is all you need. If you're building a custom connector, you'll need access to Apps & Integrations in Wrike to create an app, which requires API permissions. Account Owners always have them; other roles may not.
Step 3: Choose Your Connection Method
Marketplace connector: One-click OAuth, nothing to configure. Take this option if it's available to you:
-Claude connector directory: Also searchable in-app under Settings Connectors
-ChatGPT: see the setup guide.
-Gemini Enterprise: The setup guide is here.
-Microsoft Copilot Studio: Add via MCP on the agent's Tools tab (setup guide)
Directory connectors move to MCP v2 automatically as each marketplace clears the update. Nothing for you to do.
Custom connector: for self-configured setups or assistants that aren't listed. The server URL is https://mcp.wrike.com/v2. MCP v2 is streamable HTTP only, so there's no SSE fallback; the older /app/mcp/stream and /app/mcp/sse URLs point to v1. If you set up a custom connector before v2 shipped, updating this URL is the only change you need. Some clients also require Developer Mode to be on. (Setup guide for other clients)
Permanent Access Token: For automated workflows and coding agents that run without a human present. For everyday use, OAuth is better: nothing to rotate or leak.
Also available: Claude and Claude Code setup guides.
Step 4: Connect and Authenticate
Follow the guide for your specific assistant: each handles connectors a little differently.
One thing causes most auth failures: make sure the browser that opens during sign-in is the one where you're already logged into Wrike. If your assistant launches a different default browser or a private window, it fails in a way that looks like a permissions problem but isn't.
Expect approval prompts on your first few actions, sometimes several for what feels like one operation. That's the AI client's permission model: each tool gets its own approval. Choosing "Allow always" for tools you trust settles it down fast.
If the connector doesn't appear, scroll the full list before assuming it's missing: some clients re-alphabetize once a connector is added. Still nothing? Have a colleague check. If neither of you sees it, it's an admin-side publishing issue.
Step 5: Test It, Then Refresh Your Tool List
Start with something you can verify instantly: "What tasks are assigned to me that are overdue?" Then try an action: "Mark the first one complete." Once you trust it, paste in your meeting notes and ask it to create tasks in a named space with the right assignees and due dates. That's the use case most people keep.
If tools look missing, your client has cached an old tool list (standard MCP behavior, not a Wrike bug). To refresh:
-Claude: Disconnect and reconnect under Settings Connectors, restart the desktop app.
-ChatGPT: Go to Settings Connectors Refresh (Enterprise admins do this under Workspace Settings Apps Action control, and must enable new tools explicitly).
-Copilot Studio: Turn on Allow all under Tools, or remove and re-add the Wrike MCP tool, then publish.
-Gemini Enterprise: An admin reconnects for the org.
-Cursor / VS Code: Reload the window.
Last thing: LLMs are non-deterministic, so the same question can return slightly different answers. That's normal. Be specific: include project names, folder locations, or permalinks when you know them.
Where to Go Next
Available tools on Wrike MCP tell you exactly what it can and can't do. Typical use cases are the fastest way to find something worth trying.
For your security team: the MCP server only accesses data you already have permissions for, all traffic is encrypted over HTTPS, no data is stored or cached by the server, and tokens stay local to your device. Details in the Wrike Privacy Policy.
How are you planning to use the Wrike MCP server? Share your favorite workflows, prompts, or questions in the comments below! 👇
