en es ja ko zh

Slack MCP

Name: Slack MCP
Author: korotovsky

by korotovsky

Overview Schema Source Related Servers Discussions Admin

Hybrid

Servidor MCP de Slack

Servidor de Protocolo de Contexto de Modelo (MCP) para espacios de trabajo de Slack. Esta integración admite transportes Stdio y SSE, así como la configuración de proxy, y no requiere permisos ni la creación o aprobación de bots por parte de los administradores del espacio de trabajo.

Demostración de funciones

ezgif-316311ee04f444

Herramientas

conversations_history

Obtener mensajes del canal por ID de canal
Entradas requeridas:
- channel_id (cadena): ID del canal en formato Cxxxxxxxxxx.
- cursor (cadena): Cursor para paginación. Utiliza el valor de la última fila y columna de la respuesta como el campo next_cursor devuelto en la solicitud anterior.
- limit (número, predeterminado: 28): límite de mensajes a recuperar.
Devuelve: Lista de mensajes con marcas de tiempo, identificaciones de usuario y contenido de texto

channels_list

Obtener lista de canales
Entradas requeridas:
- channel_types (matriz): Tipos de canal posibles. Valores permitidos: 'mpim', 'im', 'public_channel', 'private_channel'.
- sort (cadena): Tipo de ordenación. Valores permitidos: 'popularidad': ordenar por número de miembros/participantes en cada canal.
Devuelve: Lista de canales

Related MCP server: Slack MCP Server

Guía de configuración

1. Configuración de autenticación

Abre Slack en tu navegador e inicia sesión.

Búsqueda `SLACK_MCP_XOXC_TOKEN`

Abra la consola para desarrolladores de su navegador.
En Firefox, en Tools -> Browser Tools -> Web Developer tools en la barra de menú
En Chrome, haga clic en el botón de "tres puntos" a la derecha de la barra de URL, luego seleccione More Tools -> Developer Tools
Cambiar a la pestaña de la consola.
Escriba "permitir pegar" y presione ENTER.
Pegue el siguiente fragmento y presione ENTER para ejecutar: JSON.parse(localStorage.localConfig_v2).teams[document.location.pathname.match(/^\/client\/([A-Z0-9]+)/)[1]].token

El valor del token se imprime justo después del comando ejecutado (comienza con xoxc- ), guárdelo en algún lugar por ahora.

Búsqueda `SLACK_MCP_XOXD_TOKEN`

Cambie a la pestaña "Aplicación" y seleccione "Cookies" en el panel de navegación izquierdo.
Encuentra la galleta llamada d . Así es, solo la letra d .
Haga doble clic en el Valor de esta cookie.
Presione Ctrl+C o Cmd+C para copiar su valor al portapapeles.
Guárdalo para más tarde.

2. Instalación

Elija uno de estos métodos de instalación:

3. Configuración y uso

Puede configurar el servidor MCP utilizando argumentos de línea de comandos y variables de entorno.

Usando npx

Si tiene npm instalado, esta es la forma más rápida de comenzar a utilizar slack-mcp-server en Claude Desktop.

Abra su claude_desktop_config.json y agregue el servidor mcp a la lista de mcpServers :

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "slack-mcp-server@latest",
        "--transport",
        "stdio"
      ],
      "env": {
        "SLACK_MCP_XOXC_TOKEN": "xoxc-...",
        "SLACK_MCP_XOXD_TOKEN": "xoxd-..."
      }
    }
  }
}

{
  "mcpServers": {
    "slack": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SLACK_MCP_XOXC_TOKEN=$SLACK_MCP_XOXC_TOKEN",
        "-e",
        "SLACK_MCP_XOXD_TOKEN=$SLACK_MCP_XOXD_TOKEN",
        "ghcr.io/korotovsky/slack-mcp-server",
        "mcp-server",
        "--transport",
        "stdio"
      ],
      "env": {
        "SLACK_MCP_XOXC_TOKEN": "xoxc-...",
        "SLACK_MCP_XOXD_TOKEN": "xoxd-..."
      }
    }
  }
}

