Kontent.ai Management (BYOK)
Read the content model, content items, assets, languages, taxonomies, collections, workflows and spaces of your Kontent.ai environment with your own management API key
Read your Confluent Cloud managed connectors, connector status and tasks, plugins and custom connector plugins with your own Cloud API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_connectorsget_connector_statusget_connectorlist_connector_pluginslist_custom_connector_pluginslist_custom_connector_runtimesConfluent Cloud Connect (BYOK) lets an AI assistant read your own Confluent Cloud Connect data through the Confluent Cloud Connect API with a key you supply (Cloud API key ID). Read-only: 8 tools (list_connectors, get_connector_status, get_connector, list_connector_plugins, list_custom_connector_plugins, list_custom_connector_runtimes, list_custom_connect_plugins, list_custom_connect_plugin_versions). 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.confluent.cloud. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Confluent Cloud Connect. Confluent Cloud Connect and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Confluent Cloud Connect API (api.confluent.cloud) with a BYOK key; documentation: https://docs.confluent.io/cloud/current/api.html. 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-confluent-cloud-connect.connectorbay.com/mcpThree ways in, the same 8 tools.
https://byok-confluent-cloud-connect.connectorbay.com/mcpPOST https://byok-confluent-cloud-connect.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-confluent-cloud-connect.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at confluent.cloud).Confluent Cloud Connect (BYOK) lets an AI assistant read your own Confluent Cloud Connect data through the Confluent Cloud Connect API with a key… It is a hosted MCP server with 8 tools such as List connectors, Get connector status, Get connector, List connector plugins, List custom connector plugins, List custom connector runtimes, published by Unify Dynamics LLC. It is independent and not affiliated with Confluent Cloud Connect.
Add the MCP endpoint https://byok-confluent-cloud-connect.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-confluent-cloud-connect.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-confluent-cloud-connect.json.
Yes: this is a bring-your-own-key connector. Create a Cloud API key ID at https://confluent.cloud/settings/api-keys 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 the content model, content items, assets, languages, taxonomies, collections, workflows and spaces of your Kontent.ai environment with your own management API key
Read your Koyeb apps, services, deployments, instances, domains and volumes with BYOK
Read your Lambda GPU cloud instances, available instance types and prices, regions, images, filesystems and firewall rulesets with BYOK
Read your LambdaTest (TestMu AI) Selenium test builds, sessions, tunnels, uploaded files and concurrency with your own username and access key
Read your Laminar AI observability project: datasets and datapoints, signals, LLM profiles and read-only SQL over traces and spans, with your own project API key
Read your Langdock workspace: agents, available models, skills, prompt folders, knowledge bases and workflows with your own API key (no prompts or instructions)
https://byok-confluent-cloud-connect.connectorbay.com/mcpPOST https://byok-confluent-cloud-connect.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-confluent-cloud-connect.connectorbay.com/openapi.jsonX-Upstream-Key header and the Cloud API key secret in X-Upstream-Key-2 of every request (never stored, logged or cached)https://byok-confluent-cloud-connect.connectorbay.com/health · Tool schemas: https://byok-confluent-cloud-connect.connectorbay.com/tools.jsonConfluent Cloud Connect (BYOK) lets an AI assistant read your own Confluent Cloud Connect data through the Confluent Cloud Connect API with a key you supply (Cloud API key ID). Read-only: 8 tools (list_connectors, get_connector_status, get_connector, list_connector_plugins, list_custom_connector_plugins, list_custom_connector_runtimes, list_custom_connect_plugins, list_custom_connect_plugin_versions). 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.confluent.cloud. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Confluent Cloud Connect. Confluent Cloud Connect 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_connectors: List the names of the managed connectors of one Kafka cluster.get_connector_status: Get the state of one managed connector and its tasks: connector state, worker, error trace, and per-task state and message.get_connector: Get one managed connector's name, type and task list. The connector configuration is not returned.list_connector_plugins: List the managed connector plugins (connector classes, type and version) available on one Kafka cluster.list_custom_connector_plugins: List custom connector plugins (uploaded by your organization) with name, connector class, type, cloud and runtime language.list_custom_connector_runtimes: List the runtimes custom connectors can run on with Kafka Connect version, supported Java versions, maturity and end-of-life date.list_custom_connect_plugins: List custom Connect plugins of one environment (plugin management API) with name, cloud, runtime language and description.list_custom_connect_plugin_versions: List the versions of one custom Connect plugin with version, connector classes, phase and any error.You bring your own Confluent Cloud Connect Cloud API key ID (https://confluent.cloud/settings/api-keys). 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.confluent.cloud 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 Confluent Cloud Connect API (api.confluent.cloud) with a BYOK key; documentation: https://docs.confluent.io/cloud/current/api.html. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Confluent Cloud Connect. Confluent Cloud Connect 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 Confluent Cloud Connect account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Confluent Cloud Connect (BYOK) is. Confluent Cloud Connect (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Confluent Cloud Connect data: Read your Confluent Cloud managed connectors, connector status and tasks, plugins and custom connector plugins with your own Cloud API key. You bring your own Confluent Cloud Connect Cloud API key ID; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Confluent Cloud Connect 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.confluent.cloud, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Confluent Cloud Connect 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 Confluent Cloud Connect receives. The request we make on your behalf, including the key and the arguments, under Confluent Cloud Connect's own terms and privacy policy. Confluent Cloud Connect acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Confluent Cloud Connect 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 Confluent Cloud Connect 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. Confluent Cloud Connect (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 Confluent Cloud Connect at any time to end all access.
Children. Confluent Cloud Connect (BYOK) is a general-audience service operated by the adult using the assistant, under Confluent Cloud Connect'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 Confluent Cloud Connect (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-confluent-cloud-connect.connectorbay.com/mcphttps://byok-confluent-cloud-connect.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. Confluent Cloud Connect (BYOK) never asks for them.