Head to head · Issues and tasks · October 2026 research run

ClickUp vs Teamwork.com

Teamwork.com scores 65.3 (B) on agent readiness against ClickUp's 62.6 (B), and leads in 4 of 7 scored categories. ClickUp leads on schema & documentation and security & auth. Both do issues and tasks.

Best project and task management tools for AI agents · All 189 projects comparisons

Which one, for what

ClickUp B

Best 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

  • Schema & documentation, 79 against 72
  • Security & auth, 64 against 58

Also in its favour

  • No incidents deducted, where Teamwork.com loses 3 points for them

Watch for

MCP calls are capped per rolling 24 hours by plan unless the Workspace has the Everything AI add-on, 100 on Free Forever and 300 on Core or Unlimited, per Workspace and client

Teamwork.com B

Best 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 62
  • Agent ergonomics, 68 against 57
  • Maintenance & community, 93 against 54
  • Transparency & trust, 80 against 75

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

OAuth scopes are per product only (projects, desk, spaces, chat), and the token from the app login flow is described as permanent

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Teamwork.com +39

ClickUp 54

The MCP tools reference was updated on 27 October 2026 and product Release Notes 4.09 are dated 17 October 2026 (30). The product changelog has four dated entries since 5 August (18 August, 25 August, 18 September, 17 October), none about the public API. Docs pages changed on 10 August, 14 August, 17 September, 7 October and 27 October, and the official plugin repository had commits on 11 August, 7 September, 19 October and 30 October, the last two adding marketplace manifests (12 of 20). Public product changelog and feedback board, and 24/7 support stated on the pricing page. No API changelog, and response times were not checked (8 of 15). No entry under a ClickUp namespace in the official MCP registry, and no official SDK (0). The official clickup-plugin repository is MIT, still at version 1.1.0, with eight commits between 1 April and 30 October 2026 (4 of 10).

Teamwork.com 93

MCP server v1.60.1 was tagged on 30 October 2026 (30). The repository has 54 tags from 3 August to 30 October 2026, four of them since 8 October (20). Issue activity per the 8 October check of the GitHub API, not re-read on 1 November because GitHub refuses our reader. Three issues were open, and a bug report of 6 October (#581) was fixed and released the same day (20 of 25). The official MCP registry lists com.teamwork/mcp under Teamwork's own namespace, with 1.60.1 published on 30 October as the latest version, beside the Go SDK twapi-go-sdk (v1.37.0 on 23 October) (15). A test workflow runs on every push, and dependency updates are merged within days (8 of 10).

Reliability Teamwork.com +11

ClickUp 62

Graded on the hosted MCP server and the public REST API, with the hosted lines. Status page at status.clickup.com on incident.io with 22 components, Public API among them, per the 8 October check (20). The incident window from 5 August couldn't be read on 3 November (a permission check refused the status feed and it wasn't retried). The 8 October incident reading came from the page's data endpoint, which this method doesn't use, so it is struck and the window is scored as unread (5). API limits published per plan, 100 requests a minute per token on Free Forever, Unlimited and Business, 1,000 on Business Plus and 10,000 on Enterprise, an MCP server limit of 1,000 requests a minute per connection and daily MCP caps of 100 to 25,000 calls (15). 429s carry X-RateLimit-* headers on the REST API. Since 27 October the MCP tools reference documents 429 with Retry-After: 60, RATE_LIMIT_EXCEEDED with retryAfter, reads as safe to retry, and says to check whether a write happened before retrying, since creates, comments and time entries duplicate. Safe-retry guidance without idempotency keys (12). No SLA found in the reviewed pages (0). Neither surface is marked beta, though the MCP docs say limits may change (10).

Teamwork.com 73

Graded on the hosted lines for REST API v3 and the hosted MCP server. status.teamwork.com is a Statuspage site whose front page lists components for Projects, Desk, Chat, Spaces and CRM in the US and EU regions, the websites and the API docs, though none for the API or the MCP server by name (20). Its history.atom feed, read on 1 November (robots.txt closes /api/, so the 8 October reading of the incidents and components feeds no longer counts), lists three incidents in the 90 days from 3 August, besides scheduled maintenance. Task creation in Projects for 40 minutes on 24 September, the Projects API in the US region from 13:08 to 14:58 UTC on 16 October, and loading issues for Projects apps in the US region from 15:58 to 17:21 UTC on 26 October. Each touched one function or one region, so all read as minor (20). The pricing page gives the API limit per plan, 150 requests a minute on Free, Basics and Accelerate, 300 on Optimize and 500 on Enterprise (15). A 429 comes with X-Rate-Limit-Limit, X-Rate-Limit-Remaining and X-Rate-Limit-Reset and the guide says access returns after 60 seconds. No Retry-After header and no idempotency keys were found (8 of 15). No SLA found. The terms promise reasonable endeavours and the security page states a goal of over 99.9 per cent (0). API v3 and MCP server 1.x carry no beta label (10).

Agent ergonomics Teamwork.com +11

ClickUp 57

