Slack MCP C22d3af8

MCP办公协作

提供方 waimakers

办公协作 stdio · 本地进程 OAuth 授权 社区 / 第三方 Cursor
查看接入方式

一个用于与Slack工作空间交互的模型上下文协议(MCP)服务器,提供频道管理、消息发送、线程回复、表情反应、用户管理等功能。

一句话选型结论

按资料字段整理

Slack MCP C22d3af8 属于办公协作类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Cursor,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类办公协作 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 8 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

办公协作
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量8暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

Slack集成JavaScript本地部署消息管理团队协作自动化工具工作空间管理

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
docker run --rm \

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Docker,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 8 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程与消息

查日程、发消息、约会议。

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 8 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在办公协作场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Slack MCP C22d3af8当前 8 stdio · 本地进程 本地部署 有 2026-05-17
CowAgent 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Karakeep MCP 未标注 未标注 未标注 无 2026-05-17
agentscope 未标注 stdio · 本地进程 本地部署 有 2026-04-11
note-gen 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Everywhere 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

办公协作
字段来自项目仓库与公开索引,中文说明由本站标注
提供方waimakers上游标注的维护方 waimakers
分类办公协作本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Docker本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

10.3 KB
来自项目仓库与上游目录的原文,未做删改

slack-mcp-server

Disclaimer

This project includes code originally developed by Anthropic and released under the MIT License. Substantial modifications and new functionality have been added by For Good AI Inc. (dba Zencoder Inc.), and are licensed under the Apache License, Version 2.0.

Overview

A Model Context Protocol (MCP) server for interacting with Slack workspaces. This server provides tools to list channels, post messages, reply to threads, add reactions, get channel history, and manage users.

Available Tools

  1. slack_list_channels
    - List public or pre-defined channels in the workspace
    - Optional inputs:

    • limit (number, default: 100, max: 200): Maximum number of channels to return
    • cursor (string): Pagination cursor for next page
    • Returns: List of channels with their IDs and information
  2. slack_post_message
    - Post a new message to a Slack channel
    - Required inputs:

    • channel_id (string): The ID of the channel to post to
    • text (string): The message text to post
    • Returns: Message posting confirmation and timestamp
  3. slack_reply_to_thread
    - Reply to a specific message thread
    - Required inputs:

    • channel_id (string): The channel containing the thread
    • thread_ts (string): Timestamp of the parent message
    • text (string): The reply text
    • Returns: Reply confirmation and timestamp
  4. slack_add_reaction
    - Add an emoji reaction to a message
    - Required inputs:

    • channel_id (string): The channel containing the message
    • timestamp (string): Message timestamp to react to
    • reaction (string): Emoji name without colons
    • Returns: Reaction confirmation
  5. slack_get_channel_history
    - Get recent messages from a channel
    - Required inputs:

    • channel_id (string): The channel ID
    • Optional inputs:
    • limit (number, default: 10): Number of messages to retrieve
    • Returns: List of messages with their content and metadata
  6. slack_get_thread_replies
    - Get all replies in a message thread
    - Required inputs:

    • channel_id (string): The channel containing the thread
    • thread_ts (string): Timestamp of the parent message
    • Returns: List of replies with their content and metadata
  7. slack_get_users
    - Get list of workspace users with basic profile information
    - Optional inputs:

    • cursor (string): Pagination cursor for next page
    • limit (number, default: 100, max: 200): Maximum users to return
    • Returns: List of users with their basic profiles
  8. slack_get_user_profile
    - Get detailed profile information for a specific user
    - Required inputs:

    • user_id (string): The user's ID
    • Returns: Detailed user profile information

Slack Bot Setup

To use this MCP server, you need to create a Slack app and configure it with the necessary permissions:

1. Create a Slack App

  • Visit the Slack Apps page
  • Click "Create New App"
  • Choose "From scratch"
  • Name your app and select your workspace

2. Configure Bot Token Scopes

