Slack A633454e

MCP办公协作

提供方 modelcontextprotocol · 包名 @modelcontextprotocol/server-slack

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

Channel management and messaging capabilities

一句话选型结论

按资料字段整理

Slack A633454e 属于办公协作类 MCP 服务器,stdio · 本地进程,Token,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

适用场景

slackmessagingchannel-management

安装与配置

stdio · 本地进程 Token
客户端在本机拉起子进程,数据不出本机
SLACK_BOT_TOKEN={SLACK_BOT_TOKEN} SLACK_TEAM_ID={SLACK_TEAM_ID} SLACK_CHANNEL_IDS={SLACK_CHANNEL_IDS} npx -y @modelcontextprotocol/server-slack {"SLACK_BOT_TOKEN":"xoxb-your-bot-token","SLACK_TEAM_ID":"T01234567","SLACK_CHANNEL_IDS":"C01234567, C76543210"}

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

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

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

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

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Slack A633454e当前 未标注 stdio · 本地进程 支持远程部署 有 2026-05-18
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

服务器档案

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

详细介绍

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

Model Context Protocol servers

This repository is a collection of reference implementations for the Model Context Protocol (MCP), as well as references to community-built servers and additional resources.

> [!IMPORTANT]
> If you are looking for a list of MCP servers, you can browse published servers on the MCP Registry. The repository served by this README is dedicated to housing just the small number of reference servers maintained by the MCP steering group.

> [!WARNING]
> The servers in this repository are intended as reference implementations to demonstrate MCP features and SDK usage. They are meant to serve as educational examples for developers building their own MCP servers, not as production-ready solutions. Developers should evaluate their own security requirements and implement appropriate safeguards based on their specific threat model and use case.

The servers in this repository showcase the versatility and extensibility of MCP, demonstrating how it can be used to give Large Language Models (LLMs) secure, controlled access to tools and data sources.
Typically, each MCP server is implemented with an MCP SDK:

  • C# MCP SDK
  • Go MCP SDK
  • Java MCP SDK
  • Kotlin MCP SDK
  • PHP MCP SDK
  • Python MCP SDK
  • Ruby MCP SDK
  • Rust MCP SDK
  • Swift MCP SDK
  • TypeScript MCP SDK

🌟 Reference Servers

These servers aim to demonstrate MCP features and the official SDKs.

  • Everything - Reference / test server with prompts, resources, and tools.
  • Fetch - Web content fetching and conversion for efficient LLM usage.
  • Filesystem - Secure file operations with configurable access controls.
  • Git - Tools to read, search, and manipulate Git repositories.
  • Memory - Knowledge graph-based persistent memory system.
  • Sequential Thinking - Dynamic and reflective problem-solving through thought sequences.
  • Time - Time and timezone conversion capabilities.

Archived

The following reference servers are now archived and can be found at servers-archived.

  • AWS KB Retrieval - Retrieval from AWS Knowledge Base using Bedrock Agent Runtime.
  • Brave Search - Web and local search using Brave's Search API. Has been replaced by the official server (@brave/brave-search-mcp-server).
  • EverArt - AI image generation using various models.
  • GitHub - Repository management, file operations, and GitHub API integration.
  • GitLab - GitLab API, enabling project management.
  • Google Drive - File access and search capabilities for Google Drive.
  • Google Maps - Location services, directions, and place details.
  • PostgreSQL - Read-only database access with schema inspection.
  • Puppeteer - Browser automation and web scraping.
  • Redis - Interact with Redis key-value stores.
  • Sentry - Retrieving and analyzing issues from Sentry.io.
  • Slack - Channel management and messaging capabilities. Now maintained by Zencoder
  • SQLite - Database interaction and business intelligence capabilities.

🚀 Getting Started

Using MCP Servers in this Repository

TypeScript-based servers in this repository can be started with npx.

For example, this will start the Memory server:```sh
npx -y @modelcontextprotocol/server-memory


Python-based servers in this repository can be started with `uvx` or `pip`. `uvx` is recommended for ease of use and setup.

For example, this will start the Git server:```sh
# With uvx
uvx mcp-server-git

# With pip
pip install mcp-server-git
python -m mcp_server_git

Follow these instructions to install uv / uvx and these to install pip.

Using an MCP Client

