Liveblocks MCP Server

To install, copy your Liveblocks secret key from a project in [your dashboard](https://liveblocks.io/dashboard) and run one of the following

Local serverstdioGo

What is the Liveblocks MCP server?

To install, copy your Liveblocks secret key from a project in your dashboard and run one of the following commands, replacing sk_xxxxxxxxxxxx with your secret key. That is what the liveblocks mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 2 tools. What each one is for:

  • Cursor — 1. Go to File → Cursor Settings → MCP → Add new server. 2. Add the following, inserting your secret key:
  • Codex — 2. Run the following command in the terminal, inserting your secret key:

Getting it running

The server ships on npm as github, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: LIVEBLOCKS_SECRET_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Liveblocks's toolset — Cursor, Codex — is a fair guide to whether it matches your workflow. It is maintained by liveblocks; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Liveblocks's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Cursor1. Go to File → Cursor Settings → MCP → Add new server. 2. Add the following, inserting your secret key:
Codex2. Run the following command in the terminal, inserting your secret key:

How to install the Liveblocks MCP server

{
  "mcpServers": {
    "liveblocks": {
      "command": "npx",
      "args": ["-y", "github:liveblocks/liveblocks-mcp-server"],
      "env": {
        "LIVEBLOCKS_SECRET_KEY": "sk_xxxxxxxxxxxx"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
LIVEBLOCKS_SECRET_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Liveblocks to Cursor.
  • Use Liveblocks to Codex.

Frequently asked questions

It connects Liveblocks to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Cursor, Codex) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Liveblocks directly.