Liveblocks
Liveblocks' official MCP. Manage rooms, threads, comments, and presence for collaborative apps from your agent.
Delv Safety Grade: A
Score 82/100 · assessed 2026-04-28
Liveblocks is a well-established collaboration platform vendor, and this is their official MCP server. The maintainer score reflects a professional mid-size company with a clear product focus, though not quite the scale of major cloud providers. Permissions are moderately scoped: the server can read and write rooms, comments, threads, and presence data within your Liveblocks workspace, plus delete and archive operations. This is broader than read-only but still domain-specific to collaboration features. Supply chain is the weakest link: no npm or PyPI package means manual clone-and-build installation, and the secret key requirement means you're handing over full API access. Transparency is strong with open source code and clear documentation from the vendor. No known security incidents. Suitable for teams already using Liveblocks who need agent-driven workspace management, but the install method and broad write permissions warrant careful key scoping.
Lethal Trifecta (prompt-injection exposure)
TRIFECTA RISKReal-time collaborative state means anyone in the room can plant content the agent reads. Plus auth tokens. Plus outbound.
Green flags
- Official vendor-maintained server from Liveblocks team
- Open source with clear documentation and issue tracker
- Domain-specific to collaboration, not general filesystem or shell access
- Active maintenance from established collaboration platform company
- No known security incidents or CVEs
Red flags
- No package registry distribution, requires manual clone-and-build install
- LIVEBLOCKS_SECRET_KEY grants full API access to entire workspace
- Can delete and archive rooms, potentially destructive operations
- Write access to comments and threads across all rooms
Permissions requested
Review
If you're running Liveblocks in production, this is a no-brainer for auditing, housekeeping, and debugging collaborative state. Everyone else can ignore it. The read-heavy API is a feature, not a bug, but expect to write code if you need mutations beyond deletion.
Good at
- Official vendor support means it tracks Liveblocks API changes without lag.
- Threaded comment inspection is genuinely useful for debugging user-reported issues.
- Bulk operations, like archiving stale rooms, save hours of manual clicking.
- Read-only presence data is perfect for generating activity reports or monitoring dashboards.
Watch out
- Useless unless you're already paying for Liveblocks in production.
- No write operations for rooms or comments, only deletion, so you can't automate content updates.
- Manual config required for hosts beyond Claude Desktop, no pre-packaged install.
- Presence endpoints are read-only, so you can't mock user states for testing scenarios.
Use cases
- Auditing rooms in a collaborative app
- Replaying threaded comments
- Bulk-archiving stale rooms
- Syncing user presence into reports
Getting started
Works with
Similar MCPs
- Lara Translate MCPProfessional translation with language detection, context-aware translations, translation memories, and glossaries.
- Make MCPTurns Make automation scenarios into callable tools for AI assistants, bridging 1,000+ apps through Make workflows.
- CCXT MCPCrypto exchange integration using CCXT, covering spot, futures, OHLCV, balances, and orders across 20+ exchanges.
- HubSpotHubSpot's MCP for CRM workflows: contacts, deals, tickets, properties. Distributed via NPM, see the developer docs for install steps.