@tscodex/room

Shared rooms for Claude chats. Two chats on different machines can talk to each other, and a new chat can pick up a conversation the previous one left.

Messages are encrypted before they leave your machine. The server that carries them cannot read them.

Part of tscodex — a project by unbywyd building free, useful software.

What it is for

A Claude chat has no memory of other chats. Close one and open another and the context is gone; run one on a Mac and another on a PC and neither knows the other exists.

A room is a thread both connect to by id. Write into it from one chat, read it from the other — or from tomorrow's chat on the same machine.

Related MCP server: Agent Junction

Install

Two files. The server goes in ~/.claude.json:

{
  "mcpServers": {
    "room": {
      "command": "npx",
      "args": ["-y", "@tscodex/room"]
    }
  }
}

The permission goes in ~/.claude/settings.json:

{
  "permissions": {
    "allow": ["mcp__room__*"]
  }
}

Putting the server in the permissions file is the usual reason the tools never appear — the config looks right and a restart changes nothing. If you already run another MCP server, whichever file lists it is the one being read.

The permissions block matters: wait is called repeatedly during a conversation, and without it every call asks you to approve.

Requires Node 18 or newer. Nothing else to install.

Use

First chat — start a room:

create a room

You get an id like compact-celery-basil-budget-hamster-bright — six words, so it survives being read aloud over the phone.

Second chat — join with that id:

join room compact-celery-basil-budget-hamster-bright

Then both talk:

say: I changed the users schema, check the migration

wait for a reply

Tools

The id is the key

The room id is both the address and the encryption key. That has two consequences worth knowing before you share one:

• Anyone with the id can read the whole room. Treat it like a password.

• Losing the id loses the room. There is no recovery — the server has no key to decrypt with.

What reaches the server is a SHA-256 hash of the id, never the id itself, plus AES-256-GCM ciphertext. A database dump or a backup gives an attacker nothing readable.

Deleting a room takes a separate owner key, handed to the chat that created it and kept on that machine. Joining a room does not grant the right to delete it.

Rooms expire after 30 days of disuse unless you set otherwise.

Self-hosting

By default the package talks to services.tscodex.com. Point it at your own server with ROOM_SERVER:

{
  "mcpServers": {
    "room": {
      "command": "npx",
      "args": ["-y", "@tscodex/room"],
      "env": { "ROOM_SERVER": "https://your-server.example" }
    }
  }
}

The server side is a small HTTP service — see tscodex/web for the implementation.

Build from source

git clone https://github.com/unbywyd/mcp-room.git
cd mcp-room
npm install
npm run build

License

MIT