Wrike MCP Server: What It Does and How to Connect Wrike to AI in 2026
Yes — Wrike has an official MCP server. Wrike’s hosted MCP server (mcp.wrike.com) lets any MCP-compatible AI tool read and act on your workspace: tasks, projects, folders, and status. Wrike launched it in June 2025 and it works with Claude, ChatGPT, Microsoft Copilot, Cursor, and Gemini. So if you’re searching “Wrike MCP,” the connection you want already exists and doesn’t require any code.
The thing worth knowing before you set it up: an MCP server hands your Wrike workspace to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches Wrike for you, nothing fires when a task hits its due date or moves status, and nothing runs while the chat is closed. Here’s exactly what the Wrike MCP does, how to turn it on, where it stops — and what to use when you want Wrike work that runs on its own.
What the Wrike MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Microsoft Copilot, Cursor, Gemini, and others — talk to an outside app through a shared interface. Wrike runs a cloud-hosted remote server, so there’s nothing to install or self-host. It enforces Wrike’s full permissions model too: connecting over MCP, an AI can only touch what your own account can touch, and every action shows up in Wrike’s activity stream under your name.
With it connected, an AI client can:
- Look up work — “show me the tasks due this week in the Q3 Launch project” answered from live Wrike data, not a guess.
- Query and filter — “which tasks are overdue and have no assignee?” run against your real workspace.
- Create and update — add a task, change its status, set a due date, or navigate and build out folder structure without opening Wrike.
- Reason across your workspace — summarize a project’s status, spot stalled tasks, or turn a block of meeting notes into tracked tasks with assignments.
It’s genuinely useful for ad-hoc work: ask a question, get an answer grounded in your projects, make a change on the spot.
How to set up the Wrike MCP server
The hosted server is the quick path — no code, no hosting:
- In Wrike, open Apps & Integrations and enable the MCP server for your account.
- In your AI client’s connector settings, add a remote MCP server pointing at
mcp.wrike.com(the streamable HTTP endpoint ishttps://mcp.wrike.com/app/mcp/stream, with an SSE alternative athttps://mcp.wrike.com/app/mcp/sse). - Authorize it against your Wrike account through the OAuth prompt — one-click sign-in grants the AI the same access your user has. (For automated setups you can use a permanent access token instead.)
- Confirm the tools appear in the client, then start a chat and ask it to read or update a task.
Wrike publishes setup guides for Claude, ChatGPT, Copilot Studio, Claude Code, and Gemini in its developer docs.
Where the Wrike MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch Wrike; it waits for you to ask.
- No triggers. A task moving to Completed, a due date arriving, a new task landing in a folder — none of these can start anything through MCP. There’s no “when this happens in Wrike, do that.”
- It’s one app at a time. The Wrike MCP knows Wrike. Getting a finished task into a Slack channel, a client email, and a Google Sheet means wiring up (and authing) a separate MCP server for each, then hoping your client can juggle them in one turn.
- You own the plumbing and the scopes. OAuth tokens, refresh, and the blast radius of read/write access to your workspace are all on you.
So the Wrike MCP is a great way to ask Wrike things and make one-off edits. It is not a way to make Wrike run — to have work happen on a schedule or in reaction to an event, across the other tools a project touches.
Running Wrike work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Wrike natively — no MCP server to enable, no OAuth plumbing to maintain — and to the ~260 other apps it supports, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Wrike work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a task moves to Completed → notify the requester in Slack, log the hours to a timesheet, and update the client-facing status sheet — automatically, the moment it happens.
- Every morning → summarize tasks overdue or due today across your projects and send the list to each owner.
- When a form or intake request comes in → create the Wrike task in the right folder, assign it, and draft the kickoff email for approval.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Wrike connection and everything downstream.
If you just want to interrogate your projects from a chat, Wrike’s official MCP server is the right tool and it’s free to connect. If you want Wrike to actually do things — on a trigger, on a schedule, across every app a project flows through — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Wrike have an official MCP server?
Yes. Wrike’s hosted MCP server at mcp.wrike.com (launched June 2025) gives MCP-compatible AI tools read/write access to your tasks, projects, and folders, with OAuth sign-in and Wrike’s full permissions model enforced.
Is the Wrike MCP server free? Connecting the MCP server is free; you enable it in Apps & Integrations and authorize an AI client against your existing Wrike account and permissions. You still need whatever Wrike plan your workspace runs on.
Can the Wrike MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Wrike work across apps, you need a workflow tool like Carly rather than an MCP server.
Can I connect Wrike to AI without coding or hosting a server? Yes. You don’t have to touch MCP at all. Carly connects to Wrike for you and lets you build the automation in plain language — describe what you want to happen and it wires up the workspace and the other apps involved, with no server to host and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
