mcpservers

Recipe

Automate team comms: Slack, email, and notifications

Let Claude read the right channels, draft replies, and turn noise into one clear digest.

15 minutes beginner 3 connectors for Founders and operators who open the day to 40 unread emails and three noisy Slack channels

What you'll need

Slack Read channels and threads, post and reply.
Optional
Gmail Search, read, draft, and label email.
Optional
Notion Drop the resulting digest or action items into a Notion page.
Optional

Do this, in order

  1. 1

    Connect comms

    Install the Slack MCP. List the channels you can read and confirm you won't post without me asking.

    You'll get: Channel list plus a confirmation that posting needs explicit instruction.

  2. 2

    Cut the noise

    Summarize everything in #engineering and #incidents since yesterday into 'needs me', 'FYI', and 'ignore'.

    You'll get: A three-bucket digest with the 'needs me' items first.

  3. 3

    Draft, don't send

    Draft replies for the two 'needs me' threads. Show them to me before anything is posted.

    You'll get: Two draft replies awaiting your approval.

You're done when

You start the day with a clear digest and ready-to-send drafts instead of an hour of catching up — and nothing goes out without your sign-off.

Why this workflow exists

Most team communication is low-signal: a few threads actually need you, the rest is FYI. Comms MCP servers let Claude read across Slack and email, sort what matters, and draft the replies — while you keep the final send. The rule that makes this safe: read and draft freely, but post only on explicit instruction.

People ask their AI

“summarize my Slack / email with Claude”“draft replies with Claude”“what MCP for slack or gmail”

Related

morning inbox and slack digest