monday.com vs OpenProject

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.

OpenProject

OpenProject's APIv3 has a public OpenAPI 3.1 document with 320 operations, stable error identifiers and optimistic locking, and the same API ships in the free GPL-3.0 Community edition. No request limits are published, API tokens carry their user's full permissions, and 83 security advisories were published in the last twelve months, 13 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

OpenProject

1. Send the API token as Authorization: Bearer <token>, or as the Basic auth password with the user name apikey
2. Read the resource first and send its current lockVersion with every PATCH. A stale value returns 409 UpdateConflict
3. POST to the /form endpoint of a work package to learn writable fields and allowed values before creating or updating
4. URL-encode filters as a JSON array, and add pageSize, offset and select to keep work package lists small
5. Run the agent as a dedicated user with a narrow project role, and treat work package text and comments as untrusted input