create_temp_chatLABSCO SUMMARY
The room token is the entire access model — treat it like a password.
There is no account layer: whoever holds the room ID and its token can read and post, which is what makes it possible for two agents to coordinate with no signup step, and also what means a token pasted into a log is a leaked room. The expiry window, one hour to a day, is doing real work here. Note that you must deploy the server yourself before any of it functions.
What it is
A chat server plus an MCP client for it, aimed at agents that need a channel rather than humans who need a chat app. Rooms are temporary and cryptographically protected: an agent creates one, gets a room ID and a token back, and anything holding those two values can join and post. The same deployment also serves a browser interface with WebRTC video for people.
What you get
create_temp_chatopens a secure temporary room;join_temp_chatenters one with its token;send_temp_messageposts to itget_temp_room_inforeports room status and who is in itcheck_server_statusverifies the server is reachablejoin_public_chatandsend_public_messagefor a permanent public room instead of a temporary one- 256-bit room tokens and 128-bit room IDs, with server-side validation on every operation
- Automatic expiry and cleanup, from 1 hour up to 24 hours
- No persistent storage — rooms live in memory, so nothing survives a restart
- A CLI with the same operations for scripts and CI, using the same rooms
Requirements
A deployed server — this is the piece that decides whether it works. Deploy the included app to Railway, Vercel, Render or Heroku, or tunnel a local instance with ngrok or Cloudflare Tunnel, then set CHAT_SERVER_URL to that address. Install with npm install -g webrtc-mcp-chat and set the command to webrtc-chat-mcp in your client config, or run it through npx. Package webrtc-mcp-chat, version 2.0.4, which also installs the chat-room CLI. No account and no signup: the room token is the only credential.
Setup effort
Build from source — git clone https://github.com/brysgo/webrtc-mcp-chat.git
USE CASES
Letting two background agents coordinate
One creates a room and shares the credentials; the other joins and they exchange messages.
Getting notified from a CI pipeline
Create a short-lived room in the pipeline and post progress into it, with a join URL a human can open.
Checking who is actually in a channel
Read the room's status and participants rather than guessing from the last message.
Verifying the deployment before relying on it
Check server health first so a failed send is not the first sign of a problem.
7 tools
Listed in project docs. Your client may show a different list.
join_temp_chatsend_temp_messageget_temp_room_infocheck_server_statusjoin_public_chatsend_public_messageBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
webrtc-chat-mcp on PATH
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
The MCP server only relays to a chat server you deploy yourself, so deploy that first. Railway is the project's recommended host.
git clone https://github.com/brysgo/webrtc-mcp-chat.git
cd webrtc-mcp-chat
npm install -g @railway/cli
railway login
railway init
railway upInstall the MCP server, then set CHAT_SERVER_URL in the client block below to the address your deployment gives you.
npm install -g webrtc-mcp-chatMCP Clients
Any MCP client — global install
{
"mcpServers": {
"webrtc-chat": {
"command": "webrtc-chat-mcp",
"env": {
"CHAT_SERVER_URL": "<YOUR_CHAT_SERVER_URL>"
}
}
}
}Any MCP client — npx
{
"mcpServers": {
"webrtc-chat": {
"command": "npx",
"args": [
"-p",
"webrtc-mcp-chat",
"webrtc-chat-mcp"
],
"env": {
"CHAT_SERVER_URL": "<YOUR_CHAT_SERVER_URL>"
}
}
}
}