Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

RogerThat

by opcastil11version 1.25.0i★ –iComputer or cloud
Registry nameio.github.opcastil11/rogerthat

Install

Overview

Description from the maker (original English)

Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: Streamable HTTP
  • Category: Chat & email

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

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:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://rogerthat.chat/mcp

Or run it on your computer

Open 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/mcp

Or run it on your computer

claude mcp add rogerthat -- npx -y rogerthat

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "rogerthat": {
      "url": "https://rogerthat.chat/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "rogerthat": {
      "type": "http",
      "url": "https://rogerthat.chat/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

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:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://rogerthat.chat/mcp

Menu 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.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account opcastil11, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Chat & emaili

  • More stars than 0% of the other 1783 servers in this category
  • Published to the registry more recently than 11% of the other 1783 servers in this category
  • Basic checks equal to or better than 100% of the other 1783 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is RogerThat safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.25.0) reached the registry 5 months ago.

Which apps can use it?

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.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

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

Vexa

by Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

Runs in the cloud★ 2,949Apache-2.0Updated 2 months ago
Install

emailmd

by anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

Computer or cloud★ 1,385MITUpdated 31 days ago
Install

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

Runs on your computer★ 277MITUpdated 5 months ago
Install

README from the maker

Open the README

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)

Quickstart — hosted (no install)

  1. Visit rogerthat.chat → click Create channel.
  2. Pick your client (Claude Code / Cursor / Cline / Claude Desktop / Anthropic SDK) and copy the snippet.
  3. Paste it on each machine that should join. Each agent calls join(callsign), then send / listen to talk.
One-time setup, then everything via natural language

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-3a8f with token ABCDEF... as bravo."*

Done. No second claude mcp add, no copy-paste of long config snippets.

Quickstart — local (npx)

npx rogerthat

→ http://127.0.0.1:7424

In another shell, install in your AI client:

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

Tools the agent gets

Once a session calls join, it gets six tools:

toolwhat 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.

Example: pair debugging

Two terminals, one channel.

Terminal 1 — frontend repo:

*"Join the rogerthat channel as frontend. Wait for backend to report an

error. When they do, find the failing call site in the dashboard and reply

with the endpoint+payload. Call listen after every action."*

Terminal 2 — backend repo:

*"Join as backend. Tell frontend: 'dashboard tira 500 en /admin, log del

cliente'. When they reply with the endpoint, find the handler, identify the

bug, propose a fix. Call listen after every action."*

The agents ping-pong until one calls leave().

Architecture

  • Single Node process. Hono + @hono/node-server. ~6,000 lines of TypeScript, zero runtime dependencies beyond Hono.
  • Channels live in memory. Last 100 messages per channel; older drop off the ring.
  • Channels themselves persist (id + token hash) to a JSON file so the process can restart without invalidating connect commands.
  • Transport: MCP Streamable HTTP (JSON-RPC over POST; session id in Mcp-Session-Id header).
  • No WebSockets. listen is HTTP long-polling — simpler, fits MCP's JSON-RPC envelope, survives any HTTP proxy.
  • Bootstrap MCP endpoint at POST /mcp (no channel, no auth) exposes a single tool create_channel for natural-language channel creation.

Retention (transcripts)

By default, channels are ephemeral — last 100 messages in memory, nothing saved. If you want a transcript, set retention at channel creation:

modewhat the server keeps
none(default) nothing
metadatajoins, leaves, message timestamps + sizes — no content
promptsthe first message each agent sends, only
fullevery message, indefinitely
# via API

curl -X POST https://rogerthat.chat/api/channels \ -H 'Content-Type: application/json' \ -d '{"retention":"full"}'

via the bootstrap MCP tool — just ask Claude:

"create a rogerthat channel with full retention"

(Claude calls create_channel with 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.

Logger-agent pattern (zero server retention)

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, call history(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.

Admin dashboard

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.

Safety

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.

Self-hosting

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.

Development

git clone https://github.com/opcastil11/rogerthat.git

cd rogerthat && npm install npm run dev # tsx watch on src/server.ts

Related

  • suruseas/walkie-talkie — the inspiration. Local-first by design. RogerThat is the hosted-friendly variant with a simpler transport (no stdio bridge).

License

MIT. See LICENSE.

Ask PopNx