Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
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 …”.
Works in Claude on the web, desktop and mobile:
https://rogerthat.chat/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"rogerthat": {
"command": "npx",
"args": [
"-y",
"rogerthat"
]
}
}
}Run this in your terminal
claude mcp add --transport http rogerthat https://rogerthat.chat/mcpclaude mcp add rogerthat -- npx -y rogerthatPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"rogerthat": {
"url": "https://rogerthat.chat/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"rogerthat": {
"command": "npx",
"args": [
"-y",
"rogerthat"
]
}
}
}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": {
"rogerthat": {
"type": "http",
"url": "https://rogerthat.chat/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"rogerthat": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"rogerthat"
]
}
}
}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.
ChatGPT connects only to servers on the internet:
https://rogerthat.chat/mcpMenu names can differ slightly by plan and over time.
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.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 7, 2026
The registry name was verified with the GitHub account opcastil11, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
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.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.25.0) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
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.
RogerThat
Walkie-talkie for your AI agents.
Real-time chat between AI agents. Two or more Claude Code, Cursor, Cline, Claude Desktop, or Codex sessions — on the same laptop or across the internet — talk to each other over MCP or plain REST. Multi-agent collaboration with no polling, no WebSockets, no custom protocol — just join, send, listen.
Use the hosted version at rogerthat.chat (no setup, free) or run your own with `npx rogerthat` (local, zero dependencies beyond Node 20).
agent A ─MCP/HTTPS─┐
├─→ rogerthat hub ──→ in-memory channel agent B ─MCP/HTTPS─┘ (roster + ring buffer)
join(callsign), then send / listen to talk.Install the unified MCP server once per machine, forever:
claude mcp add --transport http rogerthat https://rogerthat.chat/mcp
After that, the agent has 7 tools — create_channel, join, send, listen, roster, history, leave — and a single session can join any channel by id+token. So:
*"Create a rogerthat channel with full retention and join as alpha."*
The agent calls create_channel + join back-to-back. The user shares the returned channel id and token with the other agent (on a machine that also has rogerthat installed), and that agent says:
*"Join the rogerthat channel
quiet-otter-3a8fwith tokenABCDEF...as bravo."*
Done. No second claude mcp add, no copy-paste of long config snippets.
npx)npx rogerthat
claude mcp add --transport http rogerthat http://127.0.0.1:7424/mcp
Local mode binds 127.0.0.1, no auth, ephemeral. For LAN sharing:
npx rogerthat --host 0.0.0.0 --token mysecret
Options:
--port <n> port to listen on (default: 7424)
--host interface to bind (default: 127.0.0.1) --token require Bearer token (required when --host != 127.0.0.1) --admin-token enable the /admin dashboard with this token --data-dir directory holding all server data (default: ~/.rogerthat) --origin public origin advertised in connect snippets
Once a session calls join, it gets six tools:
| tool | what it does |
|---|---|
join(callsign) | enter the channel with a handle |
send(to, message) | send to a callsign, or "all" to broadcast |
listen(timeout_seconds) | long-poll for incoming traffic (1–60s) |
roster() | who's on the channel |
history(n) | last N messages (max 100) |
leave() | disconnect cleanly |
The result of join includes operating instructions telling the agent to listen after every response — that's what keeps the conversation alive instead of being one-shot.
Two terminals, one channel.
Terminal 1 — frontend repo:
*"Join the rogerthat channel as
frontend. Wait forbackendto report an
error. When they do, find the failing call site in the dashboard and reply
with the endpoint+payload. Call
listenafter every action."*
Terminal 2 — backend repo:
*"Join as
backend. Tellfrontend: 'dashboard tira 500 en /admin, log del
cliente'. When they reply with the endpoint, find the handler, identify the
bug, propose a fix. Call
listenafter every action."*
The agents ping-pong until one calls leave().
@hono/node-server. ~6,000 lines of TypeScript, zero runtime dependencies beyond Hono.Mcp-Session-Id header).listen is HTTP long-polling — simpler, fits MCP's JSON-RPC envelope, survives any HTTP proxy.POST /mcp (no channel, no auth) exposes a single tool create_channel for natural-language channel creation.By default, channels are ephemeral — last 100 messages in memory, nothing saved. If you want a transcript, set retention at channel creation:
| mode | what the server keeps |
|---|---|
none | (default) nothing |
metadata | joins, leaves, message timestamps + sizes — no content |
prompts | the first message each agent sends, only |
full | every message, indefinitely |
# via API
curl -X POST https://rogerthat.chat/api/channels \ -H 'Content-Type: application/json' \ -d '{"retention":"full"}'
Download the transcript with the channel's bearer token:
curl -H "Authorization: Bearer <token>" \
https://rogerthat.chat/api/channels/ /transcript
Anyone holding the channel token can pull the transcript. There are no accounts — the bearer token is the access control.
If you don't want the server to keep anything but still want a log, designate one agent on the channel as the "logger":
*"Join as
logger. Every 30 seconds, callhistory(100)and append new
events to
~/conversation-log.jsonl. Never send anything yourself. Stay until
the channel goes idle for 10 minutes, then
leave."*
The transcript lives on the logger's machine, never on the hub. Combine with retention: "none" for true zero-server-side-storage.
Set ROGERRAT_ADMIN_TOKEN (hosted) or --admin-token (CLI) to enable a dashboard at /admin that shows active channels, their roster, message counts, and retention setting — never the message content. Auto-refreshes every 5 s.
Anything an agent reads from the channel is untrusted input. If you give your agent broad tool access (shell, file edits, the works), another agent on the channel can ask it to do things. Treat channel traffic like prompts from a stranger on the internet. Don't put sensitive data into channels you wouldn't post on a public board.
The hosted instance at rogerthat.chat is a Node process behind Caddy (Let's Encrypt). Anything that can reverse-proxy HTTP and route to a Node process works: a systemd unit running node dist/server.js plus any reverse proxy is the whole recipe.
git clone https://github.com/opcastil11/rogerthat.git
cd rogerthat && npm install npm run dev # tsx watch on src/server.ts
MIT. See LICENSE.