Vultr Kubernetes (BYOK)

Vultr Kubernetes (BYOK) — connector documentation

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

What Vultr Kubernetes (BYOK) is for

Vultr Kubernetes (BYOK) lets an AI assistant read your own Vultr Kubernetes data through the Vultr Kubernetes API with a key you supply (API key (restrict it to your own address or leave access control open)). Read-only: 9 tools (list_clusters, get_cluster, list_node_pools, get_node_pool, list_worker_nodes, list_node_pool_labels, list_node_pool_taints, list_available_versions, list_available_upgrades). 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.vultr.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vultr Kubernetes. Vultr Kubernetes 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 Kubernetes clusters do I run on Vultr?"
• "What version does my Vultr cluster run?"
• "How many nodes does each pool of my Vultr cluster have?"
• "Is the autoscaler on for my Vultr node pool?"
• "Which worker nodes are in my Vultr node pool?"
• "Which labels does my Vultr node pool apply?"

What it does

• list_clusters: List Vultr Kubernetes Engine clusters with version, region, status, high-availability flag, endpoint and subnets.
• get_cluster: Get one VKE cluster: version, region, status, high-availability flag, endpoint and subnets.
• list_node_pools: List the node pools of a VKE cluster with plan, node count, autoscaler limits, status and tag. User data is not returned.
• get_node_pool: Get one node pool of a VKE cluster: plan, node count, autoscaler limits, status and tag.
• list_worker_nodes: List the worker nodes of a node pool with id, label, IP address, status and creation date.
• list_node_pool_labels: List the Kubernetes labels set on the nodes of a node pool.
• list_node_pool_taints: List the Kubernetes taints (key, value, effect) set on the nodes of a node pool.
• list_available_versions: List the Kubernetes versions Vultr Kubernetes Engine can deploy.
• list_available_upgrades: List the Kubernetes versions a VKE cluster can be upgraded to.

BYOK key

You bring your own Vultr Kubernetes API key (restrict it to your own address or leave access control open) (https://my.vultr.com/settings/#settingsapi). 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.vultr.com 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://www.vultr.com/api/#tag/kubernetes (the API this connector calls, with a BYOK key)

Live from the Vultr Kubernetes API (api.vultr.com) with a BYOK key; documentation: https://www.vultr.com/api/#tag/kubernetes. 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 Vultr Kubernetes. Vultr Kubernetes 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 Vultr Kubernetes account.

Built for: Worldwide. Languages: English.

Vultr Kubernetes (BYOK) — Privacy Policy

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

What Vultr Kubernetes (BYOK) is. Vultr Kubernetes (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Vultr Kubernetes data: Read your Vultr Kubernetes Engine clusters, node pools with autoscaling limits, worker nodes, labels, taints and available versions and upgrades with your own API key. You bring your own Vultr Kubernetes API key (restrict it to your own address or leave access control open); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Vultr Kubernetes 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.vultr.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Vultr Kubernetes 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 Vultr Kubernetes receives. The request we make on your behalf, including the key and the arguments, under Vultr Kubernetes's own terms and privacy policy. Vultr Kubernetes acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Vultr Kubernetes 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 Vultr Kubernetes 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. Vultr Kubernetes (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 Vultr Kubernetes at any time to end all access.

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

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

Vultr Kubernetes (BYOK) — Terms of Service

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

1. The Service. Vultr Kubernetes (BYOK) provides: Read your Vultr Kubernetes Engine clusters, node pools with autoscaling limits, worker nodes, labels, taints and available versions and upgrades with your own 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 Vultr Kubernetes credentials and only access data you are allowed to access. Vultr Kubernetes's terms apply to your use of Vultr Kubernetes; 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 Vultr Kubernetes. Vultr Kubernetes 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 Vultr Kubernetes returns, lightly trimmed; it may be incomplete, delayed or changed by Vultr Kubernetes. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Vultr Kubernetes 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 Vultr Kubernetes'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; Vultr Kubernetes 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 Vultr Kubernetes 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 Vultr Kubernetes 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-vultr-kubernetes

Vultr Kubernetes (BYOK) support

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

• MCP endpoint: https://byok-vultr-kubernetes.connectorbay.com/mcp
• REST API: https://byok-vultr-kubernetes.connectorbay.com/openapi.json
• Live status: https://byok-vultr-kubernetes.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. Vultr Kubernetes (BYOK) never asks for them.