Consulte Docker para obtener más información.

Usando npx con transporte `sse` :

En caso de que desee ejecutarlo en modo sse , debe utilizar el contenedor mcp-remote para Claude Desktop e implementar/exponer el servidor MCP en algún lugar, por ejemplo, con ngrok o docker-compose .

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://x.y.z.q:3001/sse",
        "--header",
        "Authorization: Bearer ${SLACK_MCP_SSE_API_KEY}"
      ],
      "env": {
        "SLACK_MCP_SSE_API_KEY": "my-$$e-$ecret"
      }
    }
  }
}

{
  "mcpServers": {
    "slack": {
      "command": "C:\\Progra~1\\nodejs\\npx.cmd",
      "args": [
        "-y",
        "mcp-remote",
        "https://x.y.z.q:3001/sse",
        "--header",
        "Authorization: Bearer ${SLACK_MCP_SSE_API_KEY}"
      ],
      "env": {
        "SLACK_MCP_SSE_API_KEY": "my-$$e-$ecret"
      }
    }
  }
}

TLS y exposición a Internet

Hay varias razones por las que podrías necesitar configurar HTTPS para tu SSE.

mcp-remote solo puede manejar esquemas https;
Generalmente es una buena práctica utilizar TLS para cualquier servicio expuesto a Internet;

Podrías usar ngrok :

ngrok http 3001

y luego use el punto final https://903d-xxx-xxxx-xxxx-10b4.ngrok-free.app para su argumento mcp-remote .

Usando Docker

Para obtener información detallada sobre todas las variables de entorno, consulte Variables de entorno .

export SLACK_MCP_XOXC_TOKEN=xoxc-...
export SLACK_MCP_XOXD_TOKEN=xoxd-...

docker pull ghcr.io/korotovsky/slack-mcp-server:latest
docker run -i --rm \
  -e SLACK_MCP_XOXC_TOKEN \
  -e SLACK_MCP_XOXD_TOKEN \
  slack-mcp-server --transport stdio

O bien, el método docker-compose:

wget -O docker-compose.yml https://github.com/korotovsky/slack-mcp-server/releases/latest/download/docker-compose.yml
wget -O .env https://github.com/korotovsky/slack-mcp-server/releases/latest/download/default.env.dist
nano .env # Edit .env file with your tokens from step 1 of the setup guide
docker-compose up -d

Argumentos de la consola

Argumento	Requerido ?	Descripción
`--transport` o `-t`	Sí	Seleccione el transporte para el servidor MCP, los valores posibles son: `stdio` , `sse`

Variables de entorno

Variable	Requerido ?	Por defecto	Descripción
`SLACK_MCP_XOXC_TOKEN`	Sí	`nil`	`token` de campo de datos de autenticación del conjunto de campos de datos POST ( `xoxc-...` )
`SLACK_MCP_XOXD_TOKEN`	Sí	`nil`	Token de datos de autenticación de la cookie `d` ( `xoxd-...` )
`SLACK_MCP_SERVER_PORT`	No	`3001`	Puerto para que el servidor MCP escuche
`SLACK_MCP_SERVER_HOST`	No	`127.0.0.1`	Host para que el servidor MCP escuche
`SLACK_MCP_SSE_API_KEY`	No	`nil`	Token de portador de autorización cuando `transport` es `sse`
`SLACK_MCP_PROXY`	No	`nil`	URL proxy para que la utilice el servidor MCP
`SLACK_MCP_SERVER_CA`	No	`nil`	Ruta al certificado de CA del almacén de confianza
`SLACK_MCP_SERVER_CA_INSECURE`	No	`false`	Confíe en todas las solicitudes inseguras (NO RECOMENDADO)

Herramientas de depuración

# Run the inspector with stdio transport
npx @modelcontextprotocol/inspector go run mcp/mcp-server.go --transport stdio

