Claude DesktopIDE

Liveblocks (Collaborative) MCP Server

Bring Real Time Sync
to Claude Desktop

Name: Liveblocks (Collaborative) MCP Server
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

Learn how to connect Liveblocks (Collaborative) to Claude Desktop and start using 19 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Authorize UserBroadcast EventCreate RoomCreate ThreadDelete RoomGet RoomGet StorageGet YdocIdentify UserInitialize StorageList Active UsersList RoomsList ThreadsList VersionsPatch StorageResolve ThreadSet PresenceUpdate RoomUpdate Ydoc

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the Liveblocks (Collaborative) MCP Server?

Connect your Liveblocks account to any AI agent to orchestrate real-time collaborative experiences and manage infrastructure through natural conversation.

What you can do

Room Lifecycle — Create, list, update, and delete collaborative rooms with custom metadata and access controls.
Presence & Interaction — Monitor active users in any room, set ephemeral presence, and broadcast custom events to connected clients.
Data Synchronization — Retrieve and patch room storage or Yjs documents to manage shared state across collaborative sessions.
Comments & Feedback — Manage collaborative threads, create new discussions, and resolve existing ones to streamline team feedback.
User Identity — Authorize and identify users with specific permissions and group assignments via secure token generation.

How it works

Subscribe to this server
Enter your Liveblocks Secret Key from the dashboard
Start managing your real-time infrastructure from Claude, Cursor, or any MCP-compatible client

Who is this for?

Product Managers — Monitor active collaboration sessions and review user feedback threads without leaving the chat interface.
Full-stack Developers — Debug room storage, inspect Yjs document states, and manage room permissions directly from the IDE.
Support Teams — Quickly identify active users in a room and verify room configurations to assist customers in real-time.

Built-in capabilities (19)

authorize_user

Obtain an access token with specific permissions

broadcast_event

Broadcast a JSON event to a room

create_room

Create a new room

create_thread

Create a thread and the first comment

delete_room

Delete a room

get_room

Retrieve room details

get_storage

Get the room's Storage tree (LSON or JSON format)

get_ydoc

Get a JSON representation of the Yjs document

identify_user

Obtain an ID token for a user

initialize_storage

Initialize or reinitialize Storage

list_active_users

List users currently in the room

list_rooms

List rooms with filtering and pagination

list_threads

List threads in a room

list_versions

List Yjs version history snapshots

patch_storage

Apply JSON Patch operations to Storage

resolve_thread

Resolve a thread

set_presence

Set ephemeral presence for a user/agent

update_room

Update room properties (metadata, permissions)

update_ydoc

Send a binary Yjs update

Why Claude Desktop?

Claude Desktop is the definitive way to connect Liveblocks (Collaborative) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 19 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

—
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
—
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
—
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
—
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

See it in action

Liveblocks (Collaborative) in Claude Desktop

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

Liveblocks (Collaborative) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Liveblocks (Collaborative) to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	Raw MCP	Vinkius
Server catalog	Find and host yourself	4,000+ managed
Infrastructure	Self-hosted	Sandboxed V8 isolates
Credential handling	Plaintext in config	Vault + runtime injection
Data loss prevention	None	Configurable DLP policies
Kill switch	None	Global instant shutdown
Financial circuit breakers	None	Per-server limits + alerts
Audit trail	None	Ed25519 signed logs
SIEM log streaming	None	Splunk, Datadog, Webhook
Honeytokens	None	Canary alerts on leak
Custom domains	Not applicable	DNS challenge verified
GDPR compliance	Manual effort	Automated purge + export

Unlock for AI Agents View step-by-step setup guide for Claude Desktop →

Enterprise Security

Why teams choose Vinkius for Liveblocks (Collaborative) in Claude Desktop

The Liveblocks (Collaborative) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 19 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Unlock for AI Agents View full Liveblocks (Collaborative) details →

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures
Liveblocks (Collaborative) for Claude Desktop

Every tool call from Claude Desktop to the Liveblocks (Collaborative) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

How can I see which users are currently active in a specific collaboration room?

You can use the list_active_users tool by providing the Room ID. The agent will return a list of all users currently connected to that room, including their connection IDs and associated info.

Is it possible to inspect or modify the shared state of a room from the AI?

Yes! Use get_storage to retrieve the current LSON/JSON storage tree or patch_storage to update specific keys in the room's shared state. For Yjs-based rooms, you can use get_ydoc and update_ydoc.

Can I manage user comments and discussion threads through this integration?

Absolutely. You can use list_threads to see all discussions in a room, create_thread to start a new one, and resolve_thread to mark a discussion as completed.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).