Head to head · Tasks create · October 2026 research run
ClickUp vs Wrike
ClickUp and Wrike score within a point of each other on agent readiness, 60.9 (C) and 60.1 (C). Wrike leads on agent ergonomics and maintenance & community. Both do tasks create.
Which one, for what
ClickUp C
Good for Teams already working in ClickUp that want an assistant to create and update tasks, comment, log time and read Docs through one OAuth connection.
Ahead on
- Reliability, 74 against 68
Also in its favour
- No incidents deducted, where Wrike loses 3 points for them
Watch for
MCP calls are capped per rolling 24 hours without the Everything AI add-on, 100 on Free Forever and 300 on Unlimited, per Workspace and client
Wrike C
Good for Teams already on Wrike that want an assistant to find work, create tasks and projects from notes, update status in bulk, comment and check approvals.
Ahead on
- Agent ergonomics, 63 against 48
- Maintenance & community, 63 against 54
Also in its favour
- Free to start without a card
Watch for
A permanent access token never expires and reaches everything its user can, and it is the documented route for clients that need dynamic client registration
Score by category
| Category | Weight this run | ClickUp | Wrike | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 74 | 68 | ClickUp +6 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 74 | 78 | Wrike +4 |
| Agent ergonomics | 13%16.2 | 48 | 63 | Wrike +15 |
| Security & auth | 14%17.5 | 64 | 60 | ClickUp +4 |
| Payments & pricing | 10%12.5 | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 54 | 63 | Wrike +9 |
| Transparency & trust | 7%8.8 | 75 | 78 | Wrike +3 |
| Negative events | ≤15 | 0 | -3 | |
| Total | 60.9 · C | 60.1 · C |
Facts side by side
| Fact | ClickUp | Wrike |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Mango Technologies, Inc. DBA ClickUp | Wrike, Inc. |
| Hosted endpoint | https://api.clickup.com | https://www.wrike.com/api/v4 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under ClickUp's Terms of Service and Developer Terms. The clickup-plugin repository on GitHub is MIT | Proprietary service under Wrike's terms. The agent skills repository on GitHub is MIT |
| Tools exposed | 48 | 29 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-09-18 | 2026-09-17 |
| Terms last updated | 2025-06-27 | 2025-04-08 |
| Privacy policy last updated | 2026-06-02 | 2026-06-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
Verdicts
ClickUp
The hosted MCP server uses OAuth 2.1 with PKCE, dynamic client registration and read and write scopes, and works on the Free Forever plan. Without the Everything AI add-on, MCP calls are capped at 100 to 25,000 per rolling 24 hours by plan. No API changelog, deprecation policy, official SDK or SLA was found.
Wrike
The official MCP server has 29 documented tools for search, task and project creation, bulk updates, comments and approvals, and it works on every plan including Free. Permanent access tokens never expire and carry the user's full access, and no SLA, official SDK or deprecation policy was found in the reviewed documentation.
Before you call either
ClickUp
- Connect to https://mcp.clickup.com/mcp with OAuth 2.1 and PKCE. API keys and REST OAuth tokens are refused on the MCP server
- Pass
workspace_idon every MCP call when the user belongs to more than one Workspace, as ClickUp's own skills instruct - Budget MCP calls. Each tool call counts against the rolling 24-hour cap, and
RATE_LIMIT_EXCEEDEDreturnsretryAfter - On the REST API read
X-RateLimit-RemainingandX-RateLimit-Reset, and page Get Tasks withpageat 100 tasks a page - Treat
team_idin API v2 as the Workspace ID, and send dates as Unix milliseconds
Wrike
- Build API URLs from the
hostvalue returned by /oauth2/token. Accounts live on www.wrike.com, app-eu.wrike.com or app-us2.wrike.com, and the wrong host answers 401. - Use https://mcp.wrike.com/v2 only. The older /app/mcp/stream and /app/mcp/sse URLs serve the v1 tool set.
- Call
search_workflowsbefore setting a status, becauseupdate_itemsandsearch_itemstake custom status ids. - Stay under about 400 requests a minute per token or IP and back off exponentially on 429. Use POST /batch for up to 100 operations.
- Page task lists with
pageSize(up to 1,000) andnextPageToken, and request optional data throughfields.
Questions
Which is better for AI agents, ClickUp or Wrike?
ClickUp and Wrike score within a point of each other on agent readiness, 60.9 (C) and 60.1 (C). Wrike leads on agent ergonomics and maintenance & community.
Do ClickUp and Wrike need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call ClickUp and Wrike without installing anything?
Yes. ClickUp has a hosted endpoint at https://api.clickup.com and Wrike at https://www.wrike.com/api/v4.
Other comparisons with ClickUp or Wrike
Machine-readable
- This page as Markdown
/compare/clickup-vs-wrike.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/clickup.json·/api/v1/tools/wrike.json - From a terminal
anchor compare clickup wrike(the CLI) - Over MCP
compare_tools {"a": "clickup", "b": "wrike"}at/mcp, no key