Catch Up on Slack

For an operator who was heads down or away and wants a consolidated read of every channel they are in over a 24 to 48 hour window.

Slack

The grind

Lost in the thread

Here's what doing this by hand looks like today, and why it doesn't scale.

Coming back from a day off means scrolling a dozen channels.
Important decisions get buried in long threads.
You end up asking what did I miss in five different DMs.

MewCP collapses all of this into one prompt. Here's what that looks like.

The flow

7 steps · 1 server

Your agent runs it end-to-end

List the channels the user is a member of.

For each channel, fetch the recent messages in the window.

Drop the channels with fewer than the minimum message count.

For each remaining channel, cluster the messages into distinct threads and topics, and summarize each thread in one line with the lead participant and message count.

Flag any message that mentions the current user or contains urgent keywords like broken, blocker, down, p0, p1, or incident, and put these in a For you section at the top.

Build a permalink for each notable thread.

The payoff

Back in the loop in seconds

One prompt replaces an hour of scrolling with a channel by channel recap you can scan over coffee.

Paste this into Claude, Codex, or any MCP-connected agent. It'll connect your apps and run the task from start to finish.

Run it yourself

Copy the prompt

prompt

Goal: Catch Up on Slack

MCP servers needed (connected through MewCP): Slack

Steps:
1. List the channels the user is a member of.
2. For each channel, fetch the recent messages in the window.
3. Drop the channels with fewer than the minimum message count.
4. For each remaining channel, cluster the messages into distinct threads and topics, and summarize each thread in one line with the lead participant and message count.
5. Flag any message that mentions the current user or contains urgent keywords like broken, blocker, down, p0, p1, or incident, and put these in a For you section at the top.
6. Build a permalink for each notable thread.
7. Return the recap, focus channels first, then by volume.

Check with me before sending any message or changing data in a connected app.

More recipes