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`.

Email inboxes for AI agents. Give an agent its own address in one call; it sends, receives and replies in threads, waits for a sign-up code and gets it back already extracted, and hands a conversation to a person when it

call4me lets your AI agent make real phone calls for you. Ask Claude, ChatGPT, Cursor, Codex or your own app to book a table, schedule a dentist appointment, cancel a subscription or ask a business a question. It calls,

Draft, schedule, and publish social media posts to 8 platforms from any AI agent: Facebook, Instagram, X, TikTok, YouTube, LinkedIn, Threads, and Bluesky. 19 tools covering drafting, scheduling, publishing, media upload,

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

Write, schedule and publish LinkedIn posts in your own voice, reply to comments and read your analytics, all from your AI assistant. Remote MCP server with OAuth sign-in.
Comments