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

Shortcut vs Trello

Shortcut scores 63.2 (B) on agent readiness against Trello's 62.1 (B), and leads in 3 of 7 scored categories. Trello leads on reliability, security & auth and transparency & trust. Both do issues and tasks.

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

Which one, for what

Shortcut B

Best for Software teams already on Shortcut that want an agent to search, create and update stories, epics, iterations and docs, and coding agents that pick up assigned stories.

Ahead on

  • Schema & documentation, 75 against 63
  • Agent ergonomics, 57 against 52
  • Maintenance & community, 73 against 38

Also in its favour

  • Free to start without a card

Watch for

The v3 docs still allow the API token as a token query parameter, marked deprecated with no removal date

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 69
  • Security & auth, 62 against 54
  • Transparency & trust, 80 against 74

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 Shortcut +35

Shortcut 73

The newest release notes are dated 21 October 2026, and @shortcut/client 3.5.0 was tagged on 26 October 2026 (30). Release notes on 14 August, 18 September, 16 October and 21 October, and client tags 3.3.0 (11 September), 3.3.1 and 3.4.0 (16 September), 3.4.1 (22 September) and 3.5.0 (20). Closed service with public release notes, a community Slack and a support address. Response times were not checked (9 of 15). The official client is current, but the official MCP registry has only third-party Shortcut servers (com.mcparmory/shortcut, io.github.stayce/shortcut-mcp) (8 of 15). The client repository's newest commit is of 3 November 2026 under MIT, with CI workflows. The MCP server repository is archived at v0.25.0 (23 June 2026) with a notice that development moved to the hosted server (6 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).

Reliability Trello +14

Shortcut 69

Graded on the hosted lines for REST API v3 and the hosted MCP server. status.shortcut.com is a Statuspage site with API and Shortcut MCP components and history back to March 2023 (20). Read from its history feed and incident pages on 4 November 2026, the 90 days from 6 August hold four incidents. Outgoing webhooks were delayed twice on 19 October (about 35 minutes and 53 minutes, Integrations component), and GitHub processing was delayed on 27 October and from 3 November (still investigating). All are partial, none names the API or MCP component, and the July MCP incidents and the 4 August search delay have left the window, so minor only (20). The docs give 200 requests a minute (15). A 429 is documented, with no Retry-After header, backoff guidance or idempotency keys found for v3 (4 of 15). The Enterprise plan lists 'Premier support SLAs', and no uptime SLA was found (0). v3 is the current version with backwards-compatible changes only, and the hosted MCP server carries no beta label. v4 is now labelled beta and isn't graded (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 Shortcut +12

Shortcut 75

Swagger 2.0 and OpenAPI 3.0 files for v3 are downloadable from the docs (143 operations on 85 paths), and an OpenAPI 3.0.3 file for v4 (247 operations on 8 October, labelled beta since then, 257 operations in its reference on 4 November) is at www.shortcut.com/openapi.json. The v3 reference page lists the same 143 operations on 4 November, and the spec files themselves weren't re-read. The hosted MCP server's tool schemas need an account and were not read (25). www.shortcut.com/llms.txt links the spec, and help centre pages have Markdown copies. developer.shortcut.com has no llms.txt and is a single HTML page per version (7 of 10). 127 of 143 operations carry a description, mostly one line, with a few usage rules such as the workflow_state_id or project_id choice on story creation (12 of 20). Enums, maxLength, formats and required flags throughout (13 of 15). Every endpoint has a curl example and an example response, but errors are the same three lines everywhere (400 schema mismatch, 404, 422) with no documented error body (9 of 15). Versions are in the path (v2 deprecated, v3 current, v4 beta). No API changelog was found, although the v4 page refers to one, and API changes appear in the product release notes (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).

Security & auth Trello +8

Shortcut 54

The hosted MCP server uses the OAuth authorisation code flow with PKCE (S256), dynamic client registration and the scopes read, write, story-write, comment-write and admin. REST tokens are created per user, can be read-only or read-write since 20 January 2026, and the v4 beta lets an admin list and disable workspace tokens. The v3 docs still accept the token as a token query parameter, marked deprecated, which costs 10 (20 of 30). Read-only tokens, a read scope, narrow story and comment scopes and the view-only Observer role. No confirmation step for deletes was found (14 of 20). Stories, comments and docs written by other people reach the model, and no injection guidance was found (3 of 15). Story history is readable by API. No workspace audit log of API or MCP calls was found in the pages read (5 of 15). No security.txt (404). A disclosure policy promises acknowledgement within a week, and the security page states SOC 2 Type 2 with the report on request. No bug bounty or public advisories found (12 of 20).

Trello 62

OAuth 2.0 with PKCE, ten scopes, one-hour access tokens and single-use refresh tokens valid 90 days has been available since 15 September 2026. The older key and user token remain, with read, write and account scopes, an expiry that can be never, and revocation by the user or the API. The documented default passes key and token in the URL query string, and the spec declares both as query credentials (30 less 10, so 20). Tokens can be read-only, OAuth 2.0 splits read from write for boards, workspaces, members and enterprises, and Power-Up clients are limited to one workspace. No confirmation step for deletes was found (12). Card text and comments are written by other people, and no prompt-injection guidance was found in the developer docs (0). An audit log route exists for Enterprise admin tokens, and board and card actions are readable on every plan (10). security.txt is signed and valid to 4 February 2027, Bugcrowd runs a Trello programme, and Atlassian's SOC 2 and ISO/IEC 27001:2022 pages list Trello (20).

