Expose read/unread state for chat messages via MCP
Thibaut
The ClickUp MCP currently has no way to surface whether a chat message or inbox notification has been read. When building AI agents or automations on top of ClickUp chat, this is a significant gap — without read/unread state, there's no reliable way to filter "what the user hasn't seen yet."
Current behaviour:
The MCP exposes chat messages and inbox notifications but returns no read/unread flag on any of them.
Desired behaviour:
Each chat message and inbox notification returned by the MCP includes a boolean is_read field (or equivalent), reflecting whether the authenticated user has read it.
Why this matters:
Without this, any agent or automation that tries to surface "what needs your attention" has to use heuristics — timestamp cutoffs, action-based filtering, one-time triage rules — as proxies for unread state. These are workarounds, not solutions. A simple is_read flag would unlock accurate, reliable filtering and make ClickUp a much stronger foundation for AI-powered inbox management.
Proposed addition:
is_read: boolean on chat message objects
is_read: boolean on inbox notification objects
a filter parameter on get_chat_channel_messages to return only unread messages
Log In