Liveblocks (Collaborative) MCP. Manage live collaboration and shared data states.

Q: How do I use Liveblocks (Collaborative) MCP to check users?

You use the listactiveusers tool. Just prompt your agent and tell it which room you want to check, and the system returns a real-time list of all connected participants.

Q: Can I reset shared document state with Liveblocks (Collaborative) MCP?

Yes, you use initializestorage. This function sets up or resets the room's storage area, giving it a clean starting point for new collaboration sessions.

Q: What is the difference between getydoc and getstorage?

The getydoc tool retrieves the shared state using Yjs format, which is best for structured data. Use getstorage when you need the full, general contents of the room's storage area.

Q: How do I make a new collaboration space?

You use the createroom tool. You provide details like the name and initial access controls, and the MCP handles generating the necessary infrastructure for you.

Q: Can Liveblocks (Collaborative) MCP handle user permissions?

Yes. You can use authorizeuser to generate tokens with specific read/write scopes, and updateroom to adjust overall room permissions.

Liveblocks (Collaborative) lets your AI agent manage real-time, shared infrastructure directly from conversation. Use this MCP to control collaborative rooms, monitor who is in a session, and synchronize complex documents across multiple users without touching an API endpoint. It's the complete toolset for orchestrating live state management.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Give Claude and any AI agent real-world access

Manage Room Lifecycle

Create, read, update, or delete collaborative rooms with specific access controls.

Track User Presence

Monitor which users are active in a room and set temporary presence indicators for agents.

Synchronize Shared Data

Retrieve or update the content stored within a room's document state (Yjs).

Control Collaborative Threads

Create new discussion threads and manage existing feedback loops.

Ask an AI about this

Waiting for input…

AI Agent

What AI agents can do with Liveblocks (Collaborative): 19 Tools

Use these tools to manage every aspect of a live collaboration workspace, from creating rooms and tracking users to synchronizing complex document states.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Liveblocks (Collaborative) MCP

List Active Users

Gets a list of all users currently connected to a specified room.

Authorize User

Generates an access token for a user, applying specific permissions and scopes.

Broadcast Event

Sends a structured JSON event to all clients connected within a room.

Create Room

Initializes an entirely new collaborative workspace with defined metadata and access...

Create Thread

Starts a new discussion thread within a room, automatically posting the initial...

Delete Room

Permanently removes an existing collaborative workspace and all its contents.

Get Room

Retrieves comprehensive details about a specific room, including its current status and metadata.

Get Storage

Fetches the entire contents of the room's shared storage in JSON or LSON format.

Get Ydoc

Retrieves a snapshot of the document state using Yjs for structured data inspection.

Identify User

Obtains an ID token needed to verify and identify a user's presence in the system.

Initialize Storage

Sets up or resets the shared storage area for a room, giving it a clean slate.

List Rooms

Lists all existing rooms, allowing filtering and pagination based on metadata.

List Threads

Retrieves a list of all discussion threads associated with a particular room.

List Versions

Shows historical snapshots and version control logs for the shared document state.

Patch Storage

Applies specific JSON Patch operations to update only a small part of the room's...

Resolve Thread

Marks a discussion thread as resolved, closing out the conversation topic.

Set Presence

Sets or updates the ephemeral presence status for an agent or user within a room.

Update Room

Changes properties of a room, including its metadata and access permissions.

Update Ydoc

Sends binary updates to modify the core Yjs document state.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Liveblocks (Collaborative) MCP is compatible with Claude

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The Liveblocks (Collaborative) integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "liveblocks-collaborative": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the Liveblocks (Collaborative) tools with full Vinkius guardrails applied.

Liveblocks (Collaborative) MCP is compatible with VS Code

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"liveblocks-collaborative": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on each call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with Liveblocks (Collaborative), then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,200+ others, all in one place
Add new capabilities to your AI anytime you want
Connections are secured and governed automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog weekly

Liveblocks (Collaborative) MCP server cover

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Liveblocks. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS CLOUD

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on each call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

