Bring Real Time Collaboration
to Cursor
Learn how to connect Liveblocks to Cursor and start using 18 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Liveblocks MCP Server?
Connect your Liveblocks account to any AI agent to orchestrate multiplayer experiences and real-time collaboration features through natural language.
What you can do
- Room Management — List, create, update, and delete rooms to manage your application's collaborative spaces.
- User Authentication — Generate access tokens and identify users with specific permissions using
authorize_userandidentify_user. - Collaborative Storage — Inspect and patch room storage state or manage Yjs documents for shared editing.
- Comments & Threads — Query, create, and resolve comment threads to keep track of team discussions within rooms.
- Real-time Presence — List active users in a room or broadcast custom events to connected clients.
How it works
- Subscribe to this server
- Enter your Liveblocks Secret Key
- Start managing your real-time infrastructure from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Full-stack Developers — quickly debug room storage, manage user permissions, or clear stale rooms without leaving the terminal or IDE.
- Product Managers — monitor active collaboration sessions and review comment threads across different project rooms.
- DevOps Engineers — automate the provisioning of collaborative environments and manage access rules programmatically.
Built-in capabilities (18)
Obtain an access token for a client to enter a room
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
Get a specific thread
Get a JSON representation of the Yjs document
Permissions are managed on the backend. Obtain an ID token for a client
Initialize or reinitialize Storage
List users currently in the room
Can be filtered by metadata or access. List rooms with filtering and pagination
List threads in a room
Apply JSON Patch operations to Storage
Resolve a thread
Update room properties
Send a binary Yjs update
Why Cursor?
Cursor's Agent mode turns Liveblocks into an in-editor superpower. Ask Cursor to generate code using live data from Liveblocks and it fetches, processes, and writes. all in a single agentic loop. 18 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 in Cursor
Liveblocks and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Liveblocks 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 in Cursor
The Liveblocks 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 18 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 for Cursor
Every tool call from Cursor to the Liveblocks 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 filter rooms by specific metadata using the AI?
You can ask the agent to use the list_rooms tool and provide a JSON string in the metadata parameter. For example, ask to 'List rooms where the project metadata is alpha'.
Can I generate a temporary access token for a user to join a room?
Yes. Use the authorize_user tool. Provide the Room ID and User ID, and the agent will return a token that grants access to that specific room.
Is it possible to permanently delete a room and its data?
Yes, the delete_room tool allows you to permanently remove a room and all associated storage, comments, and metadata. Use this with caution as it is irreversible.
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 →
Applitools
10 toolsBring AI-powered visual testing to your AI agent — inspect test batches, review UI diffs, and manage your visual baselines naturally.
Xiaoshouyi / Neocrm
9 toolsChina's leading enterprise CRM platform — manage leads, accounts, and opportunities via AI.
Eurostat Trade — EU International Commerce
5 toolsEU international trade data: imports and exports by partner country and product classification (SITC), industrial production index, retail trade volume, and services sector statistics for all 27 EU member states.
Lacework (Cloud Security & CNAPP)
10 toolsSecure your cloud via Lacework — search security alerts, monitor vulnerabilities, and audit cloud asset inventory.