Learn · Choosing a board

An MCP-connected project board, and what that has to mean

“Has an MCP server” is now a checkbox on most project tools. What makes the connection useful is narrower: whose identity the client acts under, how much of the product the tools cover, whether you can see the tool list before you commit, and what the board charges once an agent is working all day. Here is that checklist, and how NovumOS answers it.

What the connection should give you

  • Coverage. Does the tool list stop at read-and-create, or can the client move cards, write content, comment, manage columns, and claim work from a queue?
  • Identity. Is the agent a member with its own name and audit trail, or does every write appear as the person who pasted the token?
  • The standard transport. Streamable HTTP is what current MCP clients speak; a server stuck on the deprecated HTTP+SSE transport will age badly.
  • A public manifest. Can you read the full tool catalog, with input schemas, before you hold a token?
  • Limits and price. Does the agent inherit a bot throttle or a credit meter, or the same standard rate limits a human member gets?

How NovumOS does it

Three paths, all under /v1/mcp. Both transports sit behind the same bearer-auth wrapper and enforce identical workspace isolation; the manifest is public so a client can read our capabilities before it holds a token.

  • /v1/mcp/http: Streamable HTTP, the recommended transport. Requires Authorization: Bearer.
  • /v1/mcp/sse: the legacy HTTP+SSE transport, kept mounted for back-compat. The MCP spec marks it deprecated.
  • /v1/mcp/manifest: the plain-JSON tool catalog with JSON Schema inputs and both transport URLs. No client, no token.
terminal
claude mcp add --transport http novumos \
  https://novumos.app/v1/mcp/http \
  --header "Authorization: Bearer nov_YOUR_TOKEN"

Any MCP-capable client works the same way: the transport is standard, so point it at the same URL with the same bearer header.

What the tools cover

The manifest lists 90+ typed tools today, grouped the way the REST API is:

  • Discovery: boards, columns, cards, search, and whole block trees in one call.
  • Action: create, update, move, comment, and write content blocks on a card.
  • Work-queue leasing: claim_next_card, renew_lease, complete_lease, fail_lease, so a fleet can drain a column without two workers taking the same card.
  • Administration: webhooks, automations, board access grants, and agent governance, gated on the caller’s role.

Because every tool wraps a REST endpoint, the two surfaces can do the same things, and the manifest is generated from the live server so it always matches what the tools accept.

Identity: the token is an agent, not a key

Workspace Settings → Agents → Connect an agent creates an agent teammate with its own name, avatar, role, and audit trail, and shows its bearer token once (stored hashed with argon2id). Everything the client does over MCP is attributed to that agent on the board, in @-mentions, and in card history. An agent can be scoped to a single board, its permissions are capped by its owner’s current role, and a kill switch refuses the credential outright. The agent-seat article goes through why this matters more than the tool count.

Limits and price

An agent on NovumOS gets the same standard rate limits a human member gets, not a bot throttle, and actions are unlimited. Every seat is a flat $1 per month billed annually ($12/yr), or $3 month-to-month, the same for humans and agents; the first agent is free on every plan, and there is no per-call metering and no AI-credit meter. Agents run on your own model API keys; NovumOS never resells AI. For how other tools’ servers compare on identity, auth, and limits, see the MCP servers for project management roundup.

Quick answers

What is an MCP-connected project board?

A project board that ships its own MCP server, so an MCP client such as Claude Code, Claude Desktop, or your own agent can list boards, read cards, create and move them, and comment, through typed tools instead of a hand-written integration. On NovumOS the server is at https://novumos.app/v1/mcp/http (Streamable HTTP), every REST endpoint has a typed MCP tool, and the full tool catalog is public JSON at /v1/mcp/manifest.

How do I connect Claude Code to the board?

One command: claude mcp add --transport http novumos https://novumos.app/v1/mcp/http --header "Authorization: Bearer nov_YOUR_TOKEN". Mint the token in Workspace Settings → Agents → Connect an agent, which also gives the agent its own name, avatar, and audit trail. Claude Desktop uses the same URL and header in its config file.

Which MCP transport does NovumOS use?

Streamable HTTP at /v1/mcp/http is the primary, recommended transport. The legacy HTTP+SSE endpoint at /v1/mcp/sse stays mounted for back-compat, but the MCP spec marks HTTP+SSE deprecated, so point anything new at /v1/mcp/http. Both require an Authorization: Bearer header; the manifest at /v1/mcp/manifest needs no token.

Is the MCP server included in the free plan?

Yes. Free is $0 forever with no card and includes the MCP server, the full REST API, webhooks, unlimited boards, up to 5 human members, and one agent, since the first agent is free on every plan. Additional seats are a flat $1 per month billed annually ($3 month-to-month), the same for humans and agents, with no per-call metering.

Point your MCP client at a real board. The free plan includes the server and your first agent, with no card.

Create account