Slack channels, messages, threads, reactions and users via the Slack Web API.
MCPpedia last refreshed this data
io.github.CloudCorpRecords/channelchat is an MCP server that slack channels, messages, threads, reactions and users via the Slack Web API. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 56/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"channelchat": {
"env": {
"SLACK_TEAM_ID": "T0123",
"SLACK_BOT_TOKEN": "xoxb-..."
},
"args": [
"-y",
"@reneturcios/channelchat",
"mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Slack channels, messages, threads, reactions and users via the Slack Web API.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y '@reneturcios/channelchat' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @reneturcios/channelchat against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in productivity
Official MCP server for Anytype API - your encrypted, local and collaborative wiki.
MCP server for monday.com integration.
Give AI agents access to your Obsidian vault via local files or Self-hosted LiveSync.
Interact with Microsoft 365 and Office services through the Microsoft Graph API.
MCP Security Weekly
Get CVE alerts and security updates for io.github.CloudCorpRecords/channelchat and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
channelchat gives an MCP client a working presence in a Slack workspace: list the channels, post a message, carry on a thread, drop a reaction, and look back over history or up at the member list. It implements the full documented server-slack tool set — all eight tools — against the Slack Web API.
Two environment variables are required, exactly as in the original
server: SLACK_BOT_TOKEN (the bot user OAuth token, sent as a Bearer
token) and SLACK_TEAM_ID (the workspace id, passed to the methods
that accept one). If either is missing, every call fails with an
error naming the missing variable instead of failing the handshake.
Slack's Web API answers HTTP 200 even when a call fails, with an
ok: false body; channelchat surfaces that body's error string as
the tool error, so channel_not_found and friends reach the caller
verbatim.
npx @reneturcios/channelchat slack_list_channels
docker run -i -e SLACK_BOT_TOKEN -e SLACK_TEAM_ID ghcr.io/cloudcorprecords/channelchat
channelchat slack_list_channels --limit 20
channelchat slack_post_message --channel-id C0123 --text "deploy finished"
channelchat slack_reply_to_thread --channel-id C0123 --thread-ts 1700000000.000100 --text "looking into it"
channelchat slack_add_reaction --channel-id C0123 --timestamp 1700000000.000100 --reaction thumbsup
channelchat slack_get_user_profile --user-id U0123
channelchat --version
Exit codes: 0 success, 1 API error, 2 usage error.
npx -y @reneturcios/channelchat mcp
{
"mcpServers": {
"channelchat": {
"command": "npx",
"args": ["-y", "@reneturcios/channelchat", "mcp"],
"env": { "SLACK_BOT_TOKEN": "xoxb-...", "SLACK_TEAM_ID": "T0123" }
}
}
}
| Tool | Required | Optional |
|---|---|---|
slack_list_channels | — | types, exclude_archived, limit |
slack_post_message | channel_id, text | — |
slack_reply_to_thread | channel_id, thread_ts, text | — |
slack_add_reaction | channel_id, timestamp, reaction | — |
slack_get_channel_history | channel_id | limit |
slack_get_thread_replies | channel_id, thread_ts | — |
slack_get_users | — | cursor, limit |
slack_get_user_profile | user_id | — |
Tool arguments use the caller-facing names from the documented
surface (channel_id, thread_ts, reaction, user_id); the core
maps them onto the Web API's parameter names (channel, ts,
name, user) when it builds each request.
npm install
npm run build
npm test
npm run dev
Tests run entirely on fake-fetch fixtures, including Slack's
HTTP-200-with-ok: false error shape; no network is used.
MIT — see LICENSE.