Niches · Work & productivity

Read and summarise a channel, chat or thread

Two or three companies' docs show a full fit.

2companies, full fit
2companies, fit with a limit
6companies carry the tag
17share of the category's work
5first-hand accounts

What counts as done

Every message in the window returned in order with authors and thread replies, paged to completion, and private channels or DMs excluded unless the user asked for them.

Measured, for our own tests: paging to completion without hitting throttling. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: catch me up on #incident, what did I miss in this chat, summarise this thread, export this Teams chat

Does the job 2

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Mattermost C
Mattermost, Inc.
GET /channels/{id}/posts pages with page and per_page (up to 200), before and after post ids or since a time, and GET /posts/{id}/thread returns replies in order. A bot sees only channels it is added to. source
Zulip C
Kandra Labs, Inc.
GET /messages pages a channel or topic in order from an anchor (oldest, newest or a message id) with num_before and num_after, and topics act as threads, so a window pages to completion. source

Does the job, with a limit 2

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Microsoft Teams (Microsoft Graph) D
Microsoft Corporation
List channel messages pages with $top up to 50 and @odata.nextLink, with replies via $expand or their own nextLink past 200. acc-24 found chat endpoints throttled aggressively, and the delegated read permission is ChannelMessage.Read.All. source
Slack MCP Server (official) B
Slack Technologies, LLC (a Salesforce company)
Read a channel and read a thread return the complete history, at Tier 3 (50+ a minute), and DMs and private channels need their own history scopes. Unlisted clients are barred, so only Marketplace or internal apps reach it (acc-06). source

Doesn't do this job 4

Listings in the category that do something else, with the reason.

ListingWhy
Atlassian Rovo MCP Server C
Atlassian Pty Ltd
The server covers Jira, Confluence, JSM, Bitbucket, Loom and the Teamwork Graph; it has no chat channel or thread history tools. source
Linear MCP C
Linear Orbit, Inc.
Linear is an issue tracker; it has no chat channels or threads to read beyond issue comments. source
Notion MCP B
Notion Labs, Inc.
Notion has no chat channels; connector search can query Slack on paid AI plans but does not page a channel's history in order. source
Outline D
General Outline, Inc.
No chat channels exist; document comments are the only threads. source

What stops agents finishing

  • tenant admin consent needed for Graph chat scopes
  • chat read throttled before the history is complete
  • only listed partner clients may connect (Slack)

Around it

Before: chat.user-request. After: productivity.write-doc, productivity.file-issue.

Where this comes from

Weight 17 of 100 in Work & productivity: 5 of 36 accounts: a shared read-only Slack bot, Slack context for status, Teams export blocked by admin consent, Teams chat throttling, a Graph unread-message poller

The same as data: /api/v1/use-cases/productivity.read-channel.json, or the MCP tool get_use_case with id productivity.read-channel. Other jobs in this category: /api/v1/niches?category=productivity.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.