A remote WebRTC chat server with secure temporary rooms and MCP support for background agents
A remote WebRTC chat server with secure temporary rooms and MCP support for background agents. The webrtc mcp chat mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.
A remote-first WebRTC chat server with secure temporary rooms and full MCP (Model Context Protocol) support, designed for background agents and real-time communication.
Everything the assistant can do here goes through one of these:
create_temp_chat — Create secure temporary roomjoin_temp_chat — Join temporary room with tokensend_temp_message — Send message to secure roomget_temp_room_info — Get room status and userscheck_server_status — Verify server healthjoin_public_chat — Join permanent public roomsend_public_message — Send to public roomResponse — The Response tool exposed by this serverYou will need 3 environment variables: CHAT_SERVER_URL, ROOM_ID, ROOM_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
The server ships on npm as webrtc-mcp-chat, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Webrtc MCP Chat's toolset — create_temp_chat, join_temp_chat, send_temp_message and 5 more — is a fair guide to whether it matches your workflow. It is maintained by brysgo; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Webrtc MCP Chat's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| create_temp_chat | Create secure temporary room |
| join_temp_chat | Join temporary room with token |
| send_temp_message | Send message to secure room |
| get_temp_room_info | Get room status and users |
| check_server_status | Verify server health |
| join_public_chat | Join permanent public room |
| send_public_message | Send to public room |
| Response | The Response tool exposed by this server. |
Or use without global install:
```json
{
"mcpServers": {
"webrtc-chat": {
"command": "npx",
"args": ["webrtc-mcp-chat"],
"env": {
"CHAT_SERVER_URL": "https://your-deployed-app.com"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CHAT_SERVER_URL | Endpoint or connection string the server talks to. | Yes |
| ROOM_ID | Configuration value read at startup. | Optional |
| ROOM_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.