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
Read your Liveblocks rooms, active users, version history, threads, groups and AI copilots with your own project secret key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_roomsget_roomlist_active_userslist_versionslist_threadslist_groupsLiveblocks (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.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
8 tools, grouped by job. Every one is read-only or compute-only.
https://byok-liveblocks.connectorbay.com/mcpThree ways in, the same 8 tools.
https://byok-liveblocks.connectorbay.com/mcpPOST https://byok-liveblocks.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-liveblocks.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at liveblocks.io).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.
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.
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.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
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
Read your Cloudflare IP Access rules, Zone Lockdown rules, User Agent blocking rules and legacy firewall rules with your own API token
Read your Cloudflare account load balancers, origin pools, health monitors and pool health with your own API token
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)
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
Read the scripts, connections and cookies Cloudflare Page Shield detected on your zone, plus its content security rules, with your own API token
https://byok-liveblocks.connectorbay.com/mcpPOST https://byok-liveblocks.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-liveblocks.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-liveblocks.connectorbay.com/health · Tool schemas: https://byok-liveblocks.connectorbay.com/tools.jsonLiveblocks (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:
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).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.
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.
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.
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.
Effective 24 October 2026. These terms govern use of the Liveblocks (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-liveblocks.connectorbay.com/mcphttps://byok-liveblocks.connectorbay.com/openapi.jsonWhen 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.