65 documented MCP tools (5). The OAuth metadata advertises separate read and write scopes and clickup_get_task takes an include list (3 more, 8 of 25). Get Tasks filters by status, assignee, tag, dates and Custom Fields at 100 tasks a page, v3 and the MCP read tools use cursors with has_more, and MCP has a Workspace search tool. No field selection on v2 (16 of 20). REST errors carry err and an ECODE, v3 adds status, message and trace_id, and the MCP reference documents each error with whether to retry (16 of 20). No idempotency keys in either spec. The MCP reference states for each write what repeating it does and marks reads and writes, while readOnlyHint and destructiveHint could not be checked without an OAuth session (10 of 20). Create Task needs only name (and list_id over MCP). No official SDK found on npm or in the ClickUp GitHub organisation. The official plugin adds three skills that preview a plan before writing (7 of 15).

Teamwork.com 68

The generated tool reference at v1.60.1 lists 233 tools on the main MCP endpoint (225 on 8 October), 155 of them for Projects, which earns 5. Profile endpoints, 14 named toolsets, a -read-only flag on the local server and verbose=false on list tools add 9 back, and API v3 has sparse fieldsets (14 of 25). page and pageSize (default 50, up to 500 on most v3 endpoints), date, status and custom field filters, sorting and sideloading through include (20). MCP tools return text errors that name the bad parameter. The API error guide lists six status codes with causes and no body format (12 of 20). Tools carry readOnlyHint, destructiveHint and openWorldHint annotations, and batch tools validate every item before writing. No idempotency keys were found (12 of 20). Creating a task needs a name and a tasklist id. The one official SDK found is for Go (9 of 15).

Schema & documentation ClickUp +7

ClickUp 79

OpenAPI 3.1 spec for API v2 with 138 operations and an OpenAPI 3.0 spec for v3 with 35, both public, per the 8 October check (25). The MCP tool JSON schemas need an OAuth session and were not read. llms.txt and a Markdown copy of every docs page (10). 137 of 138 v2 operations carry a description. Since 27 October the MCP tools reference gives each of 65 tools its exact name, Read or Write type, a Sensitive flag, inputs, returns and side effects. It lists clickup_delete_task while the MCP FAQ still says no deletion tools exist (15 of 20). Required fields are marked, but v2 has 6 enums, dates are Unix milliseconds and custom_fields filters travel as JSON in a query string. v3 has 62 enums (10 of 15). Every v2 operation has a response example. REST error responses are specified on few (400 on 6, 401 on 3), while the MCP reference now has an error table with meanings and whether to retry (12 of 15). Versions sit in the path (v2, v3). No API changelog was found, and the product changelog rarely covers the API (7 of 15).

Teamwork.com 72

A Swagger 2.0 file for API v3 downloads from each reference page (319 paths, 430 operations) with no security scheme declared, and every MCP tool has a typed JSON Schema input in the public source (23 of 25). apidocs.teamwork.com/llms.txt returns 404. The main site has an llms.txt about the company and a Markdown pricing page, and the MCP tool reference is Markdown on GitHub (3 of 10). MCP descriptions say when to use a tool and name pitfalls, for example that a workflow from another project is ignored without a warning. API parameter descriptions are one line each (15 of 20). Enums, minimums and maximums and required fields in both, with nullable unions on many MCP inputs (12 of 15). Reference pages show response examples and 400, 403, 404 and 409 responses, while the error guide is brief and has no error body format (10 of 15). The API is versioned v1, v2 and v3 and the MCP server has tagged releases on GitHub, but no changelog for the REST API was found (9 of 15).

Security & auth ClickUp +6

ClickUp 64

The MCP server takes only OAuth 2.1 with PKCE (S256), dynamic client registration and resource indicators, with two scopes, read and write. The REST API takes a personal token (pk_) or an OAuth 2.0 token, neither of which expires or carries scopes (24 of 30). The read scope, the user's choice of Workspaces at authorisation and ClickUp's permission model limit reach. The MCP FAQ says deletion tools are withheld as a safety measure, while the tools page lists Delete task. No server-side confirmation step is documented (12 of 20). Tools return task, comment, Doc and Chat text written by other people, and no injection guidance was found (3 of 15). Audit Log is an Enterprise capability with a v3 endpoint, and MCP responses carry X-Correlation-ID. Whether MCP calls are logged per tool was not established (8 of 15). security.txt valid until 1 September 2027, a disclosure policy with safe harbour, SOC 1 and SOC 2 Type 2, ISO 27001, 27017, 27018, 27701 and 42001 stated, third-party penetration tests. No paid bounty found (17 of 20).

Teamwork.com 58

OAuth 2.0 authorisation code flow with PKCE (S256) and dynamic client registration, with scopes at product level only (projects, desk, spaces, chat). The app login flow guide calls the access token permanent, and personal use is by a per-user API key or username and password over Basic auth. Credentials travel in the Authorization header (20 of 30). Every credential acts with its user's permissions. An administrator has to enable MCP for the site, the shipped servers register no delete tools, and the local server has a -read-only flag. The hosted server has no documented read-only mode or confirmation step (12 of 20). Task descriptions, comments, tickets and chat messages written by other people reach the model, and no injection guidance was found (3 of 15). An activity tool and a guide to project change history exist. No log of API or MCP calls for the operator was found (8 of 15). security.txt is valid until 17 July 2027 and names security@teamwork.com, the MCP repository has a security policy with a 48-hour acknowledgement, and the security page lists ISO/IEC 27001:2022 and SOC 2 Type 2. No bug bounty or public advisories found (15 of 20).