Navigate to "OAuth & Permissions" and add these scopes:
- channels:history - View messages and other content in public channels
- channels:read - View basic channel information
- chat:write - Send messages as the app
- reactions:write - Add emoji reactions to messages
- users:read - View users and their basic information
- users.profile:read - View detailed profiles about users

3. Install App to Workspace

  • Click "Install to Workspace" and authorize the app
  • Save the "Bot User OAuth Token" that starts with xoxb-

4. Get Your Team ID

Get your Team ID (starts with a T) by following this guidance

5. Add Bot to Channels (Optional)

For the bot to access private channels or to post messages, you may need to invite it to specific channels using /invite @your-bot-name

Features

  • Multiple Transport Support: Supports both stdio and Streamable HTTP transports
  • Modern MCP SDK: Updated to use the latest MCP SDK (v1.13.2) with modern APIs
  • Comprehensive Slack Integration: Full set of Slack operations including:
  • List channels (with predefined channel support)
  • Post messages
  • Reply to threads
  • Add reactions
  • Get channel history
  • Get thread replies
  • List users
  • Get user profiles

Installation

Local Development```bash

npm install
npm run build


### Global Installation (NPM)```bash
npm install -g @zencoderai/slack-mcp-server

Docker Installation```bash

Build the Docker image locally

docker build -t slack-mcp-server .

Or pull from Docker Hub

docker pull zencoderai/slack-mcp:latest

Or pull a specific version

docker pull zencoderai/slack-mcp:1.0.0


## Configuration

Set the following environment variables:```bash
export SLACK_BOT_TOKEN="xoxb-your-bot-token"
export SLACK_TEAM_ID="your-team-id"
export SLACK_CHANNEL_IDS="channel1,channel2,channel3"  # Optional: predefined channels
export AUTH_TOKEN="your-auth-token"  # Optional: Bearer token for HTTP authorization (Streamable HTTP transport only)

Usage

Command Line Options```bash

slack-mcp [options]

Options:
--transport <type> Transport type: 'stdio' or 'http' (default: stdio)
--port <number> Port for HTTP server when using Streamable HTTP transport (default: 3000)
--token <token> Bearer token for HTTP authorization (optional, can also use AUTH_TOKEN env var)
--help, -h Show this help message


### Local Usage Examples

#### Using the slack-mcp command (after global installation)```bash
# Use stdio transport (default)
slack-mcp

# Use stdio transport explicitly
slack-mcp --transport stdio

# Use Streamable HTTP transport on default port 3000
slack-mcp --transport http

# Use Streamable HTTP transport on custom port
slack-mcp --transport http --port 8080

# Use Streamable HTTP transport with custom auth token
slack-mcp --transport http --token mytoken

# Use Streamable HTTP transport with auth token from environment variable
AUTH_TOKEN=mytoken slack-mcp --transport http

Using node directly (for development)```bash

Use stdio transport (default)

node dist/index.js

Use stdio transport explicitly

node dist/index.js --transport stdio

Use Streamable HTTP transport on default port 3000

node dist/index.js --transport http

Use Streamable HTTP transport on custom port

node dist/index.js --transport http --port 8080

Use Streamable HTTP transport with custom auth token

node dist/index.js --transport http --token mytoken

Use Streamable HTTP transport with auth token from environment variable

AUTH_TOKEN=mytoken node dist/index.js --transport http


### Docker Usage Examples

#### Using Docker directly```bash
# Run with stdio transport (default)
docker run --rm \
  -e SLACK_BOT_TOKEN=&quot;xoxb-your-bot-token&quot; \
  -e SLACK_TEAM_ID=&quot;your-team-id&quot; \
  zencoderai/slack-mcp:latest

# Run with HTTP transport on port 3000
docker run --rm -p 3000:3000 \
  -e SLACK_BOT_TOKEN=&quot;xoxb-your-bot-token&quot; \
  -e SLACK_TEAM_ID=&quot;your-team-id&quot; \
  zencoderai/slack-mcp:latest --transport http

