Slack MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLACK_TEAM_ID | Yes | Slack 워크스페이스 팀 ID (예: T12345678) | |
| SLACK_BOT_TOKEN | Yes | Slack 봇 토큰 (예: xoxb-...) | |
| SLACK_CHANNEL_IDS | No | 사전 정의된 채널 ID 목록 (쉼표로 구분) |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| slack_list_channelsA | workspace의 public 또는 pre-defined된 채널을 페이지네이션과 함께 목록으로 표시 |
| slack_post_messageC | Slack 채널에 새 메시지 게시 |
| slack_reply_to_threadC | Slack에서 특정 메시지 스레드에 답장 |
| slack_add_reactionC | 메시지에 이모지 반응 추가 |
| slack_get_channel_historyC | 채널에서 최근 메시지 가져오기 |
| slack_get_thread_repliesC | 메시지 스레드의 모든 답장 가져오기 |
| slack_get_usersC | 워크스페이스의 모든 사용자와 기본 프로필 정보 가져오기 |
| slack_get_user_profileC | 특정 사용자의 상세 프로필 정보 가져오기 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Every tool has a clearly distinct purpose targeting specific Slack operations: adding reactions, retrieving channel history, getting thread replies, fetching user profiles, listing users, listing channels, posting messages, and replying to threads. There is no overlap or ambiguity between these functions.
All tools follow a consistent 'slack_verb_noun' pattern with snake_case throughout, such as slack_add_reaction, slack_get_channel_history, and slack_post_message. This predictable naming makes it easy for agents to understand and select the right tool.
With 8 tools, this server is well-scoped for a Slack integration, covering core messaging, user management, and channel operations without being overwhelming. Each tool serves a clear and necessary function in the domain.
The toolset provides strong coverage for core Slack workflows like messaging, reactions, threads, and user/channel listing. Minor gaps exist, such as updating or deleting messages, but agents can work around these with the available tools for most common tasks.