{
 "categories": [
  "collaboration",
  "developer-tools"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-10-13",
   "fact": "homepage",
   "note": "The Liveblocks homepage describes Sync, Comments, Notifications, and realtime infrastructure.",
   "source": "https://liveblocks.io/",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "deployment",
   "note": "The REST API is hosted at https://api.liveblocks.io/v2.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "platforms",
   "note": "The secret key is copied from the Liveblocks dashboard at https://liveblocks.io/dashboard/apikeys.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "license",
   "note": "The homepage presents Liveblocks as a vendor infrastructure product. A free-plan page was not opened, so the license is recorded as commercial.",
   "source": "https://liveblocks.io/",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "modalities.api.exists",
   "note": "Liveblocks documents a REST API for rooms, users, permissions, schemas, and other account resources.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "modalities.api.kinds[0]",
   "note": "The reference says the API is REST, with resource-oriented URLs, and shows HTTPS calls to https://api.liveblocks.io/v2.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "modalities.api.auth[0]",
   "note": "Requests send the project secret key as Authorization Bearer. The public authorization endpoint is the stated exception.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "modalities.api.coverage",
   "note": "The reference covers rooms and account administration. Realtime client connections use a separate access-token flow, so this record's API coverage is partial.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "modalities.api.docs",
   "note": "Opened as the current REST API reference, including the OpenAPI description.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "modalities.sdk.exists",
   "note": "The access-token section says the @liveblocks/node package can prepare the session request.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "modalities.sdk.languages",
   "note": "The named package is @liveblocks/node, a JavaScript server SDK. Other languages were not opened.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "modalities.sdk.official",
   "note": "Liveblocks documents @liveblocks/node in its own REST reference.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "modalities.mcp.first_party",
   "note": "Liveblocks documents its MCP server and says it has 39 tools over the REST API.",
   "source": "https://liveblocks.io/docs/tools/mcp-server",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "modalities.mcp.verdict",
   "note": "The MCP page is Liveblocks documentation, so the verdict is official.",
   "source": "https://liveblocks.io/docs/tools/mcp-server",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "modalities.data_access.export[0]",
   "note": "The reference says the API returns JSON-encoded responses.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "verdict.scores.api",
   "note": "Documented REST API at api.liveblocks.io/v2 with a secret key and an OpenAPI description. Realtime access uses a separate token flow. Score 8.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "verdict.scores.mcp",
   "note": "Official local MCP server with 39 tools over the REST API. The docs say not to use a production secret. Score 7.",
   "source": "https://liveblocks.io/docs/tools/mcp-server",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "freshness.watch[0].url",
   "note": "Opened as the current Liveblocks REST API reference.",
   "source": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "freshness.watch[1].url",
   "note": "Opened as the current Liveblocks MCP server page.",
   "source": "https://liveblocks.io/docs/tools/mcp-server",
   "tier": "declared"
  },
  {
   "date": "2026-10-13",
   "fact": "freshness.watch[2].url",
   "note": "Opened as the current Liveblocks homepage.",
   "source": "https://liveblocks.io/",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-10-13",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://liveblocks.io/docs/api-reference/rest-api-endpoints"
   },
   {
    "type": "mcp",
    "url": "https://liveblocks.io/docs/tools/mcp-server"
   },
   {
    "type": "docs",
    "url": "https://liveblocks.io/"
   }
  ]
 },
 "homepage": "https://liveblocks.io/",
 "id": "liveblocks",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": "unknown"
  },
  "api": {
   "auth": [
    "secret-key"
   ],
   "coverage": "partial",
   "docs": "https://liveblocks.io/docs/api-reference/rest-api-endpoints",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "json"
   ],
   "import": []
  },
  "extensibility": {
   "scripting": [],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": true,
   "third_party": [],
   "verdict": "official"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. Liveblocks documents a REST API and a first-party MCP server over that API.\n",
   "ui_stack": [],
   "vendor_support": []
  },
  "sdk": {
   "exists": true,
   "languages": [
    "javascript"
   ],
   "official": true
  }
 },
 "name": "Liveblocks",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "notion",
   "coda"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Liveblocks",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 8,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": 7,
   "overall": 8,
   "rpa": null
  },
  "summary": "Liveblocks is automatable today through its REST API. This record is the Liveblocks realtime infrastructure for rooms, comments, and notifications, not an end-user document product. The homepage describes Sync, Comments, and Notifications as realtime infrastructure. The REST reference says the API is https://api.liveblocks.io/v2. Requests send the project secret key as Authorization Bearer, except the public authorization endpoint. Responses are JSON. The reference includes an OpenAPI description and covers rooms and other account resources, including rolling a project secret key. The same page names the official @liveblocks/node package for preparing room access tokens. The MCP docs say the official server has 39 tools over the REST API, including rooms, threads, comments, notifications, storage and Yjs reads, and broadcast events. Setup runs npx github:liveblocks/liveblocks-mcp-server with LIVEBLOCKS_SECRET_KEY. The page says not to use a production secret key, because the agent can modify that project. Connector catalogs were not opened. A full SDK language list was not opened beyond the Node package named on the REST page. Computer-use viability is unassessed. API scores 8. MCP scores 7. API is the best path because the secret key calls the REST API directly, while the MCP server is a local process and the docs warn against a production secret.\n"
 }
}