Slack

com.pulsemcpPublished by pulsemcp.comv0.0.7Updated Oct 24, 2026

MCP server for Slack — read/write messages, manage threads, and react to messages.

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant read Slack channels and threads, post and edit messages, add emoji reactions, and upload text snippets.

What you can do
Connects an assistant to a Slack workspace through a bot token. Read-only tools list accessible channels, fetch a channel with recent messages, and pull a full thread with replies. Write tools post new messages, reply to threads, update previously posted messages, add emoji reactions, and upload long text as file snippets. Tool groups can be limited so only read operations are exposed.
When to use it
Useful when you want an assistant to summarize or search Slack conversations, draft and send replies, keep threads updated, or react to messages without switching apps. Worth adding if your team works mainly in Slack and you want message reading and posting in the same assistant session.
Requirements
Runs locally via npx, so Node.js is needed. Requires a Slack workspace where you can create an app, a bot token supplied as the SLACK_BOT_TOKEN environment variable, and bot scopes for channel and private-channel reading, message history, chat write, reactions write, and file write. The optional ENABLED_TOOLGROUPS variable selects readonly or write tool groups.
Before you install
The bot token is a workspace credential; anyone with it can act as the bot, so store it carefully. Write tools can post, edit, and upload content to channels, and reactions are visible to others. Grant only the scopes you need and consider ENABLED_TOOLGROUPS=readonly to prevent unintended posting. Message content is sent to the model provider as part of tool results.

Installation

In SourceWeft

  1. Open Slack in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Slack MCP Server

A Model Context Protocol (MCP) server for integrating with Slack workspaces. This server provides tools for reading and writing messages, managing threads, and reacting to messages in Slack.

Features

  • List Channels - View all accessible public and private channels
  • Read Channel - Get channel info and recent messages
  • Read Threads - Get full threaded conversations
  • Post Messages - Send new messages to channels
  • Reply to Threads - Continue threaded conversations
  • Update Messages - Edit previously posted messages
  • React to Messages - Add emoji reactions to messages
  • Upload Snippets - Upload text content as file snippets (for long content that exceeds message limits)

Setup

Prerequisites

  • A Slack workspace with admin permissions to create apps
  • A Slack Bot Token (see instructions below)

Environment Variables

VariableRequiredDescriptionDefault
SLACK_BOT_TOKENYesSlack Bot User OAuth Token-
ENABLED_TOOLGROUPSNoComma-separated list of tool groupsAll enabled

Getting a Bot Token

  1. Go to api.slack.com/apps
  2. Create a new app or select an existing one
  3. Navigate to OAuth & Permissions
  4. Add the following Bot Token Scopes:
    • channels:read - View basic channel information
    • channels:history - View messages in public channels
    • groups:read - View private channels
    • groups:history - View messages in private channels
    • chat:write - Send messages
    • reactions:write - Add reactions
    • files:write - Upload files and snippets
  5. Install the app to your workspace
  6. Copy the Bot User OAuth Token (starts with xoxb-)

Claude Desktop

Make sure you have your Slack Bot Token ready.

Then proceed to the setup instructions below. If this is your first time using MCP Servers, you'll want to make sure you have the Claude Desktop application and follow the official MCP setup instructions.

Manual Setup

You're going to need Node working on your machine so you can run npx commands in your terminal. If you don't have Node, you can install it from nodejs.org.

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Modify your claude_desktop_config.json file to add the following:

json
{  "mcpServers": {    "slack": {      "command": "npx",      "args": ["-y", "slack-workspace-mcp-server"],      "env": {        "SLACK_BOT_TOKEN": "xoxb-your-token-here"      }    }  }}

Restart Claude Desktop and you should be ready to go!

Available Tools

Read-Only Tools

ToolDescription
slack_get_channelsList all accessible channels
slack_get_channelGet channel info with recent messages
slack_get_threadGet a thread with all replies

Write Tools

ToolDescription
slack_post_messagePost a new message to a channel
slack_reply_to_threadReply to an existing thread
slack_update_messageUpdate a previously posted message
slack_react_to_messageAdd an emoji reaction to a message
slack_upload_snippetUpload text content as a file snippet to a channel

Tool Groups

You can control which tools are available using the ENABLED_TOOLGROUPS environment variable:

  • readonly - Only read operations (get channels, messages, threads)
  • write - All operations including posting and reactions

Example: ENABLED_TOOLGROUPS=readonly to disable all write operations.

Development

bash
# Install dependenciesnpm run install-all
# Run in development modenpm run dev
# Run testsnpm test                  # Functional testsnpm run test:integration  # Integration testsnpm run test:manual       # Manual tests (requires real credentials)
# Buildnpm run build

License

MIT

Source: experimental/slack/README.md at commit 0ed34de

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.0.7LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts