Skip to main content
mcpSource-backedReview first Safety Privacy

Liveblocks MCP Server for Claude

Manage Liveblocks real-time collaboration infrastructure from Claude — create and manage rooms, broadcast events, retrieve collaborative storage and Yjs documents, manage threads and comments, handle inbox notifications, and configure notification settings — with the official Liveblocks MCP server.

HarnessClaude CodeCodexCursorClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Safety notes

  • Tools can create, update, and delete rooms, threads, and comments — changes affect your live Liveblocks collaboration infrastructure.
  • Broadcasting events via `broadcast-event` sends real-time messages to all connected users in a room immediately.

Privacy notes

  • Room metadata, collaborative storage content, Yjs document state, thread and comment content, and user notification settings from your Liveblocks project are surfaced in Claude's context.
  • Your `LIVEBLOCKS_SECRET_KEY` grants full project API access — keep it out of source control and only add it to a trusted MCP config after selecting a verified install source.

Prerequisites

  • A Liveblocks account — sign up at liveblocks.io.
  • A Liveblocks secret key from the Dashboard: Project Settings → API Keys → Secret key.
  • An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
config
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
Ask Claude to list all active Liveblocks rooms, retrieve the collaborative storage state from a room, broadcast an event to all connected users, manage comment threads, or check inbox notifications for a specific user — using natural language against the Liveblocks API.

About this resource

Overview

The Liveblocks MCP Server is the official Model Context Protocol server from Liveblocks, the platform for building real-time collaborative features. It provides 39 tools covering rooms, collaborative storage, Yjs documents, threads, comments, inbox notifications, and notification settings — giving Claude direct management access to your Liveblocks collaboration infrastructure. Apache-2.0 licensed.

Note: This entry is not marked installable because the upstream MCP server is currently documented as a direct GitHub install rather than a versioned package registry artifact. Wait for a published package, signed release, or maintainer-reviewed immutable commit pin before adding it to Claude.

Key capabilities

  • Rooms — create, get, update, and delete collaboration rooms; get active users.
  • Events — broadcast real-time events to all users in a room.
  • Storage — retrieve collaborative storage documents.
  • Yjs documents — get Yjs document state from rooms.
  • Threads — create, manage, and resolve comment threads.
  • Comments — create, edit, and react to comments within threads.
  • Inbox notifications — get, trigger, and mark notifications.
  • Notification settings — update and retrieve notification preferences.

Tools (39 total, key selection)

Tool Category Purpose
get-rooms / create-room / update-room / delete-room Rooms Room lifecycle
get-active-users Rooms List active users in a room
broadcast-event Events Send real-time event to room users
get-storage-document Storage Retrieve collaborative storage state
get-yjs-document Storage Get Yjs document from a room
get-threads / create-thread / edit-thread-metadata / mark-thread-as-resolved Threads Thread management
create-comment / edit-comment / add-comment-reaction Comments Comment management
get-inbox-notifications / trigger-inbox-notification Notifications Inbox management
subscribe-to-thread / unsubscribe-from-thread Notifications Thread subscriptions
get-notification-settings / update-notification-settings Settings Notification prefs

How it compares

Server Real-time rooms Collaborative storage Thread/comments Inbox Notes
Liveblocks MCP Yes Yes Yes Yes Official, 39 tools
Pusher MCP Yes (channels) No No No Event broadcasting
Socket.io MCP Limited No No No Community

Liveblocks MCP is the only real-time collaboration infrastructure MCP with integrated comment threads, Yjs document access, and inbox notification management.

Installation

This entry intentionally does not provide a copyable install command yet. The upstream documentation currently uses a mutable GitHub package specifier, which can execute whatever code is on the repository default branch at install time. Use this MCP server only after Liveblocks publishes a versioned package, signed release, or immutable commit-pinned install source that you have reviewed and trust.

Get your secret key from Dashboard → Project Settings → API Keys → Secret key (format: sk_prod_... or sk_dev_...).

Requirements

  • A Liveblocks account with at least one project.
  • Secret key (sk_...) from the Liveblocks Dashboard.
  • A reviewed, immutable install source for the MCP server.
  • An MCP client (Claude Code or Claude Desktop).

Security

  • LIVEBLOCKS_SECRET_KEY grants full project API access — never commit it or share it.
  • Broadcasting events is instant — confirm the target room before triggering.
  • Use separate sk_dev_... keys for development to avoid affecting production rooms.
  • Avoid running mutable GitHub package specifiers directly with npx; prefer a versioned package, signed release, or reviewed immutable commit pin.

Source Verification Notes

Verified on 2026-06-18:

  • Official repository liveblocks/liveblocks-mcp-server (Apache-2.0) documents LIVEBLOCKS_SECRET_KEY configuration (format sk_...), all 39 tools across rooms, events, storage, Yjs, threads, comments, inbox notifications, and notification settings.
  • Claude Code MCP documentation at code.claude.com/docs/en/mcp describes the stdio connector pattern used above.

Source citations

Add this badge to your README