However, running a server on its own isn't very useful, and should instead be configured into an MCP client. For example, here's the Claude Desktop configuration to use the above server:```json
{
"mcpServers": {
"memory": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-memory"]
}
}
}


On Windows, wrap `npx` with `cmd /c`:```json
{
  "mcpServers": {
    "memory": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-memory"]
    }
  }
}

Additional examples of using the Claude Desktop as an MCP client might look like:```json
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/allowed/files"]
},
"git": {
"command": "uvx",
"args": ["mcp-server-git", "--repository", "path/to/git/repo"]
},
"fetch": {
"command": "uvx",
"args": ["mcp-server-fetch"]
}
}
}


On Windows, apply the same wrapper to the `npx`-based `filesystem` entry above by changing its `"command"` to `"cmd"` and prepending `"/c", "npx"` to its existing `args`. Leave the `uvx` entries unchanged.

### Transports: stdio and Streamable HTTP

An MCP server talks to its client over a **transport**. The protocol defines two standard ones, and they run very differently:

| Transport | How the server runs | How a client reaches it |
|---|---|---|
| **stdio** | The client launches the server as a subprocess and talks to it over the process's stdin and stdout. The server opens no port. | A `command` and `args` in the client's configuration, as in the examples above |
| **Streamable HTTP** | The server runs on its own as an HTTP service, and can serve many clients | A URL, such as `http://localhost:3001/mcp` |

**Every server in this repository serves stdio, and only Everything also serves Streamable HTTP** (its README shows how to start it that way, and covers its deprecated HTTP+SSE transport too). So when you run `uvx mcp-server-git` or `npx -y @modelcontextprotocol/server-memory` in a terminal, it opens no port, prints at most a one-line startup notice, and then appears to hang. That is expected: it is waiting for a client to send it messages on stdin. You do not normally start a stdio server yourself; your MCP client starts it from its configuration and stops it when it is done.

To try a server without setting up a client, use the MCP Inspector. Given a stdio server's command, it launches the server for you and lets you browse and call its tools; given a URL, it connects to a running Streamable HTTP server:```sh
# A stdio server: the Inspector launches it
npx @modelcontextprotocol/inspector uvx mcp-server-git

# A Streamable HTTP server: start it first, then connect to its URL
npx @modelcontextprotocol/server-everything streamableHttp
npx @modelcontextprotocol/inspector --transport http --server-url http://localhost:3001/mcp

For more, see the transport layer in the MCP architecture overview, and Transports in the specification.

🛠️ Creating Your Own Server

Interested in creating your own MCP server? Visit the official documentation at modelcontextprotocol.io for comprehensive guides, best practices, and technical details on implementing MCP servers.

📚 Learn More

See ADDITIONAL.md for a curated list of frameworks and resources that simplify building MCP servers and clients.

🤝 Contributing

See CONTRIBUTING.md for information about contributing to this repository.

📦 Releasing

See RELEASING.md for how packages are published (OIDC trusted publishing from CI — no registry tokens) and how to retry a failed publish.

🔒 Security

See SECURITY.md for reporting security vulnerabilities.

📜 License

This project is licensed under the Apache License, Version 2.0 for new contributions, with existing code under MIT - see the LICENSE file for details.

💬 Community

  • GitHub Discussions

⭐ Support

If you find MCP servers useful, please consider starring the repository and contributing new servers or improvements!


Managed by Anthropic, but built together with the community. The Model Context Protocol is open source and we encourage everyone to contribute their own servers and improvements!

常见问题

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

在客户端按下面的安装命令接入:SLACK_BOT_TOKEN={SLACK_BOT_TOKEN} SLACK_TEAM_ID={SLACK_TEAM_ID} SLACK_CHANNEL_IDS={SLACK_CHANNEL_IDS} npx -y @modelcontextprotocol/server-slack {"SLACK_BOT_TOKEN":"xoxb-your-bot-token","SLACK_TEAM_ID":"T01234567","SLACK_CHANNEL_IDS":"C01234567, C76543210"}。对应的包名是 @modelcontextprotocol/server-slack。装完在客户端配置里引用同一个包或端点。

Slack A633454e 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Slack A633454e 收费吗?

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

Slack A633454e 需要 API Key 吗?

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

Slack A633454e 能提供哪些能力?

资料显示能力标签包括 Slack、Token认证、STDIO。具体工具清单以官方文档为准。

Slack A633454e 需要什么运行环境?

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

Slack A633454e 是本地还是远程?

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

热门专题

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

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