The headache of stitching together real-time project status.

Right now, managing a collaborative project means jumping through hoops. You check Slack for who is available. Then you click into Figma to see what design assets are shared. Next, you open the wiki to review documentation and finally, you run an internal script just to confirm who was logged in when the last decision was made. It's tedious clicking across five different tabs.

With this MCP, your agent handles it all. You tell it: 'Check the status of the Q3 marketing room.' The agent immediately calls `get_room` and `list_active_users`, giving you a single, consolidated report that tells you who's present, what the current storage state is, and if any critical threads need attention. It just works.

Getting instant room status with Liveblocks (Collaborative)

Manual checking of user presence means opening a dashboard, filtering by date, and copying names—a process that takes minutes and is always out of sync. You also have to manually check if the project storage was properly initialized.

Now, you simply ask your agent to verify the room's status. It calls `get_room` and confirms the metadata and permissions instantly. The visibility into who's present and what the state is changes everything; it gives you actionable intelligence immediately.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

real-time-sync

multiplayer-experience

presence-tracking

collaborative-editing

web-sockets

state-management

What Liveblocks (Collaborative) MCP does for your AI

This connector lets you treat your entire real-time backend—room creation, user presence, shared document storage, and discussion threads—as just another function call in a conversation. You can instruct your agent to create an entirely new project space, automatically assign permissions, and then instantly get a full list of who’s currently working in it.

Need to update the core data or patch a specific section of shared notes? Your agent handles that, treating complex document states like simple variables.

It's built for environments where state changes constantly; think live code editors, collaborative whiteboards, or multiplayer game lobbies. Instead of juggling multiple dashboards and manual API calls, you talk to your AI client, and it interacts with the infrastructure via Vinkius. This lets developers debug room storage, PMs review user feedback threads, and support staff verify permissions—all in one place.

Built · Hosted · Managed by Vinkius Liveblocks Collaborative MCP - Real-time State Sync

Server ID 019e38b8-c89d-701e-9e1c-bfac05464d96

Vinkius Inspector

Compliance Grade F

Score 3.6/100

Report View Report ↗

Benefits of connecting Liveblocks (Collaborative) MCP

You can stop manually checking multiple dashboards for who's online. Use the list_active_users tool to instantly verify all active participants in any room, keeping your support process fast and accurate.

Debugging document state used to mean pulling raw JSON files. Now you use get_ydoc or get_storage to get a clean, actionable snapshot of shared data directly into your chat context.

When project scope changes, you don't need an admin ticket. Use create_room and update_room together to spin up new collaboration spaces and set precise permissions instantly.

Managing team feedback is easier than ever. Instead of losing threads in email chains, the agent can use create_thread, list_threads, and eventually resolve_thread to keep discussions organized right where they happen.

Need to replicate a development environment? The ability to call initialize_storage resets your workspace instantly, giving you a clean slate for testing without manual cleanup.

Liveblocks (Collaborative) MCP use cases

01 01

Onboarding a new client team

A PM needs to set up a private working space. They ask their agent: 'Create a room called Q3 Strategy with write access and list the available rooms.' The agent uses create_room and then calls list_rooms, giving the PM immediate confirmation they're in the right place.

02 02

Live debugging shared documents

A developer finds a bug in shared notes. They prompt: 'What is the current state of the core document?' The agent uses get_ydoc to retrieve the structured data, allowing the dev to see exactly what's wrong without manually inspecting logs.

03 03

Support ticket escalation

A support engineer needs to verify if a user can access a feature. They prompt: 'Check all permissions for Project X.' The agent runs get_room and then uses list_active_users to confirm who was last in the room, providing comprehensive context.

04 04

Starting a new design cycle

A team leader needs to gather feedback. They ask: 'Start a thread about the landing page copy and notify everyone.' The agent executes create_thread and then uses broadcast_event to alert all current users in the room.

Liveblocks (Collaborative) MCP tradeoffs

What to watch out for, and the recommended way to handle each one.

Treating it like simple CRUD