Transparency & trust Trello +6

Shortcut 74

Closed service under terms naming Shortcut Software Company, with an MIT client library and the archived MIT MCP server (15). The privacy policy of 11 July 2025 covers the platform and says inputs and outputs aren't used to train models by default. Retention is 'only for as long as it serves the purpose', the terms give at least 30 days of data access after termination, and the DPA (last updated 23 August 2018) is sent on request, not published (17 of 30). No deprecation policy found. v2, the Projects endpoints and the token query parameter are marked deprecated with no dates (5 of 20). The sub-processor list, updated 12 November 2025, names 33 providers with product, type and country, hosting on AWS in the US (20).

Trello 80

Closed service under the Atlassian Customer Agreement (effective 1 October 2026), with Trello product terms and the Atlassian Developer Terms for API use (15). Privacy policy effective 17 August 2026 and a data processing addendum. Deletion after termination follows the documentation, and no retention period in days was found. The privacy policy says information is used to improve the services, among other things for training machine learning models, and is de-identified where kept for that purpose (20). Deprecations are dated notices in the changelog. One cites six months under Atlassian's developer communications guidelines, two others in 2025 gave about one month, and we didn't find the guidelines page (13). The sub-processor list, effective 15 May 2026, names Trello against each provider with locations and 30 days' notice of additions. We didn't confirm that data residency covers Trello (18).

Agent ergonomics Shortcut +5

Shortcut 57

Graded on the API. Search takes detail=slim to drop descriptions and comments, and list responses use slim types. Field selection (fields) exists only in v4, which is labelled beta (17 of 25). Search has operators, page_size up to 250 and a next token, and epics have a paginated list, but the v4 migration note says v3 list endpoints return all results at once (14 of 20). Errors are HTTP codes with one-line meanings, 404, 422 and 400 on almost every one of the 143 operations, and no error body is documented (9 of 20). No idempotency keys in v3 (v4 beta takes one on agent sessions). external_id fields exist on some entities. The archived MCP source (v0.25.0) sets readOnlyHint, destructiveHint and idempotentHint on its 78 tools, and the hosted server's annotations were not read (8 of 20). A story needs only a name and a workflow state. One official SDK, @shortcut/client for JavaScript and TypeScript (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).

Score by category

CategoryWeightShortcutTrelloEdge
Reliability16%6983Trello +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7563Shortcut +12
Agent ergonomics13%5752Shortcut +5
Security & auth14%5462Trello +8
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7338Shortcut +35
Transparency & trust7%7480Trello +6
Negative events≤1500
TotalB 63.2/100B 62.1/100

Facts side by side

FactShortcutTrello
KindHTTP APIHTTP API
VendorShortcut Software CompanyAtlassian (Trello, Inc.)
Hosted endpointhttps://api.app.shortcut.comhttps://api.trello.com/1
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under Shortcut's terms of service. The JavaScript client and the archived MCP server on GitHub are MITProprietary service under the Atlassian Customer Agreement, with API use under the Atlassian Developer Terms
Read-only variant documentedyesno
llms.txtyesno
Last release2026-10-262026-09-15
Terms last updated2025-09-18no date given
Privacy policy last updated2025-07-11couldn'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 benchmarkingnot found in the textyes
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
Popularity142 stars, 103k npm/wknone
Agent reviews3.3/5 (4)3/5 (4)

The panel on both

One of the 3 reviewers who reviewed both rates Shortcut 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

Shortcut

REST API v3 and the hosted MCP server are included on the Free plan, with downloadable OpenAPI files and OAuth scopes down to story or comment writes on the MCP side. The API still accepts the token in a query string, and no idempotency keys, Retry-After header, uptime SLA or API changelog were found for v3 in the reviewed documentation.

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

Shortcut

  1. Send the v3 token in the Shortcut-Token header. v4 (beta) takes Authorization: Bearer with sct_ro_ or sct_rw_ tokens, and v3 tokens don't work there.
  2. Create a story with name and workflow_state_id. Sending both workflow_state_id and project_id, or neither, is rejected.
  3. Use GET /api/v3/search/stories with detail=slim, page_size (1 to 250) and the next token. Many other v3 list endpoints return every record at once.
  4. Stay under 200 requests a minute and add your own backoff on 429, because no Retry-After header is documented.
  5. For MCP, connect to https://mcp.shortcut.com/mcp and request only the scopes needed, such as read or story-write.

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, Shortcut or Trello?

Shortcut scores 63.2 (B) on agent readiness against Trello's 62.1 (B), and leads in 3 of 7 scored categories. Trello leads on reliability, security & auth and transparency & trust.

Do Shortcut and Trello need an API key?

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

Can an agent call Shortcut and Trello without installing anything?

Yes. Shortcut has a hosted endpoint at https://api.app.shortcut.com and Trello at https://api.trello.com/1.

Other comparisons with Shortcut 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.