# Roma vs Taskade (slim)

> Taskade scores 57.7 (C) to Roma's 48.7 (D) for issues and tasks. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/roma-vs-taskade.md (~4,300 tokens) · this version ~2,330 tokens · JSON https://www.anchorterminal.com/compare/roma-vs-taskade.json · canonical https://www.anchorterminal.com/compare/roma-vs-taskade
- 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)

Taskade scores 57.7 (C) on agent readiness against Roma's 48.7 (D), and leads in 5 of 7 scored categories. Both do issues and tasks.

- Roma: D 48.7, rank #1119 of 1510 · https://www.anchorterminal.com/tools/roma.min.md
- Taskade: C 57.7, rank #783 of 1510 · https://www.anchorterminal.com/tools/taskade.min.md
- Roma, good for One person, or a few people sharing lists, who want an AI chat to read and write their tasks, notes and typed lists, with a single orientation call and change events for a worker agent.
- Taskade, good for Small teams that keep projects, tasks and AI agents in one workspace and want an agent to read and change them. Ahead on Schema & documentation, 91 against 83; Agent ergonomics, 68 against 60; Maintenance & community, 85 against 57; Transparency & trust, 69 against 60. Also Runs on your own machine; Free to start without a card; No incidents deducted, where Roma loses 3 points for them.

| Category | Roma | Taskade |
| --- | --- | --- |
| Reliability (16%) | 40 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 91 |
| Agent ergonomics (13%) | 60 | 68 |
| Security & auth (14%) | 44 | 45 |
| Payments & pricing (10%) | 20 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 57 | 85 |
| Transparency & trust (7%) | 60 | 69 |

| Fact (where they differ) | Roma | Taskade |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Milo Mode Inc. | Taskcade Inc. |
| Hosted endpoint | `https://api.roma.app/mcp` | `https://www.taskade.com/mcp` |
| Transports | Streamable HTTP, HTTP | Streamable HTTP, stdio |
| Pricing | Free | Freemium |
| Licence | Proprietary service under Roma's terms of service. No public source repository found | none |
| Tools exposed | 32 | 47 |
| Read-only variant documented | yes | no |
| MCP registry | not listed | `io.github.taskade/mcp-server` |
| Last release | 2026-10-28 | 2026-11-05 |
| Terms last updated | 2026-09-18 | 2026-09-30 |
| Privacy policy last updated | 2026-10-06 | 2026-10-26 |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |

Why the edge:
- Maintenance & community, Taskade +28: Roma 57 (The MCP changelog's newest entry is 28 October 2026, seven days before this check (30). Ten dated MCP changelog entries in the 90 days from 6 August (13 and 14 August, 4, 18, 23 and 30 September, 2, 13, 26 and 28 October 2026), and a weekly product changelog, newest 3 November 2026 (20). Support is an email address, hello@roma.app, with accounts on X and LinkedIn. No forum, issue tracker or public repository was found, so replies could not be read (7). No readable official MCP registry page names Roma, and no SDKs (0). No public packages or CI to assess (0).); Taskade 85 (Changelog v6.306.0 on 5 November 2026, and v6.304.0 on 4 November updated the MCP setup page (30). Fifteen entries between 29 October and 5 November alone, and @taskade/mcp-server 0.1.3 (19 October) and 0.1.4 (22 October) (20). The taskade/mcp repository merged pull requests #114 to #122 between 26 October and 4 November; GitHub's API did not answer, so open issues and reply times were not counted (15 of 25). Verified io.github.taskade/mcp-server namespace in the official MCP registry, with the hosted remote (15). CI, release and registry-publish workflows, and the Docker image moved off end-of-life Node 20 on 28 October (5 of 10, with dependency health not checked). 30 + 20 + 15 + 15 + 5 = 85.)
- Transparency & trust, Taskade +9: Roma 60 (Closed source with published terms of 13 short clauses, last updated 15 October 2026. They name Milo Mode Inc. in the United States without an address or state, and have no API-specific terms (13). The privacy policy (15 October 2026) gives retention periods of 14 days for assistant request records, up to 30 days for hosting logs, up to 90 days for database and sign-in logs and about 30 days in the trash, which agrees with the developer docs. It says Roma doesn't train AI models on user data and that OpenAI processes content under its API terms. No DPA was found (22). No deprecation policy. The changelog dates each change, but the 13 October retirement of 24 tools and five REST routes came with no notice period (3). Twelve service providers are named with their purposes. Data location is given only as the United States and other countries (14).); Taskade 69 (Closed service under terms naming Taskcade Inc. and Delaware law, with the MCP server, plugin and OpenAPI specs under MIT (20 of 30). The privacy policy gives practices for retention (AI processing logs normally 30 days, account deletion within 30 days) but calls them targets, not contractual periods, and no DPA or SCCs are offered (15 of 30). Deprecated endpoints are marked in the docs and spec with their replacement, with no deprecation policy or dates (8 of 20). Hosting is AWS US East, and AI providers are named as examples, some in China, with the full list on request; analytics tools (Google Analytics, PostHog, Plausible, Sentry) are named (12 of 20). 20 + 15 + 8 + 12 = 55.)
- Schema & documentation, Taskade +8: Roma 83 (The generated tool reference gives every one of the 32 MCP tools typed parameters with required flags and a result shape, and the REST API page links an OpenAPI document for its 39 operations at api.roma.app/api/v1/openapi.json (the file per the 8 October check, not re-read on 4 November). A live `tools/list` needs an account (25). llms.txt, llms-full.txt and a Markdown copy of every docs page (10). Descriptions say what a tool is for, when to call it and in several cases when not to, such as `get_item` being the call to show one item and `run_automation` only on the person's request (17). Enums for status stages, sort, mode and kind, length and item limits, and required fields. Ids and timestamps are plain strings with no format, and filter clauses and property values are open objects (11). Each tool has an example call, but most pass empty or placeholder arguments. Six error codes and five statuses are documented (8). The REST path is versioned as v1 and the MCP changelog is dated, newest 28 October 2026. Its 13 October entry retired 24 tools with no alias on the day (12).); Taskade 91 (OpenAPI 3.0.3 specs for REST v1 and Action v2 are linked from llms.txt and committed in the public taskade/mcp repository, which is where we read them because the site's /api/ path is disallowed in robots.txt (25). llms.txt, a developer docs index and a Markdown copy of each page (10). The hosted MCP docs say what each tool does, which role it needs and what the server cannot do; the v2 spec's operations carry no descriptions of their own (14 of 20). The v1 spec has 96 enums and 254 required lists (13 of 15). Error tables with causes and fixes on the MCP and API pages, and a documented error envelope (14 of 15). Versioned APIs (1.0.0, 2.0.0-beta), deprecations marked in the spec and a changelog updated almost daily (15). 25 + 10 + 14 + 13 + 14 + 15 = 91.)
- Agent ergonomics, Taskade +8: Roma 60 (32 MCP tools load at once, which scores 5 for more than 30. No toolsets or read-only subset on the server, so nothing added back (5). `limit` on the list tools, time windows, status filters and `sort` on `list_items`, `offset` paging with count and sum modes on `query_items`, and since 13 October a `changedSince` cursor with `hasMore` and deletions as tombstones. `list_items` without the cursor still stops at 200 rows and `search` at 20 with no paging, so the line is still partly met. The earlier partial is kept (14). Errors are one sentence saying what to change, with six REST codes and `isError: true` on MCP (16). Every tool carries a badge (16 read-only, 5 adding data, 11 updating or removing), 10 are marked safe to retry, and `externalId` and `matchOn` guard `create_items`. `create_list`, `create_expert` and `create_image_upload` have no idempotency key (17). An item needs only a title, body writes append by default and `get_context` orients a session in one call. No SDK in any language (8).); Taskade 68 (47 hosted MCP tools are listed (5), with `inspect_space` line ranges and cursor pagination to size reads (3 back). Cursor pagination on list tools and a paginated, plan-filtered `list_spaces`, with few filters (15 of 20). MCP tool errors return `class`, `code`, `retry` and `retryAfterSec`, and invalid arguments come back as a tool result the model can correct (20). Every tool states readOnlyHint, destructiveHint and openWorldHint, and `_meta` flags mark writes and billed calls; no idempotency keys for creates were found (18 of 20). Setup is one URL with OAuth; the TypeScript SDK is in preview and not on npm, and no second official SDK exists (7 of 15). 8 + 15 + 20 + 18 + 7 = 68.)