Slack MCP Server
servidor slack-mcp
Un servidor MCP (Protocolo de Contexto de Modelo) para acceder a la API de Slack. Este servidor permite a los asistentes de IA interactuar con la API de Slack mediante una interfaz estandarizada.
Características
Herramientas disponibles:
slack_list_channels: enumera los canales públicos en el espacio de trabajo con paginaciónslack_post_message: publica un nuevo mensaje en un canal de Slackslack_reply_to_thread- Responder a un hilo de mensajes específico en Slackslack_add_reaction- Agrega un emoji de reacción a un mensajeslack_get_channel_history- Obtener mensajes recientes de un canalslack_get_thread_replies: obtener todas las respuestas en un hilo de mensajesslack_get_users: recupera información básica del perfil de todos los usuarios en el espacio de trabajoslack_get_user_profile- Obtener la información del perfil de un usuarioslack_search_messages- Buscar mensajes en el espacio de trabajo
Related MCP server: Slack MCP Server
Inicio rápido
Instalación
npm install @ubie-oss/slack-mcp-serverNOTA: Ahora está alojado en el Registro de GitHub, por lo que necesita su PAT.
Configuración
Debes configurar las siguientes variables de entorno:
SLACK_BOT_TOKEN: Token OAuth de usuario de bot de SlackSLACK_USER_TOKEN: Token OAuth de usuario de Slack (necesario para algunas funciones como la búsqueda de mensajes)
También puede crear un archivo .env para configurar estas variables de entorno:
SLACK_BOT_TOKEN=xoxb-your-bot-token
SLACK_USER_TOKEN=xoxp-your-user-tokenUso
Iniciar el servidor MCP
Directamente:
npx @ubie-oss/slack-mcp-serverO bien, ejecute el módulo instalado con el nodo:
node node_modules/.bin/slack-mcp-serverEdite el json de configuración de MCP para su cliente:
{
"slack": {
"command": "npx",
"args": [
"-y",
"@ubie-oss/slack-mcp-server"
],
"env": {
"NPM_CONFIG_//npm.pkg.github.com/:_authToken": "<your-github-pat>",
"SLACK_BOT_TOKEN": "<your-bot-token>",
"SLACK_USER_TOKEN": "<your-user-token>"
}
}
}Patrón de implementación
Este servidor adopta el siguiente patrón de implementación:
Definir solicitud/respuesta usando esquemas Zod
Esquema de solicitud: Definir parámetros de entrada
Esquema de respuesta: definir respuestas limitadas a los campos necesarios
Flujo de implementación:
Validar solicitud con el esquema Zod
Llamar a Slack WebAPI
Analizar la respuesta con el esquema Zod para limitarla a los campos necesarios
Devolver como JSON
Por ejemplo, la implementación slack_list_channels analiza la solicitud con ListChannelsRequestSchema , llama a slackClient.conversations.list y devuelve la respuesta analizada con ListChannelsResponseSchema .
Desarrollo
Scripts disponibles
npm run dev- Inicia el servidor en modo de desarrollo con recarga en calientenpm run build: compila el proyecto para producciónnpm run start: inicia el servidor de producciónnpm run lint: ejecuta comprobaciones de linting (ESLint y Prettier)npm run fix: corrige automáticamente los problemas de pelusa
Contribuyendo
Bifurcar el repositorio
Crea tu rama de funciones
Ejecutar pruebas y linting:
npm run lintConfirme sus cambios
Empujar hacia la rama
Crear una solicitud de extracción
Available Tools
11 toolsslack_add_reactionA
Add a reaction emoji to a message
Inputs: reaction (required), timestamp (required), channel_id (required).
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.
Inputs: channel_id (required), limit, cursor.
slack_get_thread_repliesB
Get all replies in a message thread
Inputs: thread_ts (required), channel_id (required), limit, cursor.
slack_get_user_profilesB
Get multiple users profile information in bulk
Inputs: user_ids (required).
slack_get_usersB
Retrieve basic profile information of all users in the workspace
Inputs: limit, cursor.
slack_list_channelsA
List public channels in the workspace with pagination
Inputs: limit, cursor.
slack_post_messageC
Post a new message to a Slack channel
Inputs: text (required), channel_id (required), format.
slack_reply_to_threadC
Reply to a specific message thread in Slack
Inputs: text (required), thread_ts (required), channel_id (required), format.
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.
Inputs: query (required), limit, include_archived.
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.
Inputs: on, page, sort, after, +8 more.
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.
Inputs: query (required), limit, include_bots.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
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.
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.
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.
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
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Hosted Slack MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
A Model Context Protocol server for Wix AI tools
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server implementation that enables AI assistants to interact with Slack workspaces, allowing them to browse channels, send messages, reply to threads, add reactions, and retrieve user information.965 npm2Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA 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-
- AlicenseNot gradedqualityDmaintenanceA simple Model Context Protocol server for Slack integration that enables messaging, channel management, and workspace search capabilities.MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables LLMs to interact with Slack workspaces through OAuth 2.0 authentication. It provides tools for listing channels and posting messages while supporting secure token persistence and dynamic client registration.-