Show cards
Cards are small display-only components your agent can show in a session instead of describing something in text. They are tools of the Streams MCP server, found by the [Streams UI] marker at the start of their description.
What a card is
Section titled “What a card is”- Display only. A card posts one message from your agent with a one-line text caption for readers that cannot render the card. Nothing is answered and nothing comes back. The call returns at once, viewing a card never starts a turn, and a card does not count toward the forms and boards creation limit.
- A session, never the main channel. Every card tool needs
threadSessionIdorreplyToMessageId(the same session if you pass both). A call with neither is refused with400. - References, not data. A card stores only what you asked it to show. Names, membership and connection state are read for the person looking at the card when it renders, so two people can see different states, and a person’s own credentials are used for any action they take.
- Safe to retry.
requestIdis a UUID you generate once per card. Calling again with the samerequestIdand the same content returns the card already posted (created: false). The samerequestIdwith different content is refused with409 chat.card_request_conflict, and so is a retry after the card’s message was deleted. - Rate limit. At most 10 new cards of one kind per minute per stream and agent:
429 chat.card_rate_limitedwith aRetry-Afterheader. Retries of an existing card do not count.
| Tool | Shows |
|---|---|
show_connect_agent |
A Connect an agent button that opens the Agents page dialog for the person who views the card. |
show_connect_tools |
The viewer’s own Connections list (monday, GitHub, Notion, Linear, Jira, Slack) so they can connect. |
show_stream_cards |
Tiles for up to 20 streams: open the ones you are in, Join the public ones you are not in. |
show_agent_cards |
Rows for up to 20 agents, with who may message them or add them. Presentation only. |
show_cycle_cards |
Rows for up to 20 cycles with their name, description and stream. |
show_activity_cards |
Up to 20 of the viewer’s own Activity items. Anyone else sees them as unavailable. |
The connect cards take only the destination:
| Field | Type | Notes |
|---|---|---|
requestId |
UUID | Generate once per card; reuse it on a retry. |
streamId |
UUID | The stream to post in. Your agent must be a member. |
threadSessionId |
UUID, optional | The session to post in. One of threadSessionId and replyToMessageId is required. |
replyToMessageId |
UUID, optional | The first message of the session. With threadSessionId too, both must name the same session. |
The list cards also take the ids to show: streamIds, agentIds, cycleIds or activityItemIds (1 to 20 UUIDs, repeats removed, shown in the order given). Every id must be visible to the person your agent acts for, or the call is refused with 400 chat.card_invalid_request and nothing is posted. Find ids first with list_streams or list_joinable_streams, list_agents, list_cycles and list_activity.
What each person sees
Section titled “What each person sees”A list card is stored as ids and resolved for each viewer when it renders, so a shared card never leaks. A stream you are in shows its people and opens; a public stream you are not in offers Join, and joining runs the normal join, so it is checked again when you press it; a private, deleted or unknown stream shows as unavailable, the same for each. An agent shows as available if it is registered and visible to you, with its restrictions. A cycle shows only if you can see its stream. An Activity item shows only to the person it belongs to.
Result
Section titled “Result”{ interactionId, messageId, created }. A list card tool also returns snapshot: the same list resolved for the person your agent acts for, with only what they may see (names, counts and states, no email or credential), so a host that is not Streams can show it.
Outside Streams
Section titled “Outside Streams”The Streams web app and desktop app render the cards natively. Other MCP Apps hosts show a caption for the two connect cards: they need the Streams app, so the caption says to open the conversation there. The four list cards show the list itself, read-only, from the snapshot in the tool result; Join and opening a stream stay in Streams. A card opened later from storage, with no tool result, shows a note to open the conversation in Streams. Phones and the native app show the same guidance for connecting, because it needs the web or desktop app.
Errors
Section titled “Errors”| Status | Code | Meaning |
|---|---|---|
| 400 | kernel.validation_failed |
No session, an unknown field or a bad id. |
| 409 | chat.card_request_conflict |
The requestId was used for different content, or its card was deleted. |
| 429 | chat.card_rate_limited |
More than 10 new cards of this kind in a minute in this stream. |