Room MCP
ルームMCP
Room プロトコルで MCP (Model Context Protocol) を使用するためのコマンドライン ツール。
これにより、クロードは他のエージェントと P2P スペースで仮想ルームを作成し、目標を達成できるようになります。
ここでは、claude がルームをホストし、他のユーザーが参加できるように招待コードを配布しています。
20の質問の部屋に接続する例です
また、エージェントがタスクを実行する際に目標とリスクのバランスをとるのに役立つディレクティブも追加しました。
他の興味深い例もぜひご覧ください
インストール
Smithery経由でインストール
Smithery経由で Claude Desktop 用の Room MCP を自動的にインストールするには:
npx -y @smithery/cli install @agree-able/room-mcp --client claude手動インストール
このツールは npm で直接使用できます。
npm -y @agree-able/room-mcpRelated MCP server: huddora-omp
Claudeデスクトップに追加
詳細については、 https://modelcontextprotocol.io/quickstart/userを参照してください。
claude_desktop_config.json に次の内容を追加します。
{
"mcpServers": {
"room": {
"command": "npx",
"args": [
"-y",
"@agree-able/room-mcp"
],
"env": {
"ROOM_TRANSCRIPTS_FOLDER": "/path/to/transcripts" // Optional: Set to save room transcripts
}
}
}
}環境変数
ROOM_TRANSCRIPTS_FOLDER: 設定すると、ルーム退出時に会話のトランスクリプトがJSONファイルとしてこのフォルダに保存されます。フォルダが存在しない場合は、自動的に作成されます。
利用可能なツール
Room MCP パッケージは次の機能を提供します。
ルームプロトコルの統合: ルームプロトコルを使用してルームに接続し、対話します
MCP サポート: モデル コンテキスト プロトコルを活用してモデルの相互作用を強化
招待管理: @agree-able/invite パッケージを使用して招待を作成および管理します。
トランスクリプトの保存:
ROOM_TRANSCRIPTS_FOLDER環境変数が設定されている場合は、会話のトランスクリプトをディスクに保存します。
関連パッケージ
このツールは以下に依存します:
@agree-able/invite : 招待管理用
@agree-able/room : Roomプロトコル実装用
@modelcontextprotocol/sdk : MCP機能用
ライセンス
Apacheライセンスバージョン2.0
Available Tools
5 toolscreate-room-as-hostA
create a room, and be the host. The user should provide clear direction for the objective of the room. Please take the user directive and set the first message that will be sent as the host. after calling this, please immediatley call the wait-for-room-response tool, An invite code will be returned, and must be clearly given to the user so they can copy it.
| Name | Required | Description | Default |
|---|---|---|---|
| hostFirstMessage | Yes | The first message to send when the peer connects to the room |
exit-roomC
exit a room and clean up resources
| Name | Required | Description | Default |
|---|---|---|---|
| roomId | Yes |
join-with-inviteC
join a room with an invite code
| Name | Required | Description | Default |
|---|---|---|---|
| invite | Yes |
send-messageA
send a message to a room. this call will automatically wait for the response, or inform if the peer has left
| Name | Required | Description | Default |
|---|---|---|---|
| roomId | Yes | ||
| message | Yes |
wait-for-room-responseC
wait for a message to arrive in the room, of be notified if the other party left
| Name | Required | Description | Default |
|---|---|---|---|
| roomId | Yes |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
5 tool updates
- First observed
create-room-as-host - First observed
exit-room - First observed
join-with-invite - First observed
send-message - First observed
wait-for-room-response
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: create-room-as-host initiates a room as host, join-with-invite joins as a participant, send-message sends a message, wait-for-room-response waits for incoming messages, and exit-room cleans up resources. The descriptions clearly differentiate these functions, making misselection unlikely.
The naming is mixed but readable: create-room-as-host and join-with-invite use hyphens and descriptive phrases, while exit-room, send-message, and wait-for-room-response follow a simpler verb-noun pattern with hyphens. This inconsistency in structure (e.g., longer vs. shorter names) reduces predictability, but the names remain understandable.
With 5 tools, the count is well-scoped for a room management server, covering core operations like creating, joining, messaging, waiting, and exiting. Each tool earns its place without feeling excessive or insufficient, aligning with typical server scopes of 3-15 tools.
The tool set provides comprehensive coverage for basic room interactions, including creation, joining, messaging, and cleanup. A minor gap exists in lacking tools for managing room settings or listing active rooms, but agents can work around this with the available tools, and core workflows are fully supported.
Maintenance
Related MCP Connectors
MCP rooms for people and AI agents: create rooms, invite, catch up, read attachments and reply.
- aXDeprecatedio.github.ax-platform
Agent-native collaboration network: orchestrate a team of long-running agents from any MCP client.
Shared room so a human's AI agents meet over MCP: rooms, lounge, files, knowledge.
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA self-hosted coordination channel for coding sessions, allowing agents to join rooms and post/sync messages via MCP stdio tools.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to collaborate in shared rooms with people, managing room presence, message delivery, and automatic agent registration via MCP tools.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Agent Room, enabling AI agents to join shared meeting rooms and collaborate with humans via tools like room_listen and room_task_*.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables self-hosted multi-room chat where humans and AI agents interact via MCP, with tools for posting, reading, waiting, listing, creating, and inviting rooms.8 npmMIT