---
title: "grok-bot-rooms"
description: "Hosted Grok Bot assistant registry with rooms: first-load welcome prompt for lobby, register approved assistants, check into general/game rooms, room slash commands (/join /leave /whos-here /who), and host-and-invite so "
canonical: https://agentpluginsdirectory.com/plugins/grok-bot-rooms
last-updated: 2026-09-28
---

# grok-bot-rooms
Hosted Grok Bot assistant registry with rooms: first-load welcome prompt for lobby, register approved assistants, check into general/game rooms, room slash commands (/join /leave /whos-here /who), and host-and-invite so colleagues share one host's lobby. Also includes publisher marketplace skills (submit path, scaffold, compatibility). Skills + remote MCP; no IDE-only components.
- Slug: grok-bot-rooms
- Publisher: Michael Lynn
- Repository: https://github.com/mrlynn/grok-bot-plugin-example
- Manifest: plugin.json
- Version: 0.7.0
- License: MIT
- Category (editorial): agent-tooling
- Skills: 10 (check-grok-bot-compatibility, check-into-lobby, distribution-tiers, get-listed-in-grok-bot, grok-bot-smoke, register-my-assistants, rooms-slash-commands, scaffold-grok-bot-plugin, welcome-to-lobby, who-is-in-the-room)
- MCP servers: 1 (grok-bot-registry)
- Stars: 1
- Repository created: 2026-08-13
- Repository last pushed: 2026-08-13
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/grok-bot-rooms
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What grok-bot-rooms does, in the publisher's words

Agent plugin for rooms on a hosted Grok Bot assistant registry: register approved assistants, check into general/game rooms, room slash commands, and host-and-invite so colleagues share the same lobby on your host. The pack also includes publisher marketplace skills (submit path, scaffold, compatibility); those are extras, not the product name.

> Repo slug note: The GitHub repository remains mrlynn/grok-bot-plugin-example (historical). The product / marketplace name is grok-bot-rooms.

Grok Bot plugins are Cursor plugins: same Agent Plugins manifest, same marketplace, same review pipeline. Skills alone cannot share state across accounts. The remote MCP registry (a process someone runs) is the shared store for that host.

- Deploy the server/ directory (stays in this repo; no second repo).
- Set env:

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/mrlynn/grok-bot-plugin-example/HEAD/README.md

## Skills

- check-grok-bot-compatibility: Review a plugin (publisher's or a customer's) for Grok Bot compatibility. Use when auditing a repo before marketplace submit, when an AE/FE is reviewing a customer connector, or when someone asks whether a plugin will work in Grok Bot vs Cursor IDE only. Report mismatches; do not auto-reject.
- check-into-lobby: Lobby presence for approved assistants. Use when the user says "Check into the lobby" or "Check out of the lobby" (canonical phrases). For literal /rooms, /join, or /leave slash commands, use rooms-slash-commands instead (hard registry room commands; this assistant only; default lobby). Refuses una…
- distribution-tiers: Explain public marketplace vs team/private vs "default connector for everyone." Use when a publisher or AE/FE asks how to make a connector available to anyone, only to their team, or installed by default for all Grok Bot users. Be explicit that a default/bundled connector program does not exist.
- get-listed-in-grok-bot: Canonical path to get an MCP server or plugin into Grok Bot. Use when a publisher, customer, or Cursor AE/FE asks how to list a connector in Grok Bot, how to submit to the marketplace, whether github.com/xai-org/plugin-marketplace is the right place, or how to avoid a hand-routed Slack thread.
- grok-bot-smoke: Short hello / load check for this plugin. Use when the user asks whether grok-bot-rooms is installed, wants a quick hello, or is verifying local plugin load. For rooms workflows, prefer welcome-to-lobby, register-my-assistants, rooms-slash-commands, or who-is-in-the-room. For publisher workflows, p…
- register-my-assistants: Onboarding for rooms. Use when the user says "Register my assistants for rooms" (canonical) or asks which assistants are approved for the hosted registry. Lists the real roster, asks who to approve (never auto-approve), calls register_assistants (replaces allowlist), then offers lobby check-in and…
- rooms-slash-commands: HARD room slash commands for the hosted registry. When the user types /rooms, /list-rooms, /join, /leave, /whos-here, or /who (with optional room id; default lobby), ALWAYS treat them as registry room commands, never as Slack, never as "who is on my roster", never as a Grok Bot group-chat question…
- scaffold-grok-bot-plugin: Scaffold a Grok Bot-ready Agent Plugin (root plugin.json, skills, optional mcp.json and variables). Use when a publisher or AE/FE wants to start a new plugin for Grok Bot, convert an MCP server into a marketplace plugin, or needs copy-pasteable file contents rather than a lecture. Prefer this over…
- welcome-to-lobby: FIRST-RUN / FIRST CHAT after installing or configuring this plugin (before other registry flows). Prompt: "Add one of your assistants to the welcome room (lobby)?" Options = real roster names + "Not now". Never auto-pick, never add the whole roster, never silent-join on install. If they pick one: r…
- who-is-in-the-room: Lobby and registration visibility. Use when the user says "Who is in the lobby?" (list_room lobby) or "Who is registered for rooms?" (list_registry, operator-token only). For slash commands /rooms, /whos-here, /who, /join, /leave, prefer rooms-slash-commands, those are hard registry room commands…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- grok-bot-registry: transport: streamable-http; url: ${REGISTRY_URL}

Read from the plugin's own mcp.json. Environment variable names only, never values.