Compatible with every major AI agent and IDE
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 Claude Desktop?
Claude Desktop is the definitive way to connect Liveblocks to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 18 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
Liveblocks in Claude Desktop
Liveblocks and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Liveblocks 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.
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 Claude Desktop
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 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.

* 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 Claude Desktop
Every tool call from Claude Desktop 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.
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).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Thoughtly
11 toolsDeploy AI voice agents to make or receive calls, manage CRM contacts, and access call histories instantly.

Fanart.tv
8 toolsGet high-quality artwork for movies, TV shows and music — posters, fanart, logos, banners and more.

3Scribe
4 toolsAutomated audio and video transcription — create jobs, monitor progress, and retrieve text via AI.

Billsby
10 toolsManage subscription billing via Billsby — list customers, subscriptions, and invoices directly from any AI agent.
