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 Cursor?
Cursor's Agent mode turns Liveblocks (Collaborative) into an in-editor superpower. Ask Cursor to generate code using live data from Liveblocks (Collaborative) and it fetches, processes, and writes. all in a single agentic loop. 19 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Liveblocks (Collaborative) in Cursor
Liveblocks (Collaborative) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Liveblocks (Collaborative) to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Redis Vector
6 toolsEquip your AI to autonomously manage embeddings, run KNN similarity searches, and administrate vector indexes natively inside your Redis stack.

Adobe Acrobat Sign
10 toolsSend, track, and manage e-signatures via Adobe Acrobat Sign — create agreements, check signing status, and access audit trails from any AI agent.

Facebook Pages
12 toolsManage your Facebook Pages via AI — publish posts, list feed, track insights, and engage with comments directly through your agent.

Todoist Alternative
10 toolsManage your Todoist tasks and projects — audit productivity via AI.