# View logs
tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

Seguridad

Nunca comparta tokens API
Mantenga los archivos .env seguros y privados

Licencia

Con licencia del MIT (ver archivo de LICENCIA ). Este no es un producto oficial de Slack.

Available Tools

2 tools

channels_listC

Get list of channels

ParametersJSON Schema

Name	Required	Description	Default
`channel_types`	Yes	Possible channel types. Allowed values: 'mpim', 'im', 'public_channel', 'private_channel'.
`sort`	No	Type of sorting. Allowed values: 'popularity' - sort by number of members/participants in each channel.

TDQS

C2.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('Get list') without addressing permissions, rate limits, pagination, or what 'list' entails (e.g., format, completeness). This is inadequate for a tool that likely interacts with a chat system, where such details are critical.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with just three words, front-loaded with the core action. There's no wasted text, making it efficient for quick understanding, though this brevity contributes to gaps in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., safety, performance), output format, and usage context. For a tool with parameters and likely complex interactions in a chat system, this minimal description fails to provide sufficient context for effective agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents both parameters (channel_types and sort). The description adds no parameter-specific information beyond what's in the schema, meeting the baseline score of 3 for high schema coverage without additional value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get list of channels' clearly states the verb ('Get') and resource ('channels'), but it's vague about scope and doesn't distinguish from the sibling tool 'conversations_history'. It doesn't specify whether this retrieves all channels, user-accessible channels, or some subset, leaving purpose ambiguous beyond the basic action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'conversations_history'. The description doesn't mention context, prerequisites, or exclusions, leaving the agent to infer usage based solely on the tool name and parameters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

conversations_historyB

Get messages from the channel by channel_id, the last row/column in the response is used as 'cursor' parameter for pagination if not empty

ParametersJSON Schema

Name	Required	Description	Default
`channel_id`	Yes	ID of the channel in format Cxxxxxxxxxx
`cursor`	No	Cursor for pagination. Use the value of the last row and column in the response as next_cursor field returned from the previous request.
`limit`	No	Limit of messages to fetch in format of maximum ranges of time (e.g. 1d - 1 day, 30d - 30 days, 90d - 90 days which is a default limit for free tier history) or number of messages (e.g. 50). Must be empty when 'cursor' is provided.	1d

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes pagination behavior and the interaction between 'cursor' and 'limit' parameters, which adds useful context beyond the input schema. However, it doesn't cover other behavioral aspects such as rate limits, authentication requirements, error handling, or what the response format looks like (e.g., structure of returned messages). For a tool with no annotations, this leaves gaps in understanding its full behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently conveys the core functionality and key behavioral detail (pagination). It is front-loaded with the main purpose and avoids unnecessary words. However, it could be slightly more structured by separating the pagination explanation into a second sentence for clarity, but overall it's concise and to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 parameters, no output schema, no annotations), the description is moderately complete. It covers the purpose and pagination behavior but lacks details on response format, error conditions, or broader usage context. Without an output schema, the description doesn't explain what the tool returns (e.g., message structure), which is a significant gap. It's adequate for basic understanding but incomplete for full agent usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, meaning the input schema already documents all parameters thoroughly. The description adds some semantic context by explaining how pagination works with the cursor and the constraint that 'limit' must be empty when 'cursor' is provided, which clarifies parameter interactions. However, it doesn't provide significant additional meaning beyond what's in the schema descriptions, such as examples or edge cases, so it meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get messages from the channel by channel_id'. It specifies the resource (messages) and the required parameter (channel_id), making the verb+resource combination explicit. However, it doesn't distinguish this tool from its sibling 'channels_list', which appears to list channels rather than messages, so the differentiation is implied but not explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides some usage guidance by explaining pagination with the cursor parameter and noting that 'limit' must be empty when 'cursor' is provided. This gives context for when to use certain parameters. However, it doesn't explicitly state when to use this tool versus alternatives like 'channels_list' or other hypothetical tools, nor does it provide broader context on when this tool is appropriate versus other methods for retrieving messages.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

2 tool updatesv1.0.0Apr 21, 2025
- First observedchannels_list
- First observedconversations_history

Deploy Server

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

B3/5.0

Scored 2026-04-18 10:30 across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: channels_list retrieves a list of channels, while conversations_history fetches messages from a specific channel. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task.

Naming Consistency4/5

Both tools follow a consistent snake_case naming convention, but the patterns differ slightly: channels_list uses a noun_verb format, while conversations_history uses a noun_noun format. This minor deviation prevents a perfect score, but the naming is still readable and mostly consistent.

Tool Count2/5

With only 2 tools, this server feels too thin for a Slack integration, as it lacks essential operations like sending messages, managing users, or updating channel settings. The scope is severely limited, making it difficult for agents to perform comprehensive Slack-related tasks.

Completeness2/5

The tool surface is significantly incomplete for a Slack domain. While it covers listing channels and retrieving message history, it misses critical operations such as posting messages, creating channels, or handling reactions, which are core to Slack workflows and will likely cause agent failures.

Maintenance

ActivityInactive

ResponsivenessSlow

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

mcp AOAuth
com.mux
The official MCP Server for the Mux API
Multimedia Processing Entertainment & Media API Testing
2168
server B
io.cycloid.mcp
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Developer Tools CI/CD & DevOps Cloud Platforms
2
Sendbird MCP by usefulapi A
io.usefulapi
MCP server for Sendbird — chat users, channels, members, and messages from your AI client.
Communication Customer Support
142
Atako A
ai.atako
Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
Agent Orchestration AI & Machine Learning
31

Related MCP Servers

Slack Notify MCP
Communication Agent Orchestration
SilasReinagel
A
license
Not graded
quality
D
maintenance
MCP server for posting messages to Slack channels via webhooks or bot API. Supports configurable usernames, emojis, and both webhook and bot token authentication modes.
Updated a year ago (2025-07-21 14:37 UTC)
18 npm
MIT
Slack MCP Server
Communication Workplace & Productivity
Themetralla3000
A
license
Not graded
quality
D
maintenance
A Model Context Protocol (MCP) server for Slack workspace integration. This server allows AI assistants to interact directly with your Slack workspace, providing tools to manage channels, send messages, list users, and upload files.
Updated 4 months ago (2026-06-18 18:35 UTC)
32,291 npm
1
MIT
Slack Notifier MCP Server
Communication Workplace & Productivity
farsght
F
license
Not graded
quality
D
maintenance
An MCP server that connects to Slack via Socket Mode (WebSocket) and surfaces real-time message notifications through MCP tools. No public URL or ngrok needed.
Updated 4 months ago (2026-06-22 13:07 UTC)
-
Slack MCP Server
Communication Developer Tools
kamolc4
A
license
Not graded
quality
C
maintenance
A production-ready MCP server for the Slack API that enables searching, listing channels, reading history, inspecting users, fetching threads, and sending messages through controlled Slack tools.
Updated 3 months ago (2026-07-05 00:11 UTC)
32,291 npm
MIT

Servidor MCP de Slack

Demostración de funciones

Herramientas

Guía de configuración

1. Configuración de autenticación

Búsqueda SLACK_MCP_XOXC_TOKEN

Búsqueda SLACK_MCP_XOXD_TOKEN

2. Instalación

3. Configuración y uso

Usando npx

Usando npx con transporte sse :

TLS y exposición a Internet

Usando Docker

Argumentos de la consola

Variables de entorno

Herramientas de depuración

Seguridad

Licencia

Available Tools

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Slack Notify MCP

Slack MCP Server

Slack Notifier MCP Server

Slack MCP Server

Appeared in Searches

Búsqueda `SLACK_MCP_XOXC_TOKEN`

Búsqueda `SLACK_MCP_XOXD_TOKEN`

Usando npx con transporte `sse` :