4,000+ servers built on vurb.ts
Vinkius

Liveblocks MCP Server for CursorGive Cursor instant access to 18 tools to Authorize User, Broadcast Event, Create Room, and more

MCP Inspector GDPR Free for Subscribers

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Ask AI about this MCP Server for Cursor

The Liveblocks MCP Server for Cursor 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.

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.

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 Cursor 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 Cursor

When Cursor 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 Cursor via MCP

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

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens
03

Save the file

Cursor will automatically detect the new MCP server
04

Start using Liveblocks

Open Agent mode in chat and ask: "Using Liveblocks, help me...". 18 tools available

Why Use Cursor with the Liveblocks MCP Server

Cursor AI Code Editor provides unique advantages when paired with Liveblocks through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Liveblocks + Cursor Use Cases

Practical scenarios where Cursor combined with the Liveblocks MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Example Prompts for Liveblocks in Cursor

Ready-to-use prompts you can give your Cursor 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 Cursor

Common issues when connecting Liveblocks to Cursor through Vinkius, and how to resolve them.

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Liveblocks + Cursor FAQ

Common questions about integrating Liveblocks MCP Server with Cursor.

01

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

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

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

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.

Explore More MCP Servers

View all →