Slack

---
name: slack
description: How to work with Slack via MCP. Use when the user wants to read, search, send, or manage Slack messages, channels, threads, canvases, or user profiles.
---

## Finding and reading

Search messages: `slack_search_public` with keywords and modifiers: `in:#channel`, `from:@user`, `after:YYYY-MM-DD`
Channel history: `slack_search_channels` to resolve ID → `slack_read_channel` with date range
Full thread: get `thread_ts` from search → `slack_read_thread`
Private channels / DMs: `slack_search_public_and_private` — confirm with user first

## Sending and drafting

Post to channel: resolve ID via `slack_search_channels` → draft with `slack_send_message_draft` → `slack_send_message`
DM: `slack_search_users` to resolve user ID → `slack_send_message`
Thread reply: `slack_send_message` with `thread_ts`
Scheduled: `slack_schedule_message`

## Canvases

Create: `slack_search_channels` → `slack_create_canvas`
Read: `slack_read_canvas`
Update: `slack_read_canvas` → `slack_update_canvas`

## Users

Profile / status: `slack_search_users` → `slack_read_user_profile`

## Summarizing

Channel digest: `slack_read_channel` with date filters → summarize decisions and action items
Incident / topic: `slack_search_public` → `slack_read_thread` on key threads → compile summary

## Best Practices

- Resolve channel names and usernames to IDs before acting
- Use `thread_ts` for replies — avoid posting to main channel unnecessarily
- Use `slack_send_message_draft` before sending important or broadcast messages
- Always confirm before sending on the user's behalf
- Use date filters with `slack_read_channel` on high-traffic channels
- Confirm before using `slack_search_public_and_private`