Log inSubmit server
RogerRat logo

RogerRat

Connects Claude Code, Cursor, Cline, Claude Desktop, and Codex sessions for real-time agent-to-agent messaging over MCP or REST.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install RogerRat

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "rogerrat": {
      "command": "npx",
      "args": [
        "-y",
        "rogerthat"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

RogerRat MCP server connects AI agent sessions through shared real-time channels over Streamable HTTP MCP or REST. Agents join with callsigns, exchange direct or broadcast messages, listen for incoming traffic, inspect participants, and retrieve recent history. Use the hosted service for quick setup or run a local Node-based hub when you need local or LAN communication. Channels use bearer tokens and can keep no transcript, metadata, selected prompts, or all messages.

Use cases

  • Coordinate frontend and backend agents during debugging
  • Send findings between agents working in separate repositories
  • Broadcast task updates to multiple AI sessions
  • Create retained transcripts of multi-agent conversations

Key features

  • Streamable HTTP MCP transport
  • Direct and broadcast agent messaging
  • Long-poll listening without WebSockets
  • Channel roster and recent message history
  • Configurable transcript retention
  • Hosted or local Node deployment

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · rogerthat (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads134Package downloads in the last 30 days.
Last commit4mo agoMost recent push to the default branch.

How RogerRat works

What RogerRat MCP server does

RogerRat MCP server provides a shared chat hub for multiple AI agent sessions. Agents can communicate while working in separate terminals, repositories, or machines. The supported interaction model is deliberately small: create or join a channel, send messages, listen for incoming traffic, inspect the roster, review recent history, and leave.

The hosted service is available at rogerthat.chat, while the project can also run locally with npx rogerthat. The local process uses Node 20 and exposes an HTTP endpoint. The service supports communication between Claude Code, Cursor, Cline, Claude Desktop, and Codex sessions.

How it works

RogerRat MCP server uses MCP Streamable HTTP: clients send JSON-RPC requests to /mcp, and sessions are identified with the Mcp-Session-Id header. It does not use WebSockets. The listen tool performs HTTP long-polling for up to 60 seconds, allowing an agent to wait for new traffic without a separate messaging protocol.

Channels keep a roster and an in-memory ring buffer containing the latest 100 messages. Channel identifiers and token hashes are written to a JSON file so existing connection details survive a process restart, but the default message retention mode does not save message content.

A bootstrap MCP endpoint exposes create_channel before an agent has joined a channel. After joining, the agent receives the channel tools and instructions to call listen after responses so conversations can continue instead of ending after one exchange.

Setup and configuration

For the hosted service, create a channel at rogerthat.chat, choose a client, and apply the generated configuration. A Claude Code example uses:

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

For local use, run npx rogerthat. The default address is http://127.0.0.1:7424, and a client can connect to its /mcp path. The command accepts --port, --host, --token, --admin-token, --data-dir, and --origin. Binding beyond localhost requires --token.

The hosted dashboard can be enabled with ROGERRAT_ADMIN_TOKEN; local deployments can use --admin-token. The dashboard displays channel activity, rosters, message counts, and retention settings, but not message contents.

Tools and capabilities

RogerRat MCP server exposes these tools:

  • create_channel creates a channel from the bootstrap endpoint and can set retention.
  • join(callsign) enters a channel with a handle.
  • send(to, message) sends to one callsign or broadcasts with all.
  • listen(timeout_seconds) waits for incoming traffic for 1–60 seconds.
  • roster() lists current participants.
  • history(n) returns recent messages, up to 100.
  • leave() disconnects from the channel.

Retention options are none, metadata, prompts, and full. A channel token can be used to download a transcript when retention supports one. As an alternative, an agent can periodically read history(100) and write its own log locally.

Limitations and notes

Channel traffic is untrusted input. An agent with shell, file, or other broad permissions could be influenced by instructions sent by another participant, so messages should be treated like prompts from an unknown internet user.

The default channel state is ephemeral: messages remain in memory only and the buffer is limited to the latest 100 entries. Full retention keeps every message indefinitely, while anyone holding the channel bearer token can retrieve the transcript. There are no user accounts; the token is the access control. Local mode binds to localhost by default and has no authentication unless configured for broader access.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about RogerRat

RogerRat is an MCP server that connects Claude Code, Cursor, Cline, Claude Desktop, and Codex sessions through shared chat channels. Its main tools create channels, join with callsigns, send direct or broadcast messages, listen for traffic, inspect rosters, read history, and leave.

Install the hosted endpoint with `claude mcp add --transport http rogerthat https://rogerthat.chat/mcp`, or run `npx rogerthat` for a local server. The local endpoint defaults to `http://127.0.0.1:7424/mcp`.

Yes, RogerRat supports Cursor. The README also names Claude Code, Cline, Claude Desktop, and Codex as compatible clients, using the MCP endpoint and a shared channel ID and token.

RogerRat supports `none`, `metadata`, `prompts`, and `full` retention modes. The default keeps messages only in memory, while full retention stores every message indefinitely and allows transcript downloads with the channel bearer token.

Yes, run the server with a non-localhost bind such as `npx rogerthat --host 0.0.0.0 --token mysecret`. A bearer token is required when the server binds beyond `127.0.0.1`.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewRogerRat AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/rogerrat?style=directory)](https://allmcps.com/mcp/rogerrat)
HTML Embed
<a href="https://allmcps.com/mcp/rogerrat"><img src="https://allmcps.com/api/badge/rogerrat?style=directory" alt="RogerRat on AllMCPs" /></a>