$ recombobulate _
home / tips / connect-the-slack-mcp-server-for-team-notifications
0

Connect the Slack MCP Server for Team Notifications

bagwaa @bagwaa · Mar 26, 2026 · MCP Servers
connect-the-slack-mcp-server-for-team-notifications

Once you've wired up the Slack MCP server, Claude can send messages, post to channels, and thread replies without you ever leaving the terminal.

Install and configure it in your Claude Code settings:

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-slack"],
      "env": {
        "SLACK_BOT_TOKEN": "xoxb-your-token",
        "SLACK_TEAM_ID": "T0123456789"
      }
    }
  }
}

Once connected, you can ask Claude to compose and send context-aware notifications straight from your workflow:

claude "Summarise the last 10 git commits and post a deployment update to #releases"

Or wire it into a post-deploy hook so Claude automatically notifies the team after a successful push:

# .claude/hooks/post-tool-use.sh
if [[ "$TOOL" == "Bash" && "$OUTPUT" == *"deployed successfully"* ]]; then
  claude "Post a brief deploy success message to #deployments"
fi

Stop copy-pasting updates into Slack — let Claude handle the broadcast.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Build a Custom MCP Server to Expose Your Internal APIs

Scaffold a custom MCP server with Claude to give it direct access to your internal APIs, dashboards, and microservices.

bagwaa @bagwaa · 3 hours ago
0
Lock Down MCP Servers with --strict-mcp-config

Use --strict-mcp-config to restrict Claude Code to only the MCP servers you explicitly provide, ignoring all other sources.

bagwaa @bagwaa · 4 hours ago
0
Use the /mcp Command to Inspect Your MCP Servers

When an MCP server misbehaves, /mcp gives you a live view of every connected server, its status, and the tools it's exposing — right inside your session.

bagwaa @bagwaa · 6 hours ago