Confluent Cloud Networking (BYOK)

Confluent Cloud Networking (BYOK) — connector documentation

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

What Confluent Cloud Networking (BYOK) is for

Confluent Cloud Networking (BYOK) lets an AI assistant read your own Confluent Cloud Networking data through the Confluent Cloud Networking API with a key you supply (Cloud API key ID). Read-only: 9 tools (list_networks, get_network, list_peerings, list_transit_gateway_attachments, list_private_link_accesses, list_private_link_attachments, list_private_link_attachment_connections, list_gateways, list_ip_addresses). 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 Networking. Confluent Cloud Networking 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 Confluent Cloud networks exist in environment env-abc123?"
• "Show details of Confluent Cloud network n-abc123"
• "Which peerings does Confluent Cloud environment env-abc123 have?"
• "Which transit gateway attachments are in Confluent Cloud environment env-abc123?"
• "Which private link accesses are set up in Confluent Cloud environment env-abc123?"
• "Which private link attachments exist in Confluent Cloud environment env-abc123?"

What it does

• list_networks: List the dedicated networks of one environment with cloud, region, CIDR, connection types, zones, phase and DNS domain.
• get_network: Get one dedicated network by id: cloud, region, CIDR, connection types, zones, phase, DNS domain and any error.
• list_peerings: List VPC or VNet peerings of one environment with name, network, phase and any error.
• list_transit_gateway_attachments: List AWS transit gateway attachments of one environment with name, network, phase and any error.
• list_private_link_accesses: List private link accesses (cloud accounts allowed to reach a network by private link) of one environment with name, network, phase and any error.
• list_private_link_attachments: List private link attachments of one environment with name, cloud, region, phase and DNS domain.
• list_private_link_attachment_connections: List the connections made to private link attachments of one environment, optionally for one attachment, with name, attachment, phase and any error.
• list_gateways: List network gateways of one environment with name, cloud config kind, region and phase.
• list_ip_addresses: List the public IP address ranges Confluent Cloud uses, filterable by cloud, region, service and address type (useful for firewall allow lists).

BYOK key

You bring your own Confluent Cloud Networking 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.

Data sources

• https://docs.confluent.io/cloud/current/api.html (the API this connector calls, with a BYOK key)

Live from the Confluent Cloud Networking 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.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Confluent Cloud Networking. Confluent Cloud Networking 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 Networking account.

Built for: Worldwide. Languages: English.

Confluent Cloud Networking (BYOK) — Privacy Policy

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

What Confluent Cloud Networking (BYOK) is. Confluent Cloud Networking (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Confluent Cloud Networking data: Read your Confluent Cloud networks, peerings, transit gateway attachments, private link access and attachments, gateways and public IP ranges with your own Cloud API key. You bring your own Confluent Cloud Networking 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 Networking 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 Networking 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 Networking receives. The request we make on your behalf, including the key and the arguments, under Confluent Cloud Networking's own terms and privacy policy. Confluent Cloud Networking 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 Networking 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 Networking 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 Networking (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 Networking at any time to end all access.

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

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

Confluent Cloud Networking (BYOK) — Terms of Service

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

1. The Service. Confluent Cloud Networking (BYOK) provides: Read your Confluent Cloud networks, peerings, transit gateway attachments, private link access and attachments, gateways and public IP ranges with your own Cloud API 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 Confluent Cloud Networking credentials and only access data you are allowed to access. Confluent Cloud Networking's terms apply to your use of Confluent Cloud Networking; 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 Confluent Cloud Networking. Confluent Cloud Networking 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 Confluent Cloud Networking returns, lightly trimmed; it may be incomplete, delayed or changed by Confluent Cloud Networking. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Confluent Cloud Networking 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 Confluent Cloud Networking'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; Confluent Cloud Networking 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 Confluent Cloud Networking 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 Confluent Cloud Networking 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-confluent-cloud-networking

Confluent Cloud Networking (BYOK) support

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

• MCP endpoint: https://byok-confluent-cloud-networking.connectorbay.com/mcp
• REST API: https://byok-confluent-cloud-networking.connectorbay.com/openapi.json
• Live status: https://byok-confluent-cloud-networking.connectorbay.com/health

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. Confluent Cloud Networking (BYOK) never asks for them.