
Channelchat
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Slack channels, messages, threads, reactions and users via the Slack Web API.
Overview
Channelchat's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Channelchat in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
channelchat
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.
Install
CLI
Exit codes: 0 success, 1 API error, 2 usage error.
MCP server
Tools
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.
Development
Tests run entirely on fake-fetch fixtures, including Slack's
HTTP-200-with-ok: false error shape; no network is used.
License
MIT — see LICENSE.
Source: README.md at commit 59f0a46
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts