Skip to main content
Glama
MCP Server for Slack

MCP Server for Slack

by z9905080

MCP Server for Slack

npm version

A Model Context Protocol (MCP) server implementation for integrating AI assistants with Slack workspaces.

Overview

This package provides an MCP server that enables AI assistants to interact with Slack workspaces. It allows AI models to:

  • List and browse channels

  • Send messages to channels

  • Reply to threads

  • Add reactions to messages

  • Retrieve channel history

  • Get thread replies

  • List users and retrieve user profiles

Related MCP server: Slack MCP Server

Installation

# Install from npm
npm install shouting-mcp-slack

# Or install globally
npm install -g shouting-mcp-slack

You can find the package on npm: shouting-mcp-slack

Prerequisites

You need to set up a Slack Bot and obtain the necessary credentials:

  1. Create a Slack App in the Slack API Console

  2. Add the following Bot Token Scopes:

    • channels:history

    • channels:read

    • chat:write

    • reactions:write

    • users:read

    • users:read.email

  3. Install the app to your workspace

  4. Copy the Bot User OAuth Token

Configuration

The server requires the following environment variables:

  • SLACK_BOT_TOKEN: Your Slack Bot User OAuth Token

  • SLACK_TEAM_ID: Your Slack Team ID

Usage

Running as a CLI Tool

# Set environment variables
export SLACK_BOT_TOKEN=xoxb-your-token
export SLACK_TEAM_ID=your-team-id

# Run the server
mcp-server-slack

Using in Your Code

import { Server } from "@modelcontextprotocol/sdk/server/index.js";
import { SlackClient } from "shouting-mcp-slack";

// Initialize the server and client
const server = new Server({...});
const slackClient = new SlackClient(process.env.SLACK_BOT_TOKEN);

// Register your custom handlers
// ...

Available Tools

The server provides the following Slack integration tools:

  • slack_list_channels: List available channels

  • slack_post_message: Send a message to a channel

  • slack_reply_to_thread: Reply to a thread

  • slack_add_reaction: Add a reaction to a message

  • slack_get_channel_history: Get message history from a channel

  • slack_get_thread_replies: Get replies in a thread

  • slack_get_users: List users in the workspace

  • slack_get_user_profile: Get a user's profile

License

ISC

Author

shouting.hsiao@gmail.com

Repository

https://github.com/z9905080/mcp-slack

Available Tools

9 tools
lookup_user_by_emailC

Lookup a user by their email address

Inputs: email (required).

slack_add_reactionB

Add a reaction emoji to a message

Inputs: channel_id (required), timestamp (required), reaction (required).

slack_get_channel_historyC

Get recent messages from a channel

Inputs: channel_id (required), limit.

slack_get_thread_repliesB

Get all replies in a message thread

Inputs: channel_id (required), thread_ts (required).

slack_get_user_profileB

Get detailed profile information for a specific user

Inputs: user_id (required).

slack_get_usersB

Get a list of all users in the workspace with their basic profile information

Inputs: cursor, limit.

slack_list_channelsB

List public channels in the workspace with pagination

Inputs: limit, cursor.

slack_post_messageB

Post a new message to a Slack channel

Inputs: channel_id (required), text (required).

slack_reply_to_threadB

Reply to a specific message thread in Slack

Inputs: channel_id (required), thread_ts (required), text (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. For example, lookup_user_by_email targets user identification, slack_get_channel_history retrieves channel messages, and slack_post_message handles message creation, ensuring agents can easily differentiate between them.

    Naming Consistency4/5

    The naming is mostly consistent with a 'slack_' prefix and descriptive verb_noun patterns, but there is one deviation: lookup_user_by_email lacks the 'slack_' prefix, which slightly breaks the pattern while remaining readable.

    Tool Count5/5

    With 9 tools, the count is well-scoped for a Slack integration server. It covers core functionalities like user management, messaging, and channel operations without being excessive or insufficient for the domain.

    Completeness4/5

    The tool set provides comprehensive coverage for common Slack workflows, including user lookup, messaging, and channel interactions. A minor gap exists in lacking tools for updating or deleting messages, but agents can still perform most essential tasks effectively.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      A server implementing Model Context Protocol that enables AI assistants to interact with Slack API through a standardized interface, providing tools for messaging, channel management, user information retrieval, and more.
      11
      109
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that integrates with Slack API, allowing users to send messages, view channel history, manage channels, send direct messages, and retrieve user lists from Slack workspaces.
      1
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A simple Model Context Protocol server for Slack integration that enables messaging, channel management, and workspace search capabilities.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for Slack workspace integration. This server allows AI assistants to interact directly with your Slack workspace, providing tools to manage channels, send messages, list users, and upload files.
      1
      MIT