# Redmine vs Taskade (slim)

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

- Full: https://www.anchorterminal.com/compare/redmine-vs-taskade.md (~4,850 tokens) · this version ~2,830 tokens · JSON https://www.anchorterminal.com/compare/redmine-vs-taskade.json · canonical https://www.anchorterminal.com/compare/redmine-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 Redmine's 39.1 (E), and leads in 4 of 7 scored categories. Redmine leads on reliability, security & auth and payments & pricing. Both do issues and tasks.

- Redmine: E 39.1, rank #1328 of 1486 · https://www.anchorterminal.com/tools/redmine.min.md
- Taskade: C 57.7, rank #779 of 1486 · https://www.anchorterminal.com/tools/taskade.min.md
- Redmine, good for Teams that already run Redmine or want a free, self-hosted tracker with issues, time entries and wikis under their own control. Ahead on Reliability, 66 against 40; Security & auth, 51 against 45; Payments & pricing, 60 against 20. Also Open source.
- 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 32; Agent ergonomics, 68 against 51; Maintenance & community, 85 against 73; Transparency & trust, 69 against 52. Also A hosted endpoint, with nothing to install; Runs on your own machine; Free to start without a card; No incidents deducted, where Redmine loses 15 points for them.

| Category | Redmine | Taskade |
| --- | --- | --- |
| Reliability (16%) | 66 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 32 | 91 |
| Agent ergonomics (13%) | 51 | 68 |
| Security & auth (14%) | 51 | 45 |
| Payments & pricing (10%) | 60 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 73 | 85 |
| Transparency & trust (7%) | 52 | 69 |

| Fact (where they differ) | Redmine | Taskade |
| --- | --- | --- |
| Vendor | Redmine project | Taskcade Inc. |
| Hosted endpoint | no (local only) | `https://www.taskade.com/mcp` |
| Transports | HTTP | Streamable HTTP, stdio |
| Pricing | Free | Freemium |
| Licence | GPL-2.0-or-later | none |
| Tools exposed | none | 47 |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.taskade/mcp-server` |
| Last release | 2026-11-01 | 2026-11-05 |
| Terms last updated | no document linked | 2026-09-30 |
| Privacy policy last updated | no document linked | 2026-10-26 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | yes |

Why the edge:
- Schema & documentation, Taskade +59: Redmine 32 (No OpenAPI document or other machine-readable contract was found in the wiki or the repository (0). No llms.txt (the path returned 404) and no Markdown docs for agents (0). Each resource has a wiki page that lists its calls and parameters in a line each, with little on when to use one (9 of 20). Parameters are named with few types, and allowed values are given for only some, such as `status_id` and `include` (5 of 15). Calls have XML and JSON examples, and the 422 validation response is documented. Other error responses are not (9 of 15). The API has no version of its own. Pages note the release each call arrived in, the changelog has a REST API section, and the change history holds two entries, one of them for the unreleased 7.1.0, which also adds a Documents resource (9 of 15).); 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.)
- Payments & pricing, Redmine +40: Redmine 60 (Read with the self-hosted rule. No x402, MPP or L402 in the docs or the source (0). Redmine is free software with nothing to buy from the project (20). No trial or card is involved (20). No signup with a vendor is needed. The owner installs it and creates the key (20).); Taskade 20 (No x402, MPP or L402 (0). Plan prices are public, billed yearly, with nothing per call (10). A Free plan needs no card, but the hosted MCP server is limited to paid plans and the pricing table lists the API from Business up, so the free tier reaches little of the agent surface (10 of 20). A person signs up in a browser and verifies an email before a token can be made (0). 0 + 10 + 10 + 0 = 20.)
- Reliability, Redmine +26: Redmine 66 (Graded on the REST API of a self-hosted install, with the local-software lines. Redmine has no vendor-run cloud. Official tarballs and zip files with SHA-256 sums, and an install guide that states the supported Ruby, Rails and database versions. No official gem or container image (18 of 20, per the 9 October check for the install guide). GitHub Actions runs the 386 test files at tag 7.0.3 on four Ruby versions and three databases. The results are shown only as badge images on github.com, which we cannot read, so a public CI that runs the tests with an unreadable result takes 15 of 25. The issue tracker's lists are closed to us by robots.txt. The 7.0.3 changelog alone lists more than 20 fixed defects, which is the only evidence read (12 of 25). A release policy of quarterly minors and yearly majors, a changelog per series and an API change history (11 of 15). 7.0.x is the latest stable series, but the docs mark 17 of 23 API resources Alpha (10 of 15). 18 + 15 + 12 + 11 + 10 = 66.); Taskade 40 (Graded as a hosted service on the hosted MCP server and REST API v1. status.taskade.com is Taskade's own status portal, but it draws its data by script and no components could be read (10 of 20). No readable incident history (5). Rate limits have numbers only for `prompt_agent` (60 calls in 10 minutes) and `publish_kit_version` (5 an hour); the API docs say 429 marks a rate limit without stating it (5 of 15). The API returns 429 with Retry-After, MCP tools use `x-rate-limit-reset`, and tool errors say whether a retry is safe and after how many seconds (15). The terms commit to no uptime level without a separate written agreement, and only Enterprise mentions SLAs (0). REST API v1 is GA, while Action API v2, which most hosted MCP tools mirror, is beta (5 of 10). 10 + 5 + 5 + 15 + 0 + 5 = 40.)
- Agent ergonomics, Taskade +17: Redmine 51 (Graded on the REST API. Lists return 25 items by default and 100 at most, and related data arrives only when named in `include`. No field selection (15 of 25). `offset`, `limit` and `page` with a `total_count`, filters with operators on issues, `sort` and saved queries (17 of 20). Validation failures return 422 with a list of messages. In the source, other errors answer with a status code and an empty body (9 of 20). No idempotency keys and no retry guidance. A wiki page update with a stale version returns 409, and no equivalent is documented for issues (4 of 20). Creating an issue needs a project and a subject. No official SDK was found, and the wiki lists community clients for nine languages (6 of 15).); 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.)
- Transparency & trust, Taskade +17: Redmine 52 (The source is public under the GPL, version 2 or later (30). Data stays on the owner's server. The project publishes no statement on what an install stores or sends, and its privacy policy covers only the redmine.org website. In the source, Gravatar, which sends a hash of each email address to a third party, is off by default (17 of 30). A support policy names the three series that get fixes, and the API change history dates each breaking change. No deprecation policy with notice periods was found (10 of 20). No telemetry was found in a search of the application source, and the docs make no statement either way (12 of 20).); 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.)
- Maintenance & community, Taskade +12: Redmine 73 (Versions 7.0.3, 6.1.6 and 6.0.12 were tagged on 1 November 2026 (30). Eight releases across three series in the 90 days from 6 August, on 26 August, 30 September and 1 November (20). The master branch had 146 commits in the 30 days to 4 November 2026 and each release fixes dozens of tracked defects. The issue tracker and forums were not sampled, because robots.txt closes the issue lists, and pull requests on the GitHub mirror are not reviewed by design (14 of 25). No official SDK and no MCP server were found (0). 7.0.2 moved to Rails 8.1.4, earlier releases updated Nokogiri, and tests and linters run on Ruby 3.2 to 4.0 (9 of 10). 30 + 20 + 14 + 0 + 9 = 73.); 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.)