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

Teamwork.com B

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

CategoryWeight this runTeamwork.comWrikeEdge
Reliability16%207368Teamwork.com +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27278Wrike +6
Agent ergonomics13%16.26863Teamwork.com +5
Security & auth14%17.55860Wrike +2
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88863Teamwork.com +25
Transparency & trust7%8.88078Teamwork.com +2
Negative events≤150-3
Total65.9 · B60.1 · C

Facts side by side

FactTeamwork.comWrike
KindHTTP APIHTTP API
VendorTeamwork Crew LimitedWrike, Inc.
Hosted endpointhttps://mcp.ai.teamwork.comhttps://www.wrike.com/api/v4
TransportsHTTP, Streamable HTTP, SSE (legacy), stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under Teamwork.com's terms of service. The MCP server on GitHub is MITProprietary service under Wrike's terms. The agent skills repository on GitHub is MIT
Tools exposed22529
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-10-062026-09-17
Terms last updatedno date given2025-04-08
Privacy policy last updated2024-08-192026-06-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity26 starsnone

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

  1. 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.
  2. Ask a site administrator to enable MCP under Settings, AI before connecting.
  3. Build REST URLs from installation.apiEndPoint in the token response. Sites live at {site}.teamwork.com (US) or {site}.eu.teamwork.com (EU).
  4. 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.
  5. Pass verbose=false to list_* tools to get ids and names only, and use twprojects-create_tasks for many tasks in one call.

Wrike

  1. Build API URLs from the host value 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.
  2. Use https://mcp.wrike.com/v2 only. The older /app/mcp/stream and /app/mcp/sse URLs serve the v1 tool set.
  3. Call search_workflows before setting a status, because update_items and search_items take custom status ids.
  4. 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.
  5. Page task lists with pageSize (up to 1,000) and nextPageToken, and request optional data through fields.

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

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.