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

Confluent Cloud Admin (BYOK)

Read your Confluent Cloud daily costs, service quotas, role bindings, API key metadata, identity providers and pools, SSO group mappings and IP filters with your own Cloud API key

Unify Dynamics LLC

Tools10read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderConfluent Cloud Adminunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

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

How much did Confluent Cloud cost us between 2026-10-01 and 2026-10-15?
Tools called
list_costs
How close is my Confluent Cloud environment env-abc123 to its quotas?
Tools called
list_applied_quotas
Which quota scopes does Confluent Cloud have?
Tools called
list_quota_scopes
Who has the CloudClusterAdmin role in my Confluent Cloud organization?
Tools called
list_role_bindings
Which API keys exist for Confluent Cloud cluster lkc-abc12?
Tools called
list_api_keys
Which identity providers does Confluent Cloud trust?
Tools called
list_identity_providers

About

Confluent Cloud Admin (BYOK) lets an AI assistant read your own Confluent Cloud Admin data through the Confluent Cloud Admin API with a key you supply (Cloud API key ID). Read-only: 10 tools (list_costs, list_applied_quotas, list_quota_scopes, list_role_bindings, list_api_keys, list_identity_providers, list_identity_pools, list_sso_group_mappings, list_ip_groups, list_ip_filters). 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 Admin. Confluent Cloud Admin 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 Admin 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.

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

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

OpenAPI
Read your data10 tools
  • List costsList Confluent Cloud billing line items between two dates with product, line type, unit, quantity, price, discount, amount and the resource…
  • List applied quotasList applied service quotas for one scope (organization, environment, network, Kafka cluster or user) with default limit, applied limit and…
  • List quota scopesList the scopes service quotas can be applied to, with descriptions.
  • List role bindingsList RBAC role bindings that match a CRN pattern, optionally for one principal or role, with principal, role name and resource pattern.
  • List api keysList API keys of the organization with name, description, owner and the resource they are scoped to.
  • List identity providersList OAuth identity providers with name, description, identity claim, issuer, state and JWKS URI.
  • List identity poolsList the identity pools of one identity provider with name, claim, filter, mapped principal and state.
  • List sso group mappingsList SSO group mappings (identity provider groups mapped to Confluent principals) with name, filter, principal and state.
  • List ip groupsList IP groups (named sets of CIDR blocks used by IP filters).
  • List ip filtersList IP filters (which IP groups may use which operation groups on a resource scope) with name, resource group, scope and linked IP groups.

Information

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

Connect it to your agent

Three ways in, the same 10 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-confluent-cloud-admin.connectorbay.com/mcp
RESTPOST https://byok-confluent-cloud-admin.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-confluent-cloud-admin.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 Cloud API key ID in the X-Upstream-Key header (get one at confluent.cloud).
  • Ask a question; the agent picks the right tool and answers from the live data.

Confluent Cloud Admin connector: questions and answers

What is the Confluent Cloud Admin connector?

Confluent Cloud Admin (BYOK) lets an AI assistant read your own Confluent Cloud Admin data through the Confluent Cloud Admin API with a key you… It is a hosted MCP server with 10 tools such as List costs, List applied quotas, List quota scopes, List role bindings, List api keys, List identity providers, published by Unify Dynamics LLC. It is independent and not affiliated with Confluent Cloud Admin.

How do I connect Confluent Cloud Admin to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-confluent-cloud-admin.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-admin.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-confluent-cloud-admin.json.

Do I need a Confluent Cloud Admin account or API key?

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.

Is Confluent Cloud Admin read-only?

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

Is the Confluent Cloud Admin 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

Livepeer (BYOK)

Read your Livepeer Studio live streams, video assets, sessions, viewership and usage metrics with your own API key

Live · MCP + REST11 tools

Llama Cloud (BYOK)

Read your Llama Cloud projects, indexes, files, parse, extract and classify jobs and credit usage (North America region) with your own API key

Live · MCP + REST11 tools

Lob (BYOK)

Read your Lob print-and-mail postcards, letters, checks, self mailers, templates and campaigns with your own API key

Live · MCP + REST9 tools

Locize (BYOK)

Read your Locize localization project languages, versions, branches, tags, tenants and translation progress with your own project API key

Live · MCP + REST7 tools

Logz.io (BYOK)

Read your Logz.io account info, alerts, notification endpoints, users, log types and search your logs with your own API token (US, EU, AU, CA and UK regions)

Live · MCP + REST7 tools

