MCP servers for project management: the honest roundup.

The convergence is real: hosted remote endpoints (the ecosystem has been moving from the older SSE transport to Streamable HTTP — Linear and Asana deprecated their SSE endpoints explicitly), OAuth-centric auth, and read/write tool surfaces over the same API the vendor already sells. An MCP server is a translation layer, not a new product — which is exactly why the underlying API’s character shows through.

On the incumbents’ hosted servers, authentication is user OAuth: the agent operates under the account — and the permissions — of whichever human clicked “authorize.” That is fine for a personal copilot. It gets uncomfortable when the agent is a teammate: every write attributes to that human, access can’t be scoped below what they hold, and none of the vendors documents a distinct agent identity as of July 2026 (Linear’s “app user” mode is the closest).

This is the axis we built differently. On Novum OS an agent is a member with its own seat — its own name on every write, a role and per-board grants of its own, an audit trail that survives staff turnover, and a revocable token that is nobody’s personal credential.

MCP does not exempt anyone from their API’s throttles. Notion is the clearest documented case: roughly 180 requests per minute average per integration, and search capped at 30 requests per minute (per its developer docs, July 2026). Picture an agent triaging a backlog — search for the card, read it, update it, repeat. The search leg alone budgets one operation every two seconds; a competent agent trips that inside a minute and spends the rest of its run backing off. We did the full math on the 3-requests-per-second wall separately.

Novum OS integration tokens get standard rate limits sized for pipelines — no special bot throttle, no per-call metering — so the queue-drain loop is designed to run hot.

A browser OAuth handshake is natural for a desktop assistant and awkward for a fleet of Lambdas. If your agent runs unattended, look for token auth: Notion’s hosted server documents that it does not support bearer tokens; Linear and Atlassian accept API-key/bearer paths. Novum OS is bearer-token native — mint an agent token once, ship it to the worker, revoke or rotate it without touching a human account.

Most PM MCP servers expose create/read/update over their core objects (ClickUp’s beta deliberately omits deletes). The question for agent pipelines is whether the surface covers the coordination problems too. Ours includes the durable work-queue verbs — claim_next_card, renew_lease, complete_lease, fail_lease — so a fleet can drain a column without double-working a card, plus webhook management and board-access grants. The full catalog is public JSON at novumos.app/v1/mcp/manifest, no MCP client required.