Skip to content
MCP server

Slack_connect

Gateway pack giving AI clients five Slack tools to read history, post, and list users

Install
Pricing
Freemium
Platforms
API, CLI, Slack
Runs
Locally or Remotely
Version
0.2.1
Listing updated
today

Similar MCP servers

About Slack_connect

Slack_connect is a freemium MCP server for communication. It can run locally on your machine or as a hosted remote server.

The Slack Connect pack is an MCP server hosted behind the Pipeworx gateway that exposes a small set of Slack workspace operations to AI clients. Its five tools cover listing channels, reading channel history, sending messages, listing users, and joining public channels. The README says the bot auto-joins a channel when a history or send call needs it, so the Slack side is handled by a bot identity rather than the calling user.

The README describes the connection as tied to a connected Slack account and a Pipeworx key, and the website describes access via OAuth. Calls can also be made over HTTP to the gateway or through a local npm stdio bridge that forwards requests to the same endpoint. Shared gateway meta-tools such as ask_pipeworx are listed alongside the pack's own tools on the pack endpoint.

The pack suits developers and teams who want an AI agent to read or post in a Slack workspace without writing their own Slack integration. Usage is metered by the gateway, so each call counts against a daily allowance unless the caller signs in or adds credits.

Install

Run in a terminal

claude mcp add --transport http slack_connect https://gateway.pipeworx.io/slack_connect/mcp

Add to Settings → Connectors → Add custom connector

https://gateway.pipeworx.io/slack_connect/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "slack_connect": {
      "url": "https://gateway.pipeworx.io/slack_connect/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "slack_connect": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/slack_connect/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "slack_connect": {
      "serverUrl": "https://gateway.pipeworx.io/slack_connect/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "slack_connect": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/slack_connect/mcp"
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • PIPEWORX_API_KEYOptional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

Tools this server provides (5)

Taken from the project documentation; the running server may differ.

slack_list_channels
List channels in the Slack workspace. Returns channel names, IDs, and metadata.
slack_channel_history
Get message history from a Slack channel. Bot auto-joins the channel if needed.
slack_send_message
Send a message to a Slack channel. Bot auto-joins the channel if needed.
slack_list_users
List users in the Slack workspace. Returns user profiles, IDs, and status.
slack_join_channel
Join a public Slack channel so the bot can read history and post messages.

What it does

Channel listing
Returns channel names, IDs, and metadata for the connected Slack workspace.
Channel history reads
Fetches message history from a named Slack channel, joining it first if the bot is not a member.
Message sending
Posts a message to a Slack channel, with the bot joining the channel when needed.
User directory access
Lists workspace users with profiles, IDs, and status fields.
Public channel joining
Adds the bot to a public channel so it can read and post there.

Good for

  • Let an AI assistant summarise recent activity in a Slack channel
  • Post automated status updates from an agent into a team channel
  • Look up user IDs and profiles before messaging a colleague
  • Find the ID of a channel to use in other automations

Pricing

Freemium, from $49 a month

Free anonymous tier at 50 calls/day; free account at 200 calls/day; pay-as-you-go and subscriptions for higher use.

Prices change. Check pipeworx.io before you buy.

Slack_connect FAQ

Does the pack need an API key?

The npm package works anonymously but is capped at 50 calls a day. A free Pipeworx key raises the cap to 200 a day. The README says the key is optional for the stdio bridge, and the hosted connection needs a Pipeworx key to connect a Slack account.

Which tools are exposed by the pack?

The pack lists five tools: slack_list_channels, slack_channel_history, slack_send_message, slack_list_users, and slack_join_channel. The README also notes that the pack endpoint lists shared Pipeworx meta-tools alongside them.

Can I limit the tools to only this pack in the npm bridge?

Yes. By default the npm bridge lists only this pack's tools. Setting PIPEWORX_META_TOOLS=1 also lists ask_pipeworx and the other gateway-wide tools.

Are calls billed?

The pricing page says each tool call counts as a request, billed by data category, and that setting up the connection is free. Calls that return no data are refunded, and the free daily allowance still counts the call.

Is Slack_connect free?

Slack_connect has a free plan, with paid plans for more usage or features. Paid plans start at $49 a month.

How do I add Slack_connect to Claude Code?

Run this command in your terminal: claude mcp add --transport http slack_connect https://gateway.pipeworx.io/slack_connect/mcp

What are the best alternatives to Slack_connect?

The closest alternatives to Slack_connect are Slack MCP Server, Discord, Gmail, Zoom and Superchat MCP by usefulapi.

Where this comes from

  • Description: written from the project's README, the project's website and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers