# Read and summarise a channel, chat or thread

> Read and summarise a channel, chat or thread: 2 companies fully do it, 2 with a limit, 6 carry the tag. Every listing in Work & productivity with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/productivity.read-channel/
- Markdown: https://www.anchorterminal.com/niches/productivity.read-channel/index.md (~1,000 tokens)
- Slim: https://www.anchorterminal.com/niches/productivity.read-channel/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/productivity.read-channel/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 2 | 6 | 17 | 5 |

## 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.

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

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

- **Mattermost (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.
- **Zulip (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.

## Does the job, with a limit

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.

- **Microsoft Teams (Microsoft Graph) (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.
- **Slack MCP Server (official) (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).

- not this job: Atlassian Rovo MCP Server (Atlassian Pty Ltd): The server covers Jira, Confluence, JSM, Bitbucket, Loom and the Teamwork Graph; it has no chat channel or thread history tools.
- not this job: Linear MCP (Linear Orbit, Inc.): Linear is an issue tracker; it has no chat channels or threads to read beyond issue comments.
- not this job: Notion MCP (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.
- not this job: Outline (General Outline, Inc.): No chat channels exist; document comments are the only threads.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/productivity.read-channel.json, or the MCP tool get_use_case with id productivity.read-channel. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