Losant (BYOK)

Read your Losant IoT applications, devices, last device state, connection logs, events, workflows, data tables and time-series data with your own API access token

Live · MCP + REST12 tools

Documentation

Back to top

Confluent Cloud Admin (BYOK) — connector documentation

  • MCP endpoint: https://byok-confluent-cloud-admin.connectorbay.com/mcp
  • REST API: POST https://byok-confluent-cloud-admin.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-confluent-cloud-admin.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Confluent Cloud Admin 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-admin.connectorbay.com/health · Tool schemas: https://byok-confluent-cloud-admin.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-confluent-cloud-admin · agent@connectorbay.com

What Confluent Cloud Admin (BYOK) is for

Confluent Cloud Admin (BYOK) lets an AI assistant read your own Confluent Cloud Admin data through the Confluent Cloud Admin API with a key you supply (Cloud API key ID). Read-only: 10 tools (list_costs, list_applied_quotas, list_quota_scopes, list_role_bindings, list_api_keys, list_identity_providers, list_identity_pools, list_sso_group_mappings, list_ip_groups, list_ip_filters). 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 Admin. Confluent Cloud Admin 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:

  • "How much did Confluent Cloud cost us between 2026-10-01 and 2026-10-15?"
  • "How close is my Confluent Cloud environment env-abc123 to its quotas?"
  • "Which quota scopes does Confluent Cloud have?"
  • "Who has the CloudClusterAdmin role in my Confluent Cloud organization?"
  • "Which API keys exist for Confluent Cloud cluster lkc-abc12?"
  • "Which identity providers does Confluent Cloud trust?"

What it does

  • list_costs: List Confluent Cloud billing line items between two dates with product, line type, unit, quantity, price, discount, amount and the resource (cluster, environment) each belongs to.
  • list_applied_quotas: List applied service quotas for one scope (organization, environment, network, Kafka cluster or user) with default limit, applied limit and current usage.
  • list_quota_scopes: List the scopes service quotas can be applied to, with descriptions.
  • list_role_bindings: List RBAC role bindings that match a CRN pattern, optionally for one principal or role, with principal, role name and resource pattern.
  • list_api_keys: List API keys of the organization with name, description, owner and the resource they are scoped to. Key secrets are never returned.
  • list_identity_providers: List OAuth identity providers with name, description, identity claim, issuer, state and JWKS URI. Signing keys are not requested.
  • list_identity_pools: List the identity pools of one identity provider with name, claim, filter, mapped principal and state.
  • list_sso_group_mappings: List SSO group mappings (identity provider groups mapped to Confluent principals) with name, filter, principal and state.
  • list_ip_groups: List IP groups (named sets of CIDR blocks used by IP filters).
  • list_ip_filters: List IP filters (which IP groups may use which operation groups on a resource scope) with name, resource group, scope and linked IP groups.

BYOK key

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

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

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Confluent Cloud Admin (BYOK) — Privacy Policy

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

What Confluent Cloud Admin (BYOK) is. Confluent Cloud Admin (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Confluent Cloud Admin data: Read your Confluent Cloud daily costs, service quotas, role bindings, API key metadata, identity providers and pools, SSO group mappings and IP filters with your own Cloud API key. You bring your own Confluent Cloud Admin 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 Admin 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 Admin 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 Admin receives. The request we make on your behalf, including the key and the arguments, under Confluent Cloud Admin's own terms and privacy policy. Confluent Cloud Admin 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 Admin 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 Admin 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 Admin (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 Admin at any time to end all access.

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

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

Terms of service

Back to top

Confluent Cloud Admin (BYOK) — Terms of Service

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

  1. The Service. Confluent Cloud Admin (BYOK) provides: Read your Confluent Cloud daily costs, service quotas, role bindings, API key metadata, identity providers and pools, SSO group mappings and IP filters 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 Admin credentials and only access data you are allowed to access. Confluent Cloud Admin's terms apply to your use of Confluent Cloud Admin; 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 Admin. Confluent Cloud Admin 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 Admin returns, lightly trimmed; it may be incomplete, delayed or changed by Confluent Cloud Admin. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Confluent Cloud Admin 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 Admin'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 Admin 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 Admin 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 Admin 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-admin

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

Get Confluent Cloud Admin (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Confluent Cloud Admin Cloud API key ID. Create one at https://confluent.cloud/settings/api-keys, 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 Confluent Cloud Admin. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Confluent Cloud Admin.