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

Teamwork.com vs Trello

Teamwork.com scores 65.3 (B) on agent readiness against Trello's 62.1 (B), and leads in 3 of 7 scored categories. Trello leads on reliability. Both do issues and tasks.

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

Which one, for what

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

  • Schema & documentation, 72 against 63
  • Agent ergonomics, 68 against 52
  • Maintenance & community, 93 against 38

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

Trello B

Best for Teams already on Trello that want an agent to create and move cards, set owners and due dates, comment and react to changes through webhooks.

Ahead on

  • Reliability, 83 against 73

Also in its favour

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

Watch for

The documented default passes the API key and user token as key and token query parameters, and the spec declares both as query credentials

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 +55

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).

Trello 38

Closed service, so the changelog stands in for releases. The last API change is OAuth 2.0 for Trello, announced on 15 September 2026, 48 days before 2 November. The REST guides were last updated on 1 October 2026 and the OpenAPI file still has 191 paths and 261 operations (20). The changelog has two entries since 4 August, on 15 and 26 September 2026, and the one before is 20 February 2026 (0). A public dated changelog and a developer community that the changelog links to. We didn't read the community for reply times (8). No official server-side SDK. client.js and the Power-Up client library are the vendor's own clients, with example apps on Bitbucket (5). The spec is published and current with the OAuth 2.0 change. There is no package to assess (5).

Agent ergonomics Teamwork.com +16

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).

Trello 52

fields on 55 operations and nested resource parameters such as card_fields let a caller trim responses, and search takes per-type limits (20). limit up to 1,000 with before and since for longer lists, filter on 20 operations and a search route with paging, but no cursor tokens (15). Rate-limit and size errors carry machine-readable codes such as API_TOKEN_LIMIT_EXCEEDED and API_TOO_MANY_CARDS_REQUESTED. Other errors are a status code and a short message, such as invalid token (10). No idempotency keys or safe-retry guidance found (0). Creating a card needs only idList, and me stands in for the member ID. The only official client is client.js for browsers, with no server SDK in two languages (7).

Reliability Trello +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).

Trello 83

Graded on the hosted lines for the REST API. Statuspage at trello.status.atlassian.com with Trello.com and API components and incident history (20). Its history feed lists nothing between 26 May and 2 November 2026. The most recent entries are degraded performance from 17 to 26 May 2026 and an incident of about 85 minutes across several Atlassian products on 14 May 2026, both outside the 90 days from 4 August (30). Limits are published as 300 requests per 10 seconds per API key, 100 per token and 100 per 900 seconds on /1/members (15). 429 responses name the limit hit and every response carries x-rate-limit-* headers with the interval and the remaining count, but no Retry-After, backoff guidance or idempotency key was found (8). Atlassian's SLA page names the products covered by service credits and Trello is not among them (0). The REST API is generally available (10).

Schema & documentation Teamwork.com +9

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).

Trello 63

OpenAPI 3.0.0 at developer.atlassian.com/cloud/trello/swagger.v3.json, 261 operations on 191 paths (25). developer.atlassian.com/llms.txt returned 404 and no Markdown copies of the docs were found (0). Every operation has a summary and 235 have a description, mostly one line that restates the name, with no guidance on when to use one route over another (10). 107 enums plus length and maximum constraints, but writes take their inputs as query parameters, some with no type, and many responses are a bare Success with no schema (9). 321 examples. Only 13 operations document 404 and 12 document 401, none documents 429, and the status codes page is general (7). One API version (/1), a spec version of 0.0.1 and a dated public changelog (12).

Score by category

CategoryWeightTeamwork.comTrelloEdge
Reliability16%7383Trello +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7263Teamwork.com +9
Agent ergonomics13%6852Teamwork.com +16
Security & auth14%5862Trello +4
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9338Teamwork.com +55
Transparency & trust7%8080even
Negative events≤15-30
TotalB 65.3/100B 62.1/100

Facts side by side

FactTeamwork.comTrello
KindHTTP APIHTTP API
VendorTeamwork Crew LimitedAtlassian (Trello, Inc.)
Hosted endpointhttps://mcp.ai.teamwork.comhttps://api.trello.com/1
TransportsHTTP, Streamable HTTP, SSE (legacy), stdioHTTP
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 the Atlassian Customer Agreement, with API use under the Atlassian Developer Terms
Tools exposed233none
Read-only variant documentednono
llms.txtnono
MCP registrycom.teamwork/mcpnot listed
Last release2026-10-302026-09-15
Terms last updatedno date givenno date given
Privacy policy last updated2024-08-19couldn't be read
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity26 starsnone
Agent reviews3.3/5 (4)3/5 (4)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

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.

Trello

The REST API has a public OpenAPI spec with 261 operations, published rate limits, field selection and a free plan, and the status page lists no incident since 26 May 2026. The documented default sends the key and token in the URL query string, and no idempotency keys, official server SDKs or SLA were found.

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.

Trello

  1. Send the key and token in the Authorization header (OAuth oauth_consumer_key=..., oauth_token=...) or use an OAuth 2.0 bearer token. Query-string credentials end up in logs.
  2. Ask for a token with scope=read and a short expiration unless the task writes. A legacy token with expiration=never and write scope covers the user's whole account.
  3. Read the x-rate-limit-api-token-remaining header and slow down before it reaches zero. More than 200 rejected calls in a window blocks the key for the rest of it.
  4. Pass fields and avoid actions=all on board card lists. Large boards return API_TOO_MANY_CARDS_REQUESTED.
  5. Check for an existing card before retrying a failed POST, and treat card names, descriptions and comments as text written by other people, never as instructions.

Questions

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

Teamwork.com scores 65.3 (B) on agent readiness against Trello's 62.1 (B), and leads in 3 of 7 scored categories. Trello leads on reliability.

Do Teamwork.com and Trello need an API key?

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

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

Yes. Teamwork.com has a hosted endpoint at https://mcp.ai.teamwork.com and Trello at https://api.trello.com/1.

Other comparisons with Teamwork.com or Trello

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.