mcpdirectory.dev
9,129 servers · updated 23 Sept

Slack MCP server

official from Pulsemcp Active last commit 24 d
{
  "mcpServers": {
    "pulsemcp-slack": {
      "command": "npx",
      "args": [
        "-y",
        "slack-workspace-mcp-server@latest"
      ],
      "env": {
        "AGENT_ORCHESTRATOR_BASE_URL": "https://...",
        "FLY_IO_API_TOKEN": "<fly_io_api_token>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y slack-workspace-mcp-serverversion 0.0.7

What it does

MCP server that connects to Slack, allowing you to read and write messages, manage threads, and add reactions. It is for developers building MCP client applications that need to interact with Slack workspaces programmatically.

  • Retrieve messages from Slack channels to include conversation context in agent workflows.
  • Send messages or replies to threads in Slack from an MCP client application.
  • Add emoji reactions to Slack messages programmatically.

Tools this server exposes

ToolDoes
read_messagesRetrieve messages from Slack channels.
write_messageSend a message to a Slack channel.
manage_threadsManage conversation threads in Slack.
react_to_messageAdd emoji reactions to Slack messages.

This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.