What is the difference between SSE transport and stdio transport?
SSE transport enables communication over HTTP/HTTPS, making the server accessible over the network rather than requiring a direct subprocess connection.
@dVelopment
Basic information
Slack MCP Server with SSE transport
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"slack-mcp-server-sse": {
"command": "docker",
"args": [
"compose",
"up",
"--build"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Slack MCP Server with SSE Transport is a Model Context Protocol (MCP) server that integrates Slack API functionality using Server-Sent Events (SSE) transport instead of stdio. It allows AI assistants to interact with Slack workspaces through a simple HTTP-based interface. The server is built with TypeScript, supports Docker deployment, and works with any MCP client that supports SSE transport.
Set environment variables SLACK_BOT_TOKEN (Slack Bot User OAuth Token starting with xoxb-) and SLACK_TEAM_ID (Slack Workspace/Team ID). Build TypeScript code with npm run build and start the server with npm start. Alternatively, deploy with Docker Compose or run a pre-built Docker image. Connect to the SSE endpoint at /sse using an EventSource client.
SSE transport enables communication over HTTP/HTTPS, making the server accessible over the network rather than requiring a direct subprocess connection.
Node.js 18 or higher is required. A Slack Bot Token with appropriate scopes and a Slack Team ID are also needed.
The server itself does not store data; it makes API calls to Slack on behalf of the token. All data resides in the Slack workspace.
The server exclusively uses Server-Sent Events (SSE) transport. It exposes an SSE endpoint at `/sse` and does not support stdio.
Provide the `SLACK_BOT_TOKEN` (starting with `xoxb-`) and `SLACK_TEAM_ID` as environment variables. The token must have scopes like `channels:history`, `channels:read`, `chat:write`, `reactions:write`, and `users:read`.

Send real faxes to any US, Canadian, or international fax number from any AI assistant. The agent quotes the exact price from the document's real page count, hands the human a Stripe Checkout link (payment stays human-in

Upfirst is an AI phone receptionist for small businesses. Review call transcripts, then fix the greeting, knowledge, and transfer rules from your AI client.

Search, read, and summarise meeting transcripts and summaries from Google Meet, Zoom, and Microsoft Teams - directly from Claude. Meetings as context: ask what was decided, who you spoke with, or what’s come up across an

Official Mobile Text Alerts server. Send and schedule SMS, manage subscribers and groups, and complete carrier registration from any MCP-compatible AI assistant.

Soprano Connect MCP Server enables you to build AI agents that can communicate, engage customers, and manage communications workflows through the Soprano Connect platform using the Model Context Protocol (MCP).
Comments