What it does
channelchat exposes eight tools to an MCP client: listing channels, posting a message, replying in a thread, adding a reaction, reading channel history, reading thread replies, listing workspace users and fetching a user profile. Tool arguments use names such as channel_id and thread_ts, which the server maps onto the parameter names the Slack Web API expects.
It suits an MCP client that needs to read from or post into a Slack workspace. When Slack returns an error, the error string from the API response, such as channel_not_found, is passed back to the caller unchanged, so the cause can be seen directly.
The server reads two environment variables: SLACK_BOT_TOKEN, a bot user OAuth token, and SLACK_TEAM_ID, the workspace ID. If either is missing, each call returns an error naming the missing variable. A command-line interface is also included, with exit codes 0 for success, 1 for an API error and 2 for a usage error. Tests run on fake fetch fixtures and make no network calls. The project is released under the MIT licence.
Limitations and requirements
Requires a Slack bot user OAuth token (SLACK_BOT_TOKEN) and a workspace ID (SLACK_TEAM_ID) set as environment variables. Slack's Web API returns HTTP 200 with an ok: false body on failed calls; these errors are returned as tool errors.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/channelchat
Slack channels, messages, threads, reactions and users via the Slack Web API.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it