add-comment-reaction
Add a reaction to a Liveblocks comment
LABSCO SUMMARY
The comment and notification surface is as large as the room surface.
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.
What it is
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.
What you get
- 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
Requirements
A Liveblocks project — rooms, threads and notifications are addressed by roomId and userId within one account.
Setup effort
One command plus a key — npx -y github:liveblocks/liveblocks-mcp-server, then supply credentials
USE CASES
01
Standing up a room with the right people in it
Create the room with the access levels it should have, adjust them once the user and group lists settle, and check who is connected to it now.
02
Renaming a room after the slug behind it changed
Find the room in the recent list, then move it to the new ID in one call rather than recreating it.
03
Reading what a document holds without running the app
Pull the room's storage document, and the Yjs text document alongside it, as data you can inspect directly.
04
Clearing a comment thread that has gone stale
List the threads on the room, open the one in question, mark it resolved, or delete it when there is nothing left to keep.
05
Answering a customer comment as the support account
Add the reply as a comment under the thread, correct it if it went out wrong, and acknowledge the original with a reaction.
06
Telling one person something happened without notifying the room
Trigger a custom notification for that user, confirm it landed in their inbox, and set their subscription for the room so the next one follows the same rule.
39 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
broadcast-event
Broadcast an event to a Liveblocks room
create-comment
Create a Liveblocks comment. Always ask for a userId.
create-room
Create a Liveblocks room
create-thread
Create a Liveblocks thread. Always ask for a userId.
delete-all-inbox-notifications
Delete all Liveblocks inbox notifications
delete-comment
Delete a Liveblocks comment
delete-inbox-notification
Delete a Liveblocks inbox notification
delete-notification-settings
Delete Liveblocks notification settings
delete-room
Delete a Liveblocks room
delete-room-subscription-settings
Delete a Liveblocks room's subscription settings
delete-thread
Delete a Liveblocks thread
edit-comment
Edit a Liveblocks comment
edit-thread-metadata
Edit a Liveblocks thread's metadata. null can be used to remove a key.
get-active-users
Get a Liveblocks room's active users
get-comment
Get a Liveblocks comment
get-inbox-notification
Get a Liveblocks inbox notification
get-inbox-notifications
Get recent Liveblocks inbox notifications
get-notification-settings
Get a Liveblocks notification settings
get-room
Get a Liveblocks room
get-room-subscription-settings
Get a Liveblocks room's subscription settings
get-rooms
Get recent Liveblocks rooms
get-storage-document
Get a Liveblocks storage document
get-thread
Get a Liveblocks thread
get-thread-participants
Get a Liveblocks thread's participants
get-thread-subscriptions
Get a Liveblocks thread's subscriptions
get-threads
Get recent Liveblocks threads
get-user-room-subscription-settings
Get a user's room subscription settings
get-yjs-document
Get a Liveblocks Yjs text document
mark-thread-as-resolved
Mark a Liveblocks thread as resolved
mark-thread-as-unresolved
Mark a Liveblocks thread as unresolved
remove-comment-reaction
Remove a reaction from a Liveblocks comment
subscribe-to-thread
Subscribe to a Liveblocks thread
trigger-inbox-notification
Create a custom Liveblocks inbox notification
unsubscribe-from-thread
Unsubscribe from a Liveblocks thread
update-notification-settings
Update Liveblocks notification settings
update-room
Update a Liveblocks room
update-room-id
Update a Liveblocks room's ID
update-room-subscription-settings
Update a Liveblocks room's subscription settings
BEFORE YOU INSTALL
What to know first
Tools you get
39 tools when we connected. Rooms, threads, comments and notifications can be created, modified and deleted; Storage and Yjs are read-only (get-storage-document, get-yjs-document).
Requires
LIVEBLOCKS_SECRET_KEY in your environment
CONTEXT COST
Moderate Standing cost
Rated by the size of the 39 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y github:liveblocks/liveblocks-mcp-serverMCP Clients
Cursor, Claude Desktop
JSON
{
"mcpServers": {
"liveblocks": {
"command": "npx",
"args": [
"-y",
"github:liveblocks/liveblocks-mcp-server"
],
"env": {
"LIVEBLOCKS_SECRET_KEY": "<YOUR_LIVEBLOCKS_SECRET_KEY>"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add liveblocks -e LIVEBLOCKS_SECRET_KEY=<YOUR_LIVEBLOCKS_SECRET_KEY> -- npx -y github:liveblocks/liveblocks-mcp-serverCodex
CODEX · TERMINAL
codex mcp add liveblocks \
--env LIVEBLOCKS_SECRET_KEY=<YOUR_LIVEBLOCKS_SECRET_KEY> \
-- npx -y github:liveblocks/liveblocks-mcp-server
