Check token health, age, auto-refresh status, and cache stats

Check if Slack tokens are valid and show authentication status

Force refresh tokens by extracting from Chrome (macOS; requires having signed into Slack in Chrome)

List all DMs and channels with user names resolved. Uses cached DMs by default for speed.

Get messages from a channel or DM with user names resolved

Export FULL conversation history with all messages, threads, and user names. Can save to file.

Search messages across the Slack workspace

Get detailed information about a Slack user

Send a message to a channel or DM

Get all replies in a message thread

List all users in the workspace

Add an emoji reaction to a message

Remove an emoji reaction from a message

Mark a conversation as read up to a specific message timestamp

Get channels and DMs with unread messages, sorted by unread count (highest first)

Search workspace users by name, display name, or email. Case-insensitive partial match.

Save or update a workflow profile that binds a workflow_kind (support_inbox | incident_room | exec_brief | product_launch_watch | custom) to channels, priority people, retention mode, and summary cadence. Stored locally at ~/.slack-mcp-workflows.json. slack_catch_me_up reads the profile by name and returns evidence shaped by its workflow_kind.

List all saved workflow profiles from ~/.slack-mcp-workflows.json. Optionally filter by workflow_kind. Returns profile_name, channels, priority_people, retention_mode, summary_cadence, structured_keys, created_at, updated_at.

Catch up on a saved workflow profile. Reads the profile's channels (or everything currently unread if the profile names none), pulls messages since the cadence window or an explicit since, expands active threads, and returns structured evidence: which threads are unanswered and for how long, what the profile's priority people said or were pinned on, and which conversations moved most. Runs locally against your own session — no hosted account, no server-side model. It also returns a continuity block — commitments someone made, asks nobody has claimed, and questions still unanswered — built from phrase and reply-count rules over the same messages, with the matched text and a permalink on every row so each line can be opened and checked. The response carries an output_contract naming the keys to compose for this workflow_kind; write the summary from the returned signals, continuity and conversations, citing conversation names and timestamps.

What this server process has actually done, as counts: how many messages it read, how many of those were written by authors outside this workspace broken down by origin, how many sends were attempted, and how many were held. A provenance label is a claim about one message; this is the claim about the whole session, and it is the only way to check after the fact whether outside-authored text reached the model and whether anything tried to send on the back of it. Counts only — no message text, no channel name, no user id is recorded. The receipt and the strict hold belong to this server process, so over HTTP every client of the process shares them.