# ONES vs Trello (slim)

> Trello scores 60.2 (C) to ONES's 46.9 (D) for issues and tasks. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/ones-vs-trello.md (~4,450 tokens) · this version ~2,530 tokens · JSON https://www.anchorterminal.com/compare/ones-vs-trello.json · canonical https://www.anchorterminal.com/compare/ones-vs-trello
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Trello scores 60.2 (C) on agent readiness against ONES's 46.9 (D), and leads in 4 of 7 scored categories. ONES leads on maintenance & community. Both do issues and tasks.

- ONES: D 46.9, rank #1164 of 1510 · https://www.anchorterminal.com/tools/ones.min.md
- Trello: C 60.2, rank #661 of 1510 · https://www.anchorterminal.com/tools/trello.min.md
- ONES, good for Teams moving off Jira and Confluence who want issues, sprints, worklogs, test cases and a wiki in one tool an agent can reach. Ahead on Maintenance & community, 68 against 38. Also Free to start without a card.
- Trello, good 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 25; Schema & documentation, 63 against 55; Agent ergonomics, 52 against 40; Transparency & trust, 80 against 62.

| Category | ONES | Trello |
| --- | --- | --- |
| Reliability (16%) | 25 | 83 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 55 | 63 |
| Agent ergonomics (13%) | 40 | 52 |
| Security & auth (14%) | 65 | 62 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 68 | 38 |
| Transparency & trust (7%) | 62 | 80 |

| Fact (where they differ) | ONES | Trello |
| --- | --- | --- |
| Vendor | The Beautiful ONES Technology PTE. LTD. | Atlassian (Trello, Inc.) |
| Hosted endpoint | `https://us.ones.com/mcp` | `https://api.trello.com/1` |
| Transports | Streamable HTTP | HTTP |
| Licence | none | Proprietary service under the Atlassian Customer Agreement, with API use under the Atlassian Developer Terms |
| Tools exposed | 67 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| MCP registry | `com.ones/ones` | not listed |
| Last release | 2026-09-30 | 2026-09-15 |
| Terms last updated | 2025-09-08 | no date given |
| Privacy policy last updated | 2026-01-07 | couldn't be read |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Reliability, Trello +58: ONES 25 (Graded as a hosted service on ONES.com Cloud's Open API and MCP server. No status page is linked from ones.com, the trust centre or the docs, and status.ones.com did not resolve (0). With no readable history the incident line scores 5. No rate limit with numbers was found in the developer docs index or the terms, which only reserve the right to restrict excessive traffic (0). No 429, backoff or idempotency guidance found (0). The pricing page states 99.9% uptime on Business and 99.95% on Enterprise (10). The MCP server has been in the release notes since 6.42.0 on 26 August 2025 and carries no beta label (10). 0 + 5 + 0 + 0 + 10 + 10 = 25.); 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).)
- Maintenance & community, ONES +30: ONES 68 (Latest dated release notes are 7.33.0 on 30 September 2026, 37 days before this check. The registry entry moved to 1.0.3 on 8 October with no release note behind it, so it doesn't set recency (20). Nine dated releases since 8 August, several adding Open API endpoints or MCP capabilities (7.23.0, 7.26.0, 7.27.0, 7.29.0) (20). Closed service with a public changelog and support by email, with no public issue tracker (8 of 15). Verified com.ones/ones namespace in the official MCP registry (15). One official SDK for apps, with package health not checked (5 of 10). 20 + 20 + 8 + 15 + 5 = 68.); 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).)
- Transparency & trust, Trello +18: ONES 62 (Closed service under terms naming The Beautiful ONES Technology PTE. LTD. and Singapore law (15 of 30). The privacy policy of 7 January 2026 deletes business data 30 days after a service ends with no login for 365 days, and honours deletion requests within 30 days, but no DPA or subprocessor list is public (12 of 30). Endpoint version histories record changes, with no deprecation policy (5 of 20). The privacy policy names AWS, Oracle cloud and OpenAI and says data is transferred mostly to the US, China and Singapore, with no subprocessor list or regions (6 of 20). 15 + 12 + 5 + 6 = 38.); 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, Trello +12: ONES 40 (Scored on the MCP server and the Open API together. 67 MCP tools load by default (5), and a client granted fewer scope groups is limited to fewer tools (5 back). Lists take `limit` and `cursor` with project and issue type filters, and `query_issues_by_onesql` runs a filtered query (15 of 20). Error status codes are documented per endpoint with response schemas, but no error code catalogue was found (8 of 20). No idempotency keys or MCP annotations found (0). One official SDK, `@ones-open/node-sdk`, aimed at ONES Apps, and the MCP setup is one `mcp-remote` line (7 of 15). 10 + 15 + 8 + 0 + 7 = 40.); 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).)
- Schema & documentation, Trello +8: ONES 55 (No downloadable OpenAPI file was found. The reference is rendered pages, and the MCP docs list tool names and one-line descriptions without input schemas (0). llms.txt with sized indexes and a Markdown copy of every page (10). Endpoint and tool descriptions state what each does in one line, with version history per endpoint but little on when not to use one (10 of 20). Parameters are typed with defaults, limits (`limit` at most 100) and required marks (10 of 15). Each endpoint lists 200, 401, 403, 404 and 500 responses with schemas and examples (10 of 15). API version 2.0, a History table per endpoint and dated release notes (15). 0 + 10 + 10 + 10 + 10 + 15 = 55.); 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).)