Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Liveblocks (BYOK) icon

Liveblocks (BYOK)

Read your Liveblocks rooms, active users, version history, threads, groups and AI copilots with your own project secret key

Unify Dynamics LLC

Tools8read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderLiveblocksunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Liveblocks rooms were used most recently?
Tools called
list_rooms
Show details of Liveblocks room my-room-id
Tools called
get_room
Who is in Liveblocks room my-room-id right now?
Tools called
list_active_users
What versions does Liveblocks room my-room-id have?
Tools called
list_versions
Which comment threads are unresolved in Liveblocks room my-room-id?
Tools called
list_threads
Which Liveblocks groups exist?
Tools called
list_groups

About

Liveblocks (BYOK) lets an AI assistant read your own Liveblocks data through the Liveblocks API with a key you supply (project secret key (sk_...)). Read-only: 8 tools (list_rooms, get_room, list_active_users, list_versions, list_threads, list_groups, get_group, list_ai_copilots). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.liveblocks.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Liveblocks. Liveblocks and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Liveblocks API (api.liveblocks.io) with a BYOK key; documentation: https://liveblocks.io/docs/api-reference/rest-api-endpoints. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

8 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data8 tools
  • List roomsList rooms newest first with creation time, last connection time, default access, metadata and organization, optionally filtered by ID prefix or…
  • Get roomGet one room's creation time, last connection time, default accesses and metadata.
  • List active usersList users currently present in a room (connection ID, user ID and user info).
  • List versionsList the version history snapshots of a room (ID, time, authors), newest first.
  • List threadsList comment threads of a room with resolved flag, visibility, timestamps and metadata (comment text is not returned).
  • List groupsList user groups of the project with organization, scopes and members.
  • Get groupGet one group with its members and scopes.
  • List ai copilotsList AI copilots with name, description, provider, model and last use (system prompts are not returned).

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-liveblocks.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 8 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-liveblocks.connectorbay.com/mcp
RESTPOST https://byok-liveblocks.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-liveblocks.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your project secret key (sk_...) in the X-Upstream-Key header (get one at liveblocks.io).
  • Ask a question; the agent picks the right tool and answers from the live data.

Liveblocks connector: questions and answers

What is the Liveblocks connector?

Liveblocks (BYOK) lets an AI assistant read your own Liveblocks data through the Liveblocks API with a key you supply (project secret key (sk_...)). It is a hosted MCP server with 8 tools such as List rooms, Get room, List active users, List versions, List threads, List groups, published by Unify Dynamics LLC. It is independent and not affiliated with Liveblocks.

How do I connect Liveblocks to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-liveblocks.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-liveblocks.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-liveblocks.json.

Do I need a Liveblocks account or API key?

Yes: this is a bring-your-own-key connector. Create a project secret key (sk_...) at https://liveblocks.io/dashboard/apikeys and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Liveblocks read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Liveblocks connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Cloudflare IP Addressing (BYOK)

Read your Cloudflare BYOIP prefixes with advertisement and validation status, BGP prefixes, service bindings, delegations, address maps and regional hostnames with your own API token

Live · MCP + REST11 tools

Cloudflare IP Firewall (BYOK)

Read your Cloudflare IP Access rules, Zone Lockdown rules, User Agent blocking rules and legacy firewall rules with your own API token

Live · MCP + REST9 tools

Cloudflare Load Balancing (BYOK)

Read your Cloudflare account load balancers, origin pools, health monitors and pool health with your own API token

Live · MCP + REST9 tools

Cloudflare Logpush (BYOK)

Read your Cloudflare Logpush jobs, their health and dataset assignments and log transformers with your own API token (destinations and log contents are left out)

Live · MCP + REST10 tools

Cloudflare Magic Transit (BYOK)

Read your Cloudflare Magic WAN and Magic Transit sites, GRE and IPsec tunnels, interconnects, static routes, connectors and BGP settings with your own API token

Live · MCP + REST9 tools

Cloudflare Page Shield (BYOK)

Read the scripts, connections and cookies Cloudflare Page Shield detected on your zone, plus its content security rules, with your own API token

Live · MCP + REST8 tools

Documentation

Back to top

Liveblocks (BYOK) — connector documentation

  • MCP endpoint: https://byok-liveblocks.connectorbay.com/mcp
  • REST API: POST https://byok-liveblocks.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-liveblocks.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Liveblocks project secret key (sk_...), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-liveblocks.connectorbay.com/health · Tool schemas: https://byok-liveblocks.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-liveblocks · agent@connectorbay.com

What Liveblocks (BYOK) is for

Liveblocks (BYOK) lets an AI assistant read your own Liveblocks data through the Liveblocks API with a key you supply (project secret key (sk_...)). Read-only: 8 tools (list_rooms, get_room, list_active_users, list_versions, list_threads, list_groups, get_group, list_ai_copilots). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.liveblocks.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Liveblocks. Liveblocks and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Liveblocks rooms were used most recently?"
  • "Show details of Liveblocks room my-room-id"
  • "Who is in Liveblocks room my-room-id right now?"
  • "What versions does Liveblocks room my-room-id have?"
  • "Which comment threads are unresolved in Liveblocks room my-room-id?"
  • "Which Liveblocks groups exist?"

What it does

  • list_rooms: List rooms newest first with creation time, last connection time, default access, metadata and organization, optionally filtered by ID prefix or metadata query.
  • get_room: Get one room's creation time, last connection time, default accesses and metadata.
  • list_active_users: List users currently present in a room (connection ID, user ID and user info).
  • list_versions: List the version history snapshots of a room (ID, time, authors), newest first.
  • list_threads: List comment threads of a room with resolved flag, visibility, timestamps and metadata (comment text is not returned).
  • list_groups: List user groups of the project with organization, scopes and members.
  • get_group: Get one group with its members and scopes.
  • list_ai_copilots: List AI copilots with name, description, provider, model and last use (system prompts are not returned).

BYOK key

You bring your own Liveblocks project secret key (sk_...) (https://liveblocks.io/dashboard/apikeys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.liveblocks.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Liveblocks API (api.liveblocks.io) with a BYOK key; documentation: https://liveblocks.io/docs/api-reference/rest-api-endpoints. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Liveblocks. Liveblocks and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Liveblocks account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Liveblocks (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Liveblocks (BYOK) is. Liveblocks (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Liveblocks data: Read your Liveblocks rooms, active users, version history, threads, groups and AI copilots with your own project secret key. You bring your own Liveblocks project secret key (sk_...); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Liveblocks call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.liveblocks.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Liveblocks rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Liveblocks receives. The request we make on your behalf, including the key and the arguments, under Liveblocks's own terms and privacy policy. Liveblocks acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Liveblocks gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Liveblocks data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Liveblocks (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Liveblocks at any time to end all access.

Children. Liveblocks (BYOK) is a general-audience service operated by the adult using the assistant, under Liveblocks's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Liveblocks (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Liveblocks (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Liveblocks (BYOK) provides: Read your Liveblocks rooms, active users, version history, threads, groups and AI copilots with your own project secret key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Liveblocks credentials and only access data you are allowed to access. Liveblocks's terms apply to your use of Liveblocks; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Liveblocks. Liveblocks and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Liveblocks returns, lightly trimmed; it may be incomplete, delayed or changed by Liveblocks. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Liveblocks account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Liveblocks's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Liveblocks may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Liveblocks key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Liveblocks takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-liveblocks

Liveblocks (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Liveblocks (BYOK) never asks for them.

Get Liveblocks (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Liveblocks project secret key (sk_...). Create one at https://liveblocks.io/dashboard/apikeys, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Liveblocks. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Liveblocks.