Wrike MCP server
Wrike in any MCP client, through Memtro: Wrike does not publish this server. Memtro's Wrike connector reads Wrike through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Wrike work management: tasks by status, title or recent change, projects, people, time logs and task comments; when asked, can create, edit, assign, complete, move or delete a task, link tasks as dependencies, create or edit a folder or project, comment, log or correct time, and invite a person to the account.
Reads
wrike_list_tasksTasks in Wrike, most recently updated first: title, status, importance, dates, who is responsible (ids…wrike_list_projectsProjects in Wrike: title, status, owners (ids), start and end dates.wrike_list_contactsPeople in the Wrike account: id, name, email, role and whether active.wrike_list_timelogsTime logged in Wrike: hours, the date it was tracked for, the task, the person (id) and the comment.wrike_list_task_commentsComments on one Wrike task: author (id), when and the text.
Acts, when you ask
These change something in Wrike. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
wrike_create_taskCreates a task in a Wrike folder or project, with an optional description, due date and responsible people.wrike_add_commentAdds a comment to a Wrike task, as the token's user.wrike_log_timeLogs time on a Wrike task for the token's user: hours, the date worked and a comment.wrike_update_taskChange a Wrike task's title, description, importance or dates.wrike_assign_taskAdd people to, or remove them from, a Wrike task's assignees (ids from wrike_list_contacts).wrike_complete_taskSet a Wrike task's status: Completed, Deferred, Cancelled, or Active to reopen it (not available on Wrike's Team plan).wrike_move_task_to_folderPut a Wrike task into more folders or projects, or take it out of some (a task can sit in several).wrike_delete_taskDelete a Wrike task; it goes to the Recycle Bin, from which it can be restored in Wrike.wrike_add_task_dependencyMake one Wrike task depend on another (give exactly one of predecessor_id or successor_id), which can reschedule the dependent task.wrike_create_folderCreate a folder, or a project when project settings are given, inside a Wrike folder or project.wrike_update_folderRename a Wrike folder or project, change its description, or change a project's status, dates or owners.wrike_update_timelogCorrect a Wrike time log's hours, date or comment.wrike_update_commentReplace the text of a Wrike comment; Wrike allows this only in the 5 minutes after it was posted.wrike_invite_userInvite a person into the Wrike account by email.
Connect it
First connect Wrike on Dashboard → Connections, then add Memtro to your client once. The Wrike tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Wrike connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What is due in Wrike this week?
- › What changed on the Northwind launch project since Monday?
- › How many hours did I log on the Acme migration last week?
- › Create a task in the Brightwave Ltd project: draft the onboarding email, due next Wednesday, Priya Nair responsible
- › Mark the BigCo pricing page task completed
Questions
- Is this an official Wrike MCP server?
- No. It is Memtro's MCP server with Memtro's Wrike connector behind it: the connector reads Wrike through its API with the credentials you connect on Dashboard → Connections, and Wrike publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Wrike?
- Only when you ask, and only what it has been granted: create a task in a Wrike folder or project; add a comment to a Wrike task; log time on a Wrike task; edit a Wrike task's title, description, importance or dates; add or remove assignees on a Wrike task; set a Wrike task's status (complete, defer, cancel, reopen); move a Wrike task into or out of folders; delete a Wrike task (to the Recycle Bin); make one Wrike task depend on another; create a Wrike folder or project; edit a Wrike folder or project; correct a Wrike time log; edit a Wrike comment within 5 minutes of posting; invite a person into the Wrike account by email. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.