Liveblocks MCP Server vs Hub MCP

In-depth architectural comparison of the Liveblocks MCP Server and Hub MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Liveblocks MCP Server when:

• You need dedicated capabilities in the Cloud Platforms domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: LIVEBLOCKS_SECRET_KEY.
• Primary tools included: Full CRUD operations on rooms, threads, comments, notifications, Read access to Storage and Yjs, Integration with Liveblocks REST API.

Explore Liveblocks MCP Server Details

Choose Hub MCP when:

• You need dedicated capabilities in the Cloud Platforms domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• You have access to required keys: HUB_PAT_TOKEN, MCP_AUTH_TOKEN.

Feature & Specification Comparison

Specification	Liveblocks MCP Server liveblocks Cloud Platforms	Hub MCP docker VerifiedCloud Platforms
Summary	Create, modify, and delete different aspects of Liveblocks such as rooms, threads, comments, notifications, and more. Additionally, it has read access to Storage and Yjs.	Official MCP server to interact with Docker Hub, providing access to repositories, hub search and Docker Hardened Images
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

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

{
  "mcpServers": {
    "docker-hub-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ],
      "env": {
        "HUB_PAT_TOKEN": "YOUR_HUB_PAT_TOKEN_HERE",
        "MCP_AUTH_TOKEN": "YOUR_MCP_AUTH_TOKEN_HERE"
      }
    }
  }
}

Related MCP Server Comparisons