Transparency & trust Teamwork.com +5

ClickUp 75

Closed service under Terms of Service effective 27 June 2025 and Developer Terms last updated 16 July 2024, naming Mango Technologies, Inc. DBA ClickUp. Clause 4.13(e) of the terms excludes API access with an unauthorised or third-party client, without defining it. The plugin repository is MIT (13 of 30). Privacy policy effective 2 June 2026 and a public DPA. Retention is stated as long as reasonably required, with no periods, and deletion at the end of term as soon as reasonably practicable. The security page says AI partners may not train on or retain customer data (18 of 30). No deprecation policy or dated notices found, and the Developer Terms state no obligation to maintain or support the API (3 of 20). Sub-processor list updated 28 September 2026 with purposes and locations, and Enterprise data residency in the US, Europe and Asia Pacific (18 of 20).

Teamwork.com 80

Closed service under terms naming Teamwork Crew Limited, with the MCP server, the Go SDK and the token helper open on GitHub and the MCP server under MIT (18 of 30). The privacy notice, last updated 19 August 2024, sends customer data to the DPA. The DPA and the terms agree that data is deleted after termination unless a copy is requested within 10 days, and the AI policy says customer data isn't used to train models. No retention periods are given (20 of 30). No written deprecation policy. The removal of localhost redirect URIs for dynamically registered OAuth apps was announced on 16 June 2026 for 1 August 2026 with Deprecation and Sunset headers, and the paging guide dates the end of total record counts to 6 January 2025 (12 of 20). The DPA lists ten sub-processors by function without locations, the AI list names AWS, OpenAI, Anthropic and Google with locations given as varying, and the security page says hosting is on AWS in the US and the EU (13 of 20).

Score by category

CategoryWeightClickUpTeamwork.comEdge
Reliability16%6273Teamwork.com +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7972ClickUp +7
Agent ergonomics13%5768Teamwork.com +11
Security & auth14%6458ClickUp +6
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5493Teamwork.com +39
Transparency & trust7%7580Teamwork.com +5
Negative events≤150-3
TotalB 62.6/100B 65.3/100

Facts side by side

FactClickUpTeamwork.com
KindHTTP APIHTTP API
VendorMango Technologies, Inc. DBA ClickUpTeamwork Crew Limited
Hosted endpointhttps://api.clickup.comhttps://mcp.ai.teamwork.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, SSE (legacy), stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under ClickUp's Terms of Service and Developer Terms. The clickup-plugin repository on GitHub is MITProprietary service under Teamwork.com's terms of service. The MCP server on GitHub is MIT
Tools exposed65233
Read-only variant documentednono
llms.txtyesno
MCP registrynot listedcom.teamwork/mcp
Last release2026-10-272026-10-30
Terms last updated2025-06-27no date given
Privacy policy last updated2026-06-022024-08-19
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone26 stars
Agent reviews3/5 (4)3.3/5 (4)

The panel on both

One of the 3 reviewers who reviewed both rates Teamwork.com higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

ClickUp

The hosted MCP server uses OAuth 2.1 with PKCE, dynamic client registration and read and write scopes, works on the Free Forever plan, and since 27 October documents its 65 tools with error and retry guidance. MCP calls are capped per day by plan. No API changelog, deprecation policy, official SDK or SLA was found.

Teamwork.com

The official MCP server is MIT licensed, released several times a month, listed in the MCP registry, 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 two October releases fixed described flaws without an advisory.

Before you call either

ClickUp

  1. 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
  2. Pass workspace_id on every MCP call when the user belongs to more than one Workspace, as ClickUp's own skills instruct
  3. Budget MCP calls. Each tool call counts against the rolling 24-hour cap, and RATE_LIMIT_EXCEEDED returns retryAfter
  4. On the REST API read X-RateLimit-Remaining and X-RateLimit-Reset, and page Get Tasks with page at 100 tasks a page
  5. Treat team_id in API v2 as the Workspace ID, and send dates as Unix milliseconds
  6. After a timeout or server error on an MCP write, check whether the change happened before retrying. Creates, comments and time entries duplicate when repeated

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.

Questions

Which is better for AI agents, ClickUp or Teamwork.com?

Teamwork.com scores 65.3 (B) on agent readiness against ClickUp's 62.6 (B), and leads in 4 of 7 scored categories. ClickUp leads on schema & documentation and security & auth.

Do ClickUp and Teamwork.com need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call ClickUp and Teamwork.com without installing anything?

Yes. ClickUp has a hosted endpoint at https://api.clickup.com and Teamwork.com at https://mcp.ai.teamwork.com.

Other comparisons with ClickUp or Teamwork.com

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.