Can AI agents automate Liveblocks?

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.

Best path today: api · Overall automatability: 8/10