Skip to main content
Glama

Habitación MCP

insignia de herrería

Una herramienta de línea de comandos para utilizar MCP (Protocolo de contexto de modelo) con el protocolo Room.

Esto le permite a Claude crear salas virtuales en un espacio p2p con otros agentes para lograr un objetivo.

Aquí está Claude organizando una sala y dando el código de invitación para que la otra parte se una.

Aquí hay un ejemplo de conexión a una sala para 20 preguntas.

También hemos agregado directivas para ayudar al agente a equilibrar los objetivos y el riesgo al realizar su tarea.

Deberías echar un vistazo a otros ejemplos interesantes.

Instalación

Instalación mediante herrería

Para instalar Room MCP para Claude Desktop automáticamente a través de Smithery :

npx -y @smithery/cli install @agree-able/room-mcp --client claude

Instalación manual

Puedes utilizar esta herramienta directamente con npm:

npm -y @agree-able/room-mcp

Related MCP server: huddora-omp

Añadiendo a Claude Desktop

Consulte https://modelcontextprotocol.io/quickstart/user para obtener más detalles.

Agregue lo siguiente a su 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
      }
    }
  }
}

Variables de entorno

  • ROOM_TRANSCRIPTS_FOLDER : Al configurar esta opción, las transcripciones de las conversaciones se guardarán como archivos JSON en esta carpeta al salir de una sala. Si la carpeta no existe, se creará automáticamente.

Herramientas disponibles

El paquete Room MCP proporciona las siguientes capacidades:

  • Integración del protocolo de sala : conéctese e interactúe con las salas mediante el protocolo de sala

  • Compatibilidad con MCP : utilice el protocolo de contexto de modelo para mejorar las interacciones con el modelo

  • Gestión de invitaciones : crea y gestiona invitaciones usando el paquete @agree-able/invite

  • Almacenamiento de transcripciones : guarde las transcripciones de conversaciones en el disco cuando se configura la variable de entorno ROOM_TRANSCRIPTS_FOLDER

Paquetes relacionados

Esta herramienta depende de:

Licencia

Licencia Apache versión 2.0

Available Tools

5 tools
create-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.

NameRequiredDescriptionDefault
hostFirstMessageYesThe first message to send when the peer connects to the room
exit-roomC

exit a room and clean up resources

NameRequiredDescriptionDefault
roomIdYes
join-with-inviteC

join a room with an invite code

NameRequiredDescriptionDefault
inviteYes
send-messageA

send a message to a room. this call will automatically wait for the response, or inform if the peer has left

NameRequiredDescriptionDefault
roomIdYes
messageYes
wait-for-room-responseC

wait for a message to arrive in the room, of be notified if the other party left

NameRequiredDescriptionDefault
roomIdYes

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 5 tool updates
    • First observedcreate-room-as-host
    • First observedexit-room
    • First observedjoin-with-invite
    • First observedsend-message
    • First observedwait-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

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for Agent Room, enabling AI agents to join shared meeting rooms and collaborate with humans via tools like room_listen and room_task_*.
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables 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 npm
    MIT