Provides tools for interacting with Slack, including listing channels, reading message history, sending messages, listing users, and joining channels.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-slack_connect List all channels in our Slack workspace."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Slack MCP Pack
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tool | Description |
| List channels in the Slack workspace. Returns channel names, IDs, and metadata. |
| Get message history from a Slack channel. Bot auto-joins the channel if needed. |
| Send a message to a Slack channel. Bot auto-joins the channel if needed. |
| List users in the Slack workspace. Returns user profiles, IDs, and status. |
| Join a public Slack channel so the bot can read history and post messages. |
Related MCP server: Slack MCP Server
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"slack_connect": {
"url": "https://gateway.pipeworx.io/slack_connect/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/slack_connect/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Slack_connect data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Messaging tools for AI agents: send messages, manage chats, groups and channels.
Enable interaction with Slack workspaces. Supports subscribing to Slack events through Resources.
Carbon Voice MCP serves as a bridge that connects AI assistants like ChatGPT, Claude, and Cursor to a user's Carbon Voice account, turning voice messages and conversations into a private, on-demand knowledge base. It provides 28 specialized tools for comprehensive voice messaging management, including creating and sending messages, accessing conversation history with instant transcription, running AI actions (summarization, TLDR generation, meeting notes), and managing workspace collaboration through folders, contacts, and team communications.
One place to build, share, and govern the skills and tools your AI agents use at work.
