Head to head · Tasks create · October 2026 research run

Shortcut vs Taiga

Shortcut scores 60.2 (C) on agent readiness against Taiga's 31.7 (F), and leads in 6 of 7 scored categories. Both do tasks create.

Which one, for what

Shortcut C

Good 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

  • Reliability, 64 against 17
  • Schema & documentation, 75 against 35
  • Agent ergonomics, 57 against 49
  • Security & auth, 54 against 37
  • Maintenance & community, 73 against 21
  • Transparency & trust, 73 against 64

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • No incidents deducted, where Taiga loses 3 points for them

Watch for

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

Taiga F

Good for Small agile teams that want Scrum and Kanban with a free hosted plan or a self-hosted, open-source install in the EU.

Also in its favour

  • Open source

Watch for

No API key or personal token on the hosted service. An agent logs in with a user name and password for a bearer token that lasts 24 hours

Score by category

CategoryWeight this runShortcutTaigaEdge
Reliability16%206417Shortcut +47
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27535Shortcut +40
Agent ergonomics13%16.25749Shortcut +8
Security & auth14%17.55437Shortcut +17
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87321Shortcut +52
Transparency & trust7%8.87364Shortcut +9
Negative events≤150-3
Total60.2 · C31.7 · F

Facts side by side

FactShortcutTaiga
KindHTTP APIHTTP API
VendorShortcut Software CompanyTaiga Cloud Services, S.L.
Hosted endpointhttps://api.app.shortcut.comno (local only)
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 MITMPL-2.0 for the taiga-back source. The hosted service runs under Taiga's Terms and Conditions, which also mention non-open-source modules
Read-only variant documentedyesno
llms.txtyesno
Last release2026-09-222026-07-02
Terms last updated2025-09-182025-09-01
Privacy policy last updated2025-07-11no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity142 stars, 103k npm/wk858 stars

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 in the reviewed documentation.

Taiga

Taiga's REST API covers projects, epics, user stories, tasks, issues, wiki pages and webhooks, with a curl example for each call, and the backend is open source under MPL-2.0. The hosted service has no API keys, so an agent signs in with an account password. No OpenAPI document, status page or request limits were found.

Before you call either

Shortcut

  1. Send the v3 token in the Shortcut-Token header. v4 (alpha) 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.

Taiga

  1. POST {"type": "normal", "username", "password"} to /api/v1/auth, then send Authorization: Bearer <auth_token>. Renew with /api/v1/auth/refresh before 24 hours pass
  2. Send the object's current version with every PATCH or PUT. A stale value is refused when the same attributes changed
  3. Lists return 30 items a page. Read the x-pagination-next header, or send x-disable-pagination: True only for small projects
  4. Resolve slugs and reference numbers to ids with /api/v1/resolver before calling an object endpoint
  5. Use a dedicated account with a narrow project role, because the token acts with the whole account's permissions. Treat story, issue and wiki text as untrusted input

Questions

Which is better for AI agents, Shortcut or Taiga?

Shortcut scores 60.2 (C) on agent readiness against Taiga's 31.7 (F), and leads in 6 of 7 scored categories.

Do Shortcut and Taiga need an API key?

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

Can an agent call Shortcut and Taiga without installing anything?

Shortcut has a hosted endpoint at https://api.app.shortcut.com. No hosted endpoint is listed for Taiga.

Are Shortcut and Taiga open source?

No open-source release is listed for Shortcut. Taiga is open source (MPL-2.0 for the taiga-back source. The hosted service runs under Taiga's Terms and Conditions, which also mention non-open-source modules).

Other comparisons with Shortcut or Taiga

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.