Skip to main content
Glama
Slack MCP Server

Slack MCP Server

by ubie-oss

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SLACK_BOT_TOKENYesSlack Bot User OAuth Token
SLACK_USER_TOKENYesSlack User OAuth Token (required for some features like message search)
NPM_CONFIG_//npm.pkg.github.com/:_authTokenNoYour GitHub Personal Access Token needed to install the package

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
slack_list_channelsA

List public channels in the workspace with pagination

slack_post_messageC

Post a new message to a Slack channel

slack_reply_to_threadC

Reply to a specific message thread in Slack

slack_add_reactionA

Add a reaction emoji to a message

slack_get_channel_historyA

Get messages from a channel in chronological order. Use this when: 1) You need the latest conversation flow without specific filters, 2) You want ALL messages including bot/automation messages, 3) You need to browse messages sequentially with pagination. Do NOT use if you have specific search criteria (user, keywords, dates) - use slack_search_messages instead.

slack_get_thread_repliesB

Get all replies in a message thread

slack_get_usersB

Retrieve basic profile information of all users in the workspace

slack_get_user_profilesB

Get multiple users profile information in bulk

slack_search_messagesA

Search for messages with specific criteria/filters. Use this when: 1) You need to find messages from a specific user, 2) You need messages from a specific date range, 3) You need to search by keywords, 4) You want to filter by channel. This tool is optimized for targeted searches. For general channel browsing without filters, use slack_get_channel_history instead.

slack_search_channelsA

Search for channels by partial name match. Use this when you need to find channels containing specific keywords in their names. Returns up to the specified limit of matching channels.

slack_search_usersA

Search for users by partial name match across username, display name, and real name. Use this when you need to find users containing specific keywords in their names. Returns up to the specified limit of matching users.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 11 tools

Disambiguation4/5

Most tools target distinct actions (post, reply, react, list, search), and the history-vs-search-messages pair is explicitly disambiguated in the descriptions. The main overlap is slack_get_users (all users, basic info) versus slack_get_user_profiles (bulk profile info) versus slack_search_users, where the boundary between the first two is unclear.

Naming Consistency5/5

All tools use a uniform slack_<verb>_<noun> snake_case convention (slack_post_message, slack_list_channels, slack_search_users), with verbs chosen sensibly for the action. No mixed casing or inconsistent prefixes.

Tool Count5/5

Eleven tools is well within a reasonable range for a Slack integration and each tool maps to a recognizable Slack operation. Nothing feels padded or missing at the count level.

Completeness3/5

Core read/write workflows (post, reply, react, read history/threads, search, list channels/users) are covered, but the message lifecycle is incomplete: no update_message, delete_message, or remove_reaction, and there is no direct-message or channel-management (create/join) coverage. These are notable gaps that would force agents into dead ends for common Slack tasks.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues