Rooms are only the front of it: threads, comments, reactions, per-user subscription settings and inbox notifications all get full read-and-write coverage, which puts moderation and support work in the client instead of in a dashboard you built. create-thread and create-comment both instruct the caller to ask for a userId, so authorship is supplied rather than guessed, and get-storage-document and get-yjs-document hand back document contents with no running app in the loop.
An administration surface over a Liveblocks project: rooms and their access lists, storage and Yjs documents, comment threads and comments, subscriptions and inbox notifications, 39 tools in all.
- Rooms created, read, updated, renamed by ID and deleted, with default, per-user and per-group access levels plus metadata
- The active users in a room, and an event broadcast to everyone connected to it
- A room's storage document and its Yjs text document read out as data
- Comment threads listed, opened, resolved or unresolved, edited in metadata, subscribed to and deleted
- Comments created, edited, deleted and reacted to inside a thread, with participants and subscriptions listed
- Room subscription settings per user, and one user's settings across rooms
- Inbox notifications listed, opened, deleted one at a time or all at once, and custom ones triggered with an activity payload
A Liveblocks project — rooms, threads and notifications are addressed by roomId and userId within one account.
One command plus a key — npx -y github:liveblocks/liveblocks-mcp-server, then supply credentials