4,000+ servers built on vurb.ts
Vinkius

Liveblocks MCP Server for VS Code CopilotGive VS Code Copilot instant access to 18 tools to Authorize User, Broadcast Event, Create Room, and more

MCP Inspector GDPR Free for Subscribers

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this MCP Server for VS Code Copilot

The Liveblocks MCP Server for VS Code Copilot is a standout in the Productivity category — giving your AI agent 18 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "liveblocks": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Liveblocks and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Liveblocks
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

About Liveblocks MCP Server

Connect your Liveblocks account to any AI agent to orchestrate multiplayer experiences and real-time collaboration features through natural language.

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.

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.

The Liveblocks MCP Server exposes 18 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 18 Liveblocks tools available for VS Code Copilot

When VS Code Copilot connects to Liveblocks through Vinkius, your AI agent gets direct access to every tool listed below — spanning real-time-collaboration, room-management, user-presence, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

authorize

Authorize user on Liveblocks

Obtain an access token for a client to enter a room

broadcast

Broadcast event on Liveblocks

Broadcast a JSON event to a room

create

Create room on Liveblocks

Create a new room

create

Create thread on Liveblocks

Create a thread and the first comment

delete

Delete room on Liveblocks

Delete a room

get

Get room on Liveblocks

Retrieve room details

get

Get storage on Liveblocks

Get the room's Storage tree

get

Get thread on Liveblocks

Get a specific thread

get

Get ydoc on Liveblocks

Get a JSON representation of the Yjs document

identify

Identify user on Liveblocks

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

initialize

Initialize storage on Liveblocks

Initialize or reinitialize Storage

list

List active users on Liveblocks

List users currently in the room

list

List rooms on Liveblocks

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

list

List threads on Liveblocks

List threads in a room

patch

Patch storage on Liveblocks

Apply JSON Patch operations to Storage

resolve

Resolve thread on Liveblocks

Resolve a thread

update

Update room on Liveblocks

Update room properties

update

Update ydoc on Liveblocks

Send a binary Yjs update

Connect Liveblocks to VS Code Copilot via MCP

Follow these steps to wire Liveblocks into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using Liveblocks

Ask Copilot: "Using Liveblocks, help me...". 18 tools available

Why Use VS Code Copilot with the Liveblocks MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Liveblocks through the Model Context Protocol.

01

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

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Liveblocks + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Liveblocks MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Liveblocks in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Liveblocks immediately.

01

"List the first 10 rooms in my Liveblocks project."

02

"Create a new room with ID 'sprint-planning' and set default access to room:write."

03

"Who is currently active in the room 'main-editor'?"

Troubleshooting Liveblocks MCP Server with VS Code Copilot

Common issues when connecting Liveblocks to VS Code Copilot through Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Liveblocks + VS Code Copilot FAQ

Common questions about integrating Liveblocks MCP Server with VS Code Copilot.

01

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.
02

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.
03

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.
04

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.

Explore More MCP Servers

View all →