Connect Claude to your board in five minutes.

Sign up free (no card). The free tier includes the full API, the MCP server, and one agent, so everything below works at $0.

Two kinds of credential work; pick by how visible you want the automation to be:

• An agent token (recommended). Workspace Settings → Agents → Connect an agent. This creates an agent teammate with its own name, avatar, and audit trail, and shows its bearer token once. Claude’s actions appear on the board as that agent.
• An integration token. Workspace Settings → Integrations → New integration. Faster, but actions attribute to the integration’s owner rather than a distinct teammate.

Tokens start with nov_, are shown once, and are stored hashed. Rotate or revoke them from the same settings screen.

claude mcp add --transport http novumos \
  https://novumos.app/v1/mcp/http \
  --header "Authorization: Bearer nov_YOUR_TOKEN"

That registers the server for the current project. Run claude mcp list to confirm it connected.

Claude Desktop configures MCP servers in claude_desktop_config.json (Settings → Developer → Edit Config). Use the mcp-remote bridge to attach the bearer header to the remote connection:

{
  "mcpServers": {
    "novumos": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://novumos.app/v1/mcp/http",
        "--header", "Authorization: Bearer nov_YOUR_TOKEN"
      ]
    }
  }
}

Restart Claude Desktop after saving; the tools appear under the connector menu.

The server speaks Streamable HTTP at /v1/mcp/http. That is the current MCP standard transport and the endpoint you should point clients at. The older HTTP+SSE endpoint at /v1/mcp/sse stays mounted for back-compat, but the MCP spec marks HTTP+SSE deprecated, so prefer /v1/mcp/http for anything new. Both endpoints require the same Authorization: Bearer nov_… header and enforce identical workspace (tenant) isolation.

Ask Claude, in plain language:

• “List my boards.”
• “Move the ‘Whisper migration’ card to AI Drafting and add a comment summarizing the open questions.”
• “Claim the next card in the Drafting queue, draft the post from the brief, write it back, and complete the lease.”

If you have the board open in a browser while Claude works, you will see the cards move live, because mutations broadcast on the same real-time channel the UI uses.

• Discover: list boards and columns, query and search cards, read a card’s full block tree.
• Act: create, update, and move cards; append and edit content blocks; add comments.
• Work a queue: claim the next card in a queue column under a lease, heartbeat while working, then complete (advance) or fail (requeue with backoff). Two workers never draft the same card.
• Administer (when its role allows): manage webhooks and board access grants.

The full, always-current tool catalog is published at GET /v1/mcp/manifest as plain JSON, so you don’t need an MCP client to read it. Every tool wraps a REST endpoint documented in the interactive API reference, so you can read and script the same operations without MCP at all.

• Bearer-token auth on every connection; tokens are argon2id-hashed at rest and revocable.
• Every tool call is tenant-scoped to the workspace the token belongs to, with the same isolation guarantees as the REST API.
• Scope an agent to a single board with a viewer/editor grant for least-privilege pipelines.