← All integrations

Wrike MCP server

23 operations0 webhooks

Work management with Wrike - search and manage tasks, work with folders and projects, log and read time entries, comment on tasks, and read contacts and account settings.

Try Wrike with your agent

Connect Wrike, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Wrike on my account, then run one read-only example and show me the result.

Runs once, when you ask

Wrike tools and triggers

Tools are what your agent can do in Wrike through Corsair's MCP server. Triggers are the Wrike events a routine can start from.

Folders

  • CreateWrite

    Create a folder inside another, or in the account root when given its virtual root id

    folders.create

  • DeleteDestructive

    Move a folder and every folder and task inside it to the recycle bin unless they have parents outside the deleted folder; Wrike does not refuse a folder with contents

    folders.delete

  • GetRead-only

    Read one folder or project

    folders.get

  • ListRead-only

    List folders and projects, each with its parent and scope

    folders.list

  • TasksRead-only

    List the tasks in a folder, optionally including every descendant folder

    folders.tasks

  • UpdateWrite

    Rename a folder, change its description or move it between parents

    folders.update

Comments

  • CreateWrite

    Post a comment on a task

    comments.create

  • DeleteDestructive

    Delete a comment

    comments.delete

  • ListRead-only

    List comments across the account, up to a limit

    comments.list

  • TaskRead-only

    List the comments on a task

    comments.task

  • UpdateWrite

    Edit the text of a comment you wrote; Wrike allows it only in the 5 minutes after posting

    comments.update

Tasks

  • CreateWrite

    Create a task in a folder, with assignees, dates, custom fields and metadata; Wrike has no account-level create

    tasks.create

Connect Wrike to Claude, ChatGPT or Cursor

  1. 1

    Connect Wrike in Corsair

    Add your Wrike API key once in Corsair. Corsair stores the credential encrypted and makes the Wrike API calls for your agent, so it never goes into a prompt or a config file. Connect Wrike

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Wrike. On a ChatGPT personal plan, connect Wrike here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Wrike's read and write operations run right away and its 4 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/wrike, add the Wrike plugin, and connect with an API key. Then call methods like corsair.wrike.api.account.get() from your app. Corsair keeps each tenant isolated.

Yes. Wrike requires an API key from your Wrike account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Wrike, GitHub, Notion, Stripe, and the rest. Trigger Wrike from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for work management with Wrike - search and manage tasks, work with folders and projects, log and read time entries, comment on tasks, and read contacts and account settings. Common builds include sync jobs, admin tooling, and agents that call Wrike APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Wrike API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/wrike in the open repo. When Wrike ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Wrike data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Wrike data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Wrike on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 4 destructive Wrike operations. You can change a link's mode at hub.corsair.dev/me.