# Your Wrike projects. A review that writes itself.

Source: https://corespeed.io/integrations/wrike

Connect Wrike to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent lists your folders and projects, reads your tasks by status and the comments on them, and drafts a review of what is deferred and why. It uses your own Wrike account, and creating a task or adding a comment is a separate call.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Wrike after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## See what is deferred. Read why it waits

Ask your agent to read your deferred Wrike tasks and their comments, then draft a review of what waits and on whom.

You ask your agent: "List my deferred tasks in Wrike. Read each one and its comments, and draft a review of what waits and on whom. Do not change any task."

It calls CoreSpeed:

- `wrike__list_tasks`: ok, 487 ms
- `wrike__get_task`: ok, 341 ms
- `wrike__list_task_comments`: ok, 263 ms

It reads from: Wrike.

### Deferred work: What waits, and on whom.

Three tasks are deferred. Northwind SSO setup waits on the client's identity team.

**Waiting on others**

- Northwind SSO setup: the client's identity team.

**Next step**

- Escalate to the Northwind account owner.
- Set a date to revisit SSO.

_Illustrative example · Fictional data · No tasks changed_

All connectors: https://corespeed.io/docs/connectors

## From folders and comments to the next decision

Requests you can make once Wrike is connected. The data is fictional.

### Check tasks by status

Active and deferred · Tasks by status

- Active: Northwind data import
- Deferred: Northwind SSO setup
- From the tasks you can access

### Read why a task waits

SSO setup · Task comments

- Waiting on: The client's identity team
- Since: Last Monday
- Read, not changed

### Hold a comment for review

Add a follow-up note · Example approval policy

- Policy: Ask before commenting on a task
- Outcome: The comment waits for a person
- Approval required

Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md)

## Keep your agent. Bring your work

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Wrike**: Authorize the account and the content you need.
3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Does it work on any Wrike data center?

Yes. CoreSpeed uses the data-center host of your Wrike account, so EU and US accounts both connect.

### Can my agent delete a Wrike task?

Only by a separate delete call on one exact task, which approvals can hold for a person.

### Does this send or change anything on its own?

No. These examples read context and draft a result. Sending or changing a record is a separate tool call, which approvals can hold for a person. How approvals work: https://corespeed.io/docs/approvals

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/wrike

## Related pages

- [Basecamp for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/basecamp): Bring Basecamp projects and open to-dos into your agent. Draft a check-in of the open work and who holds it.
- [Linear for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/linear): Bring Linear issues and project context into your agent. See what is moving and what needs attention.
- [monday.com for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/monday): Bring monday.com boards into your agent. Check a plan against the board's items, and draft what is missing.
- [Shared agent tools and controls for teams](https://corespeed.io/solutions/teams): Manage shared connections, approval policies, and tool usage for teams working across Claude Code, Codex, and other MCP clients.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- Wrike API: Tasks: https://developers.wrike.com/api/v4/tasks/
- Wrike API overview: https://developers.wrike.com/overview/

Reviewed 2026-11-10.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)