Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Slack channels, messages, threads, reactions and users via the Slack Web API.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"channelchat": {
"command": "npx",
"args": [
"-y",
"@reneturcios/channelchat",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add channelchat -- npx -y @reneturcios/channelchat mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"channelchat": {
"command": "npx",
"args": [
"-y",
"@reneturcios/channelchat",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"channelchat": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/channelchat",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.