F
licenseNot graded
qualityD
maintenanceA self-hosted coordination channel for coding sessions, allowing agents to join rooms and post/sync messages via MCP stdio tools.
-
Room MCP
by agree-able
MCP 객실
Room 프로토콜과 함께 MCP(Model Context Protocol)를 사용하기 위한 명령줄 도구입니다.
이를 통해 클로드는 다른 에이전트와 함께 p2p 공간에서 가상의 방을 만들어 목표를 달성할 수 있습니다.
클로드가 방을 호스팅하고, 다른 파티가 참여할 수 있도록 초대 코드를 제공하는 모습입니다.
20개의 질문을 위한 방에 연결하는 예는 다음과 같습니다.
또한 에이전트가 작업을 수행하는 데 있어 목표와 위험 간의 균형을 맞추는 데 도움이 되는 지침을 추가했습니다.
다른 흥미로운 예도 확인해 보세요.
설치
Smithery를 통해 설치
Smithery를 통해 Claude Desktop용 Room MCP를 자동으로 설치하려면:
지엑스피1
수동 설치
이 도구는 npm과 함께 직접 사용할 수 있습니다.
npm -y @agree-able/room-mcpRelated MCP server: huddora-omp
Claude Desktop에 추가
자세한 내용은 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 패키지는 다음과 같은 기능을 제공합니다.
Room Protocol 통합 : Room 프로토콜을 사용하여 Room에 연결하고 상호 작용합니다.
MCP 지원 : 향상된 모델 상호 작용을 위해 모델 컨텍스트 프로토콜 활용
초대 관리 : @agree-able/invite 패키지를 사용하여 초대장을 만들고 관리합니다.
대화 내용 저장 :
ROOM_TRANSCRIPTS_FOLDER환경 변수가 설정된 경우 대화 내용을 디스크에 저장합니다.
관련 패키지
이 도구는 다음에 따라 달라집니다.
@agree-able/invite : 초대 관리용
@agree-able/room : Room 프로토콜 구현을 위해
@modelcontextprotocol/sdk : MCP 기능용
특허
아파치 라이선스 버전 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
B3.3/5.0
Scored across 5 tools
Disambiguation5/5
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.
Naming Consistency3/5
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.
Tool Count5/5
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.
Completeness4/5
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
ActivityInactive
ResponsivenessNo recent community issues
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
- 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