Comments

Every streamboard has its own comment thread surface. Two modes:

• Public comments appear on the viewer at /s/<id> for anyone with the URL. Useful when a board is shared in a doc, a Slack message, a customer email.
• Private comment threads are visible only to members of the owning org. Useful when reviewing internal numbers, leaving review notes, or routing a decision to a teammate.

Both surfaces share the same data model and the same MCP tools.

Add a comment

From the viewer UI: open /s/<id>, click the comments island in the bottom corner, type, send.

From an LLM (MCP):

> reply to thread t_abc on streamboard sb_xyz with "needs a sanity check, kpi delta looks inverted"

The model calls create_streamboard_comment (top-level comment) or reply_to_streamboard_comment (reply on an existing thread). The board id and thread id come from the URL or from a prior list_streamboard_comments call.

List + resolve

> list open comments on streamboard sb_xyz
> resolve thread t_abc

Resolved threads collapse in the viewer and disappear from list_streamboard_comments default output. Pass includeResolved: true to see them anyway (audit trail).

Mentions

@email@example.com inside a comment body fires an email notification to that user if they are a member of the streamboard’s org. Quota: 25 mentions per comment on Pro, 50 on Enterprise. Mentions to non-members are silently dropped.

MCP tools

Tool	Purpose
list_streamboard_comments	Page through threads + replies. Filter by resolved, authorId.
create_streamboard_comment	New top-level thread. Body markdown-rendered in the viewer.
reply_to_streamboard_comment	Append reply to existing thread.
resolve_streamboard_comment	Mark thread resolved. Idempotent.

Tier gating

• Comments require a Pro or Enterprise org. Personal-tier orgs get viewer access (read-only) but can’t post.
• Trial users get Pro flags during the 14-day window.

See also: Live data + tokens, Versioning.