Avoid

Trying to use this MCP just to read a single user's profile or update a contact record. This tool is built for live, shared sessions.

Instead

If you only need basic data records (like names and emails), use a standard database MCP instead. Only use Liveblocks when the state of collaboration is the core requirement.

Forgetting permissions

Avoid

Attempting to delete a room or patch storage without first confirming who can do it. The operation will fail with vague permission errors.

Instead

Always start by calling list_active_users and then use authorize_user if you need to grant specific permissions before attempting a destructive action like delete_room.

Misunderstanding data flow

Avoid

Treating the shared storage as simple text. You can't just write 'Hi' and expect it to stick—it needs proper structure.

Instead

To modify content, you must use patch_storage with a defined JSON Patch operation, or send a binary update using update_ydoc. Don't try to manually format the data.

When to use Liveblocks (Collaborative) MCP

Use this MCP when your business logic revolves around shared state and real-time presence. If you need an AI agent to know who is currently viewing, editing, or discussing something in a live environment, this is required. Specifically, if you need the capability to check active users with list_active_users or synchronize documents using get_ydoc, use it. Don't use it if your primary goal is simple data storage (use a dedicated database MCP) or if you only need to manage user accounts without tracking their activity in specific rooms. This tool handles the 'session layer,' not just the 'data layer.'

Frequently asked questions about Liveblocks (Collaborative) MCP

How do I use Liveblocks (Collaborative) MCP to check users? +

You use the list_active_users tool. Just prompt your agent and tell it which room you want to check, and the system returns a real-time list of all connected participants.

Can I reset shared document state with Liveblocks (Collaborative) MCP? +

Yes, you use initialize_storage. This function sets up or resets the room's storage area, giving it a clean starting point for new collaboration sessions.

What is the difference between get_ydoc and get_storage? +

The get_ydoc tool retrieves the shared state using Yjs format, which is best for structured data. Use get_storage when you need the full, general contents of the room's storage area.

How do I make a new collaboration space? +

You use the create_room tool. You provide details like the name and initial access controls, and the MCP handles generating the necessary infrastructure for you.

Can Liveblocks (Collaborative) MCP handle user permissions? +

Yes. You can use authorize_user to generate tokens with specific read/write scopes, and update_room to adjust overall room permissions.

Give Claude and any AI agent real-world access

What AI agents can do with Liveblocks (Collaborative): 19 Tools

List Active Users

Gets a list of all users currently connected to a specified room.

Authorize User

Generates an access token for a user, applying specific permissions and scopes.

Broadcast Event

Sends a structured JSON event to all clients connected within a room.

Create Room

Initializes an entirely new collaborative workspace with defined metadata and access...

Create Thread

Starts a new discussion thread within a room, automatically posting the initial...

Delete Room

Permanently removes an existing collaborative workspace and all its contents.

Get Room

Retrieves comprehensive details about a specific room, including its current status and metadata.

Get Storage

Fetches the entire contents of the room's shared storage in JSON or LSON format.

Get Ydoc

Retrieves a snapshot of the document state using Yjs for structured data inspection.

Identify User

Obtains an ID token needed to verify and identify a user's presence in the system.

Initialize Storage

Sets up or resets the shared storage area for a room, giving it a clean slate.

List Rooms

Lists all existing rooms, allowing filtering and pagination based on metadata.

List Threads

Retrieves a list of all discussion threads associated with a particular room.

List Versions

Shows historical snapshots and version control logs for the shared document state.

Patch Storage

Applies specific JSON Patch operations to update only a small part of the room's...

Resolve Thread

Marks a discussion thread as resolved, closing out the conversation topic.

Set Presence

Sets or updates the ephemeral presence status for an agent or user within a room.

Update Room

Changes properties of a room, including its metadata and access permissions.

Update Ydoc

Sends binary updates to modify the core Yjs document state.

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

The headache of stitching together real-time project status.

Getting instant room status with Liveblocks (Collaborative)

real-time-sync

multiplayer-experience

presence-tracking