# Run with HTTP transport on custom port
docker run --rm -p 8080:8080 \
  -e SLACK_BOT_TOKEN=&quot;xoxb-your-bot-token&quot; \
  -e SLACK_TEAM_ID=&quot;your-team-id&quot; \
  zencoderai/slack-mcp:latest --transport http --port 8080

# Run with custom auth token
docker run --rm -p 3000:3000 \
  -e SLACK_BOT_TOKEN=&quot;xoxb-your-bot-token&quot; \
  -e SLACK_TEAM_ID=&quot;your-team-id&quot; \
  -e AUTH_TOKEN=&quot;mytoken&quot; \
  zencoderai/slack-mcp:latest --transport http

Using Docker Compose

Create a docker-compose.yml file:```yaml
version: '3.8'

services:
slack-mcp:
# Use published image:
image: zencoderai/slack-mcp:latest
# Or build locally:
# build: .
environment:
- SLACK_BOT_TOKEN=xoxb-your-bot-token
- SLACK_TEAM_ID=your-team-id
- SLACK_CHANNEL_IDS=channel1,channel2,channel3 # Optional
- AUTH_TOKEN=your-auth-token # Optional for HTTP transport
ports:
- "3000:3000" # Only needed for HTTP transport
command: ["--transport", "http"] # Optional: specify transport type
restart: unless-stopped


Then run:```bash
# Start the service
docker compose up -d

# View logs
docker compose logs -f slack-mcp

# Stop the service
docker compose down

Transport Types

Stdio Transport

  • Use case: Command-line tools and direct integrations
  • Communication: Standard input/output streams
  • Default: Yes

Streamable HTTP Transport

  • Use case: Remote servers and web-based integrations
  • Communication: HTTP POST requests with optional Server-Sent Events streams
  • Features:
  • Session management
  • Bidirectional communication
  • Resumable connections
  • RESTful API endpoints
  • Bearer token authentication

Authentication (Streamable HTTP Transport Only)

When using Streamable HTTP transport, the server supports Bearer token authentication:

  1. Command Line: Use --token to specify a custom token
  2. Environment Variable: Set AUTH_TOKEN= as a fallback
  3. Auto-generated: If neither is provided, a random token is generated

The command line option takes precedence over the environment variable. Include the token in HTTP requests using the Authorization: Bearer header.

Troubleshooting

If you encounter permission errors, verify that:

  1. All required scopes are added to your Slack app
  2. The app is properly installed to your workspace
  3. The tokens and workspace ID are correctly copied to your configuration
  4. The app has been added to the channels it needs to access

Development

Build```bash

npm run build


### Watch Mode```bash
npm run watch

API Endpoints (Streamable HTTP Transport)

When using Streamable HTTP transport, the server exposes the following endpoints:

  • POST /mcp - Client-to-server communication
  • GET /mcp - Server-to-client notifications (Server-Sent Events streams)
  • DELETE /mcp - Session termination

Changes from Previous Version

  • Updated MCP SDK: Upgraded from v1.0.1 to v1.13.2
  • Modern API: Migrated from low-level Server class to high-level McpServer class
  • Zod Validation: Added proper schema validation using Zod
  • Transport Flexibility: Added support for Streamable HTTP transport
  • Command Line Interface: Added CLI arguments for transport selection
  • Session Management: Implemented proper session handling for HTTP transport
  • Better Error Handling: Improved error handling and logging

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Slack MCP C22d3af8 怎么安装?

在客户端按下面的安装命令接入:docker run --rm \。装完在客户端配置里引用同一个包或端点。

Slack MCP C22d3af8 怎么在 Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Slack MCP C22d3af8 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Slack MCP C22d3af8 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Slack MCP C22d3af8 支持哪些客户端?

资料标注支持 Cursor;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Slack MCP C22d3af8 能提供哪些能力?

资料显示约 8 个工具;能力标签包括 Slack、JavaScript、Cursor、团队协作。具体工具清单以官方文档为准。

Slack MCP C22d3af8 需要什么运行环境?

运行时为 Docker;属于本地进程,需要在本机装好运行环境。

Slack MCP C22d3af8 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。