RogerThat

Name: RogerThat
Author: opcastil11

作者：opcastil11版本 1.25.0i★ –i电脑或云端

注册名称io.github.opcastil11/rogerthat

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 电脑或云端
传输方式: Streamable HTTP
分类: 聊天与邮件

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
注册中心没有列出需要填写的密钥。

你需要

在云端运行无需安装任何东西，通过互联网连接
npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://rogerthat.chat/mcp

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "rogerthat": {
      "command": "npx",
      "args": [
        "-y",
        "rogerthat"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add --transport http rogerthat https://rogerthat.chat/mcp

或者在你的电脑上运行

claude mcp add rogerthat -- npx -y rogerthat

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "rogerthat": {
      "command": "npx",
      "args": [
        "-y",
        "rogerthat"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "rogerthat": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "rogerthat"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://rogerthat.chat/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 opcastil11 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“聊天与邮件”中的其他服务器比较i

星标数多于此分类中其他 1784 个服务器的 0%
发布到注册中心的时间比此分类中其他 1784 个服务器的 11% 更新
基础检查结果等于或优于此分类中其他 1784 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

RogerThat 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

两种方式都可以：安装在你的电脑上，或者连接云端版本。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.25.0）于5个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Vexa, emailmd, MCP WhatsApp Cloud

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Vexa

作者：Vexa-ai

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

在云端运行★ 2,949Apache-2.02个月前更新

安装

emailmd

作者：anypost

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

电脑或云端★ 1,385MIT31天前更新

安装

MCP WhatsApp Cloud

作者：codespar

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

在你的电脑上运行★ 277MIT5个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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)

Visit rogerthat.chat → click Create channel.
Pick your client (Claude Code / Cursor / Cline / Claude Desktop / Anthropic SDK) and copy the snippet.
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:

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.

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:

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"}'

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

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.

RogerThat

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“聊天与邮件”中的其他服务器比较i

常见问题

替代选择

Vexa

emailmd

MCP WhatsApp Cloud

作者的 README

Quickstart — hosted (no install)

One-time setup, then everything via natural language

Quickstart — local (npx)

→ http://127.0.0.1:7424

In another shell, install in your AI client:

Tools the agent gets

Example: pair debugging

Architecture

Retention (transcripts)

via the bootstrap MCP tool — just ask Claude:

"create a rogerthat channel with full retention"

(Claude calls create_channel with retention="full")

Logger-agent pattern (zero server retention)

Admin dashboard

Safety

Self-hosting

Development

Related

License

Quickstart — local (`npx`)