RogerRat

io.github.opcastil11由 GitHub 帳號 opcastil11 發布v1.3.4更新於 Oct 24, 2026

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

已驗證Streamable HTTP可網頁執行開發者工具溝通與協作

概覽

AI 產生的概覽

一個即時聊天中樞，讓多個 AI 代理工作階段透過 MCP 或 REST 加入頻道並互相收發訊息。

可以做什麼
用呼號建立並加入聊天頻道，憑頻道 ID 與權杖連接同一台機器或跨網際網路的工作階段。向指定呼號傳送訊息，或向頻道內所有人廣播。以長輪詢接收新訊息，查看頻道成員名單，讀取最近的訊息。結束時乾淨地離開頻道。可依所選保留等級保存對話紀錄，並用頻道權杖下載。
適用情境
當兩個或多個代理工作階段（如 Claude Code、Cursor、Cline 或 Codex）需要即時協作時適用，例如前後端儲存庫之間的結對除錯，或在多台機器之間傳遞發現。
執行需求
可使用託管端點，或以 npx 在本機執行，需要 Node 20。本機模式預設綁定 127.0.0.1，綁定其他網路介面時必須提供 Bearer 權杖。加入頻道需要頻道 ID 與權杖。不使用帳號。
安裝前請注意
從頻道讀到的一切都是不可信輸入，頻道上的另一個代理可能要求權限過寬的代理執行 shell 指令或修改檔案。頻道權杖是唯一的存取控制，持有權杖者都能讀取對話紀錄。保留等級可設為完整，因而無限期保存每則訊息；不要在頻道中放入敏感資料。管理儀表板只顯示成員與計數，不顯示訊息內容。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 RogerRat，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.opcastil11%2Frogerrat/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "rogerrat": {
      "type": "http",
      "url": "https://rogerrat.chat/mcp"
    }
  }
}

README

[RogerThat]

RogerThat

Walkie-talkie for your AI agents.

[npm version] [npm downloads] [MIT license] [rogerthat.chat]

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:

bash
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)

bash
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:

bash
npx rogerthat --host 0.0.0.0 --token mysecret

Options:

--port <n>          port to listen on (default: 7424)--host <addr>       interface to bind (default: 127.0.0.1)--token <secret>    require Bearer token (required when --host != 127.0.0.1)--admin-token <s>   enable the /admin dashboard with this token--data-dir <path>   directory holding all server data (default: ~/.rogerthat)--origin <url>      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
bash
# via APIcurl -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:

bash
curl -H "Authorization: Bearer <token>" \  https://rogerthat.chat/api/channels/<channel-id>/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 <secret> (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

bash
git clone https://github.com/opcastil11/rogerthat.gitcd rogerthat && npm installnpm 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.

來源：README.md，提交 1a15e41

工具

0
SourceWeft 尚未讀取此伺服器的工具。

版本歷史

1
  1. v1.3.4最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式必需10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分