VS Code CopilotIDE

Liveblocks MCP Server

Bring Real Time Collaboration
to VS Code Copilot

Name: Liveblocks MCP Server
Price: 29 USD
Availability: InStock
Rating: 0.2 (1 reviews)
Author: Vinkius

Learn how to connect Liveblocks to VS Code Copilot 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 Subscribers

Authorize UserBroadcast EventCreate RoomCreate ThreadDelete RoomGet RoomGet StorageGet ThreadGet YdocIdentify UserInitialize StorageList Active UsersList RoomsList ThreadsPatch StorageResolve ThreadUpdate RoomUpdate Ydoc

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

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_user and identify_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)

authorize_user

Obtain an access token for a client to enter a room

broadcast_event

Broadcast a JSON event to a room

create_room

Create a new room

create_thread

Create a thread and the first comment

delete_room

Delete a room

get_room

Retrieve room details

get_storage

Get the room's Storage tree

get_thread

Get a specific thread

get_ydoc

Get a JSON representation of the Yjs document

identify_user

Permissions are managed on the backend. Obtain an ID token for a client

initialize_storage

Initialize or reinitialize Storage

list_active_users

List users currently in the room

list_rooms

Can be filtered by metadata or access. List rooms with filtering and pagination

list_threads

List threads in a room

patch_storage

Apply JSON Patch operations to Storage

resolve_thread

Resolve a thread

update_room

Update room properties

update_ydoc

Send a binary Yjs update

Why VS Code Copilot?

GitHub Copilot Agent mode brings Liveblocks data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 18 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

—
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
—
Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
—
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
—
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

Liveblocks in VS Code Copilot

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

Liveblocks and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Liveblocks to VS Code Copilot 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.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	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

Unlock for AI Agents View step-by-step setup guide for VS Code Copilot →

Enterprise Security

Why teams choose Vinkius for Liveblocks in VS Code Copilot

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 VS Code Copilot 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.

Unlock for AI Agents View full Liveblocks details →

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures
Liveblocks for VS Code Copilot

Every tool call from VS Code Copilot to the Liveblocks MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

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.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.