Liveblocks Mcp Server

Created By
liveblocksa year ago
MCP server for Liveblocks.
Overview

what is Liveblocks MCP Server?

Liveblocks MCP Server is a server that allows AI to interact with various functions from the Liveblocks API, enabling the creation, modification, and deletion of elements such as rooms, threads, comments, and notifications.

how to use Liveblocks MCP Server?

To use the Liveblocks MCP Server, clone the repository, build the project, and configure it with your Liveblocks secret key. Detailed steps are provided in the documentation.

key features of Liveblocks MCP Server?

  • Integration with Liveblocks API for real-time collaboration.
  • Ability to create, modify, and delete rooms and threads.
  • Read access to Storage and Yjs.

use cases of Liveblocks MCP Server?

  1. Building collaborative applications that require real-time data synchronization.
  2. Managing user interactions in a multi-user environment.
  3. Facilitating notifications and comments in applications.

FAQ from Liveblocks MCP Server?

  • What is required to set up the Liveblocks MCP Server?

You need to clone the repository, build the project, and obtain a Liveblocks secret key.

  • Can I use this server for any type of application?

Yes, it is designed for applications that require real-time collaboration features.

  • Is there an automatic setup option?

An automatic setup is coming soon with Smithery.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
liveblocks
Star
1
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago