Head to head · Tasks create · October 2026 research run
Teamwork.com vs Wrike
Teamwork.com scores 65.9 (B) on agent readiness against Wrike's 60.1 (C), and leads in 4 of 7 scored categories. Wrike leads on schema & documentation. Both do tasks create.
Which one, for what
Good for Agencies and services firms already on Teamwork.com that want an assistant to create and update tasks, log time, read workload and budgets, and answer Desk tickets.
Ahead on
- Reliability, 73 against 68
- Agent ergonomics, 68 against 63
- Maintenance & community, 88 against 63
Also in its favour
- Runs on your own machine
- No incidents deducted, where Wrike loses 3 points for them
Watch for
OAuth scopes are per product only (projects, desk, spaces, chat), and the token from the app login flow is described as permanent
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
- Schema & documentation, 78 against 72
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 | Teamwork.com | Wrike | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 73 | 68 | Teamwork.com +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 72 | 78 | Wrike +6 |
| Agent ergonomics | 13%16.2 | 68 | 63 | Teamwork.com +5 |
| Security & auth | 14%17.5 | 58 | 60 | Wrike +2 |
| Payments & pricing | 10%12.5 | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 88 | 63 | Teamwork.com +25 |
| Transparency & trust | 7%8.8 | 80 | 78 | Teamwork.com +2 |
| Negative events | ≤15 | 0 | -3 | |
| Total | 65.9 · B | 60.1 · C |
Facts side by side
| Fact | Teamwork.com | Wrike |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Teamwork Crew Limited | Wrike, Inc. |
| Hosted endpoint | https://mcp.ai.teamwork.com | https://www.wrike.com/api/v4 |
| Transports | HTTP, Streamable HTTP, SSE (legacy), stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Teamwork.com's terms of service. The MCP server on GitHub is MIT | Proprietary service under Wrike's terms. The agent skills repository on GitHub is MIT |
| Tools exposed | 225 | 29 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-10-06 | 2026-09-17 |
| Terms last updated | no date given | 2025-04-08 |
| Privacy policy last updated | 2024-08-19 | 2026-06-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 26 stars | none |
Verdicts
Teamwork.com
The official MCP server is MIT licensed, released almost daily, and has typed tools with annotations, profile endpoints and no delete tools on the shipped servers. OAuth scopes stop at product level, access tokens are permanent, and no SLA, API changelog or prompt-injection guidance was found in the reviewed documentation.
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
Teamwork.com
- Use a profile endpoint such as https://mcp.ai.teamwork.com/project-manager. The base URL loads every tool across Projects, Desk, Spaces and Chat.
- Ask a site administrator to enable MCP under Settings, AI before connecting.
- Build REST URLs from
installation.apiEndPointin the token response. Sites live at {site}.teamwork.com (US) or {site}.eu.teamwork.com (EU). - Stay under 150 requests a minute on Free, Basics and Accelerate. The limit is shared by the whole site. On 429, wait until
X-Rate-Limit-Reset. - Pass
verbose=falsetolist_*tools to get ids and names only, and usetwprojects-create_tasksfor many tasks in one call.
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, Teamwork.com or Wrike?
Teamwork.com scores 65.9 (B) on agent readiness against Wrike's 60.1 (C), and leads in 4 of 7 scored categories. Wrike leads on schema & documentation.
Do Teamwork.com and Wrike need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Teamwork.com and Wrike without installing anything?
Yes. Teamwork.com has a hosted endpoint at https://mcp.ai.teamwork.com and Wrike at https://www.wrike.com/api/v4.
Other comparisons with Teamwork.com or Wrike
- Asana vs Teamwork.com
- Asana vs Wrike
- Basecamp vs Teamwork.com
- Basecamp vs Wrike
- ClickUp vs Teamwork.com
- ClickUp vs Wrike
- monday.com vs Teamwork.com
- monday.com vs Wrike
- Plane vs Teamwork.com
- Plane vs Wrike
- Roma vs Teamwork.com
- Roma vs Wrike
- Shortcut vs Teamwork.com
- Shortcut vs Wrike
- Teamwork.com vs Todoist
- Teamwork.com vs Trello
- Teamwork.com vs YouTrack
- Todoist vs Wrike
- Trello vs Wrike
- Wrike vs YouTrack
Machine-readable
- This page as Markdown
/compare/teamwork-vs-wrike.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/teamwork.json·/api/v1/tools/wrike.json - From a terminal
anchor compare teamwork wrike(the CLI) - Over MCP
compare_tools {"a": "teamwork", "b": "wrike"}at/mcp, no key