Show that Liveblocks MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/liveblocks-mcp-server.svg)](https://heyclau.de/entry/mcp/liveblocks-mcp-server)

How it compares

Liveblocks MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldLiveblocks MCP Server for Claude

Manage Liveblocks real-time collaboration infrastructure from Claude — create and manage rooms, broadcast events, retrieve collaborative storage and Yjs documents, manage threads and comments, handle inbox notifications, and configure notification settings — with the official Liveblocks MCP server.

Open dossier
Android Skills MCP Server for Claude

Access AI-optimized Android development guides from Claude — search and retrieve SKILL.md content covering Jetpack Compose, Navigation 3, CameraX, AGP 9, App Functions, Edge-to-Edge, Android Profilers, XR, Google Play, and the Android CLI — with the Android Skills MCP server.

Open dossier
Appwrite MCP Server for Claude

Connect Claude to the full Appwrite backend platform — databases, authentication, serverless functions, teams, messaging, and storage — with the official Appwrite MCP server using dynamic dispatch across the entire Appwrite API surface.

Open dossier
Backlog MCP Server for Claude

Manage Backlog projects from Claude — create and update issues, comment on tickets, manage wiki pages, review pull requests, and navigate your Nulab Backlog space — with the official Backlog MCP server supporting stdio and HTTP transports.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorLiveblocksJaewoong Eum (skydoves)AppwriteNulab
Added2026-06-182026-06-182026-06-182026-06-18
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesTools can create, update, and delete rooms, threads, and comments — changes affect your live Liveblocks collaboration infrastructure. Broadcasting events via `broadcast-event` sends real-time messages to all connected users in a room immediately.The server runs entirely offline — no network requests are made during queries. All skill content is bundled with the npm package.Mutation operations (write, update, delete) require `confirm_write=true` to be passed explicitly, adding a confirmation step before any destructive action. The API key scope determines what operations are available — use least-privilege scopes for your use case.Tools can create, update, and delete projects, issues, wikis, and pull requests — changes affect your live Backlog space. Use `ENABLE_TOOLSETS` to restrict which tool groups are available if you only need read access.
Privacy notesRoom metadata, collaborative storage content, Yjs document state, thread and comment content, and user notification settings from your Liveblocks project are surfaced in Claude's context. Your `LIVEBLOCKS_SECRET_KEY` grants full project API access — keep it out of source control and only add it to a trusted MCP config after selecting a verified install source.No API keys, user data, or query content is sent to any external service. All lookups happen locally against the bundled skill snapshot.User records, database documents, function logs, team memberships, and messaging data from your Appwrite project are surfaced in Claude's context. Your `APPWRITE_API_KEY` grants project-level access — keep it in the MCP config env and never commit it to version control.Issue content, comments, wiki pages, pull request details, and user information from your Backlog space are surfaced in Claude's context. Your `BACKLOG_API_KEY` grants account-level Backlog access — keep it in the MCP config env and never commit it to version control.
Prerequisites
  • A Liveblocks account — sign up at liveblocks.io.
  • A Liveblocks secret key from the Dashboard: Project Settings → API Keys → Secret key.
  • An MCP client such as Claude Code or Claude Desktop.
  • Node.js with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.
  • An Appwrite account — log in at cloud.appwrite.io or self-hosted.
  • An Appwrite project with an API key that has the required scopes for your use case.
  • Python with `uvx` available.
  • An MCP client such as Claude Code or Claude Desktop.
  • A Backlog account on backlog.com or your Backlog.jp/enterprise space.
  • A Backlog API key: Personal Settings → API → Generate API Key.
  • Node.js with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.
Install
claude mcp add android-skills -- npx -y android-skills-mcp
claude mcp add appwrite -e APPWRITE_PROJECT_ID=<project-id> -e APPWRITE_API_KEY=<api-key> -- uvx mcp-server-appwrite
claude mcp add backlog -e BACKLOG_DOMAIN=yourspace.backlog.com -e BACKLOG_API_KEY=<your-api-key> -- npx backlog-mcp-server
Config
{
  "mcpServers": {
    "liveblocks": {
      "command": "<reviewed-immutable-liveblocks-mcp-command>",
      "env": {
        "LIVEBLOCKS_SECRET_KEY": "sk_<your-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "android-skills": {
      "command": "npx",
      "args": ["-y", "android-skills-mcp"]
    }
  }
}
{
  "mcpServers": {
    "appwrite": {
      "command": "uvx",
      "args": ["mcp-server-appwrite"],
      "env": {
        "APPWRITE_PROJECT_ID": "<project-id>",
        "APPWRITE_API_KEY": "<api-key>",
        "APPWRITE_ENDPOINT": "https://cloud.appwrite.io/v1"
      }
    }
  }
}
{
  "mcpServers": {
    "backlog": {
      "command": "npx",
      "args": ["backlog-mcp-server"],
      "env": {
        "BACKLOG_DOMAIN": "yourspace.backlog.com",
        "BACKLOG_API_KEY": "<your-api-key>",
        "MAX_TOKENS": "50000"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.