monday.com vs Redmine

monday.com

The GraphQL API publishes its full schema, accepts an Idempotency-Key header on mutations and reports limits in RateLimit headers, and a documented signup API lets an agent create its own account and token. Personal tokens carry every permission their user has, daily calls stop at 1,000 below Pro, and the status page shows two long platform incidents since July 2026.

Redmine

Redmine's REST API covers issues, projects, time entries and 20 other resources, and versions 6.1 and later add OAuth 2 with one scope per permission. The software is free under the GPL. No OpenAPI document exists, most errors return a bare status code, and 24 security advisories were published in twelve months, two rated critical.

monday.com

1. Send an API-Version header such as 2026-10 on every call. Without it the API uses whichever version is current
2. Read the board's columns first (get_board_info or boards { columns }), then write column values as a JSON string keyed by column ID
3. Reuse one Idempotency-Key per mutation when retrying after a timeout or 5xx. After a 429, wait for Retry-After or retry_in_seconds
4. Page items with items_page and next_items_page, at most 500 a page. Cursors expire after 60 minutes
5. For a narrower grant than a personal token, connect MCP through a custom OAuth app with only scopes such as boards:read

Redmine

1. Ask an administrator to tick Enable REST API under Administration, Settings, API. It is off by default and every call fails until then
2. Send the key in the X-Redmine-API-Key header, never as the key query parameter, and set Content-Type: application/json on every POST and PUT
3. Add status_id=* to issue lists. The default returns open issues only, 25 a page with a maximum of 100
4. Comment on an issue by sending notes in a PUT to /issues/<id>.json. There is no separate comment endpoint
5. A DELETE on a project through the API skips the confirmation the web page asks for, so run the agent as a non-administrator user