Compatible with every major AI agent and IDE
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)
Obtain an access token with specific permissions
Broadcast a JSON event to a room
Create a new room
Create a thread and the first comment
Delete a room
Retrieve room details
Get the room's Storage tree (LSON or JSON format)
Get a JSON representation of the Yjs document
Obtain an ID token for a user
Initialize or reinitialize Storage
List users currently in the room
List rooms with filtering and pagination
List threads in a room
List Yjs version history snapshots
Apply JSON Patch operations to Storage
Resolve a thread
Set ephemeral presence for a user/agent
Update room properties (metadata, permissions)
Send a binary Yjs update
Why Cline?
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Liveblocks (Collaborative) tool calls without waiting for prompts between steps. Connect 19 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
- —
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
- —
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
- —
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
- —
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Liveblocks (Collaborative) in Cline
Liveblocks (Collaborative) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Liveblocks (Collaborative) to Cline 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.
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 |
Why teams choose Vinkius for Liveblocks (Collaborative) in Cline
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 Cline 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.

* 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
How Vinkius secures
Liveblocks (Collaborative) for Cline
Every tool call from Cline to the Liveblocks (Collaborative) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
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 Cline connect to MCP servers?
Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
Can Cline run MCP tools without approval?
By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
Does Cline support multiple MCP servers at once?
Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.
Server shows error in sidebar
Click the server name to see logs. Verify the URL and token are correct.
Explore More MCP Servers
View all →
Rev.com
11 toolsAutomate human-powered transcription via Rev.com — manage orders, captions, and file metadata with AI.

Planable
10 toolsCollaborate, approve, and manage your social media content calendar autonomously using AI.

Paperspace
6 toolsProvision and track powerful GPU workloads via Paperspace — list compute instances, fetch active deployments, trace team projects, and query Gradient environments via AI.

Factorial
8 toolsModernize HR operations with time-off management, payroll processing, and performance reviews that employees actually enjoy using.
