Linode Kubernetes (BYOK)

Linode Kubernetes (BYOK) — connector documentation

• MCP endpoint: https://byok-linode-lke.connectorbay.com/mcp
• REST API: POST https://byok-linode-lke.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-linode-lke.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Linode Kubernetes personal access token (read-only scopes are enough), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-linode-lke.connectorbay.com/health · Tool schemas: https://byok-linode-lke.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-linode-lke · agent@connectorbay.com

What Linode Kubernetes (BYOK) is for

Linode Kubernetes (BYOK) lets an AI assistant read your own Linode Kubernetes data through the Linode Kubernetes API with a key you supply (personal access token (read-only scopes are enough)). Read-only: 9 tools (list_clusters, get_cluster, list_node_pools, get_node_pool, list_api_endpoints, get_control_plane_acl, list_kubernetes_versions, list_tier_versions, list_lke_pricing). 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.linode.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Linode Kubernetes. Linode 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 Linode and what version are they?"
• "Is LKE cluster 1234 high availability and what version does it run?"
• "How many nodes and which plan does each pool of cluster 1234 use?"
• "What are the nodes in pool 55 of cluster 1234?"
• "What is the API endpoint of LKE cluster 1234?"
• "Which IP ranges may reach the control plane of cluster 1234?"

What it does

• list_clusters: List LKE Kubernetes clusters with region, status, tier, Kubernetes version, high-availability flag and tags.
• get_cluster: Get one LKE cluster with region, status, tier, Kubernetes version, control plane settings and VPC.
• list_node_pools: List the node pools of an LKE cluster with plan type, node count, autoscaler limits, Kubernetes version and node status.
• get_node_pool: Get one node pool of an LKE cluster with its nodes, plan type, autoscaler, disks, labels and taints.
• list_api_endpoints: List the Kubernetes API server endpoints of an LKE cluster.
• get_control_plane_acl: Show the control plane access list of an LKE cluster: whether it is enabled and the allowed IPv4 and IPv6 ranges.
• list_kubernetes_versions: List the Kubernetes versions available for standard LKE clusters.
• list_tier_versions: List the Kubernetes versions available for one LKE tier (standard or enterprise).
• list_lke_pricing: List LKE add-on prices, such as the high-availability control plane, with hourly and monthly cost and per-region prices.

BYOK key

You bring your own Linode Kubernetes personal access token (read-only scopes are enough) (https://cloud.linode.com/profile/tokens). 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.linode.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://techdocs.akamai.com/linode-api/reference/get-lke-clusters (the API this connector calls, with a BYOK key)

Live from the Linode Kubernetes API (api.linode.com) with a BYOK key; documentation: https://techdocs.akamai.com/linode-api/reference/get-lke-clusters. 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 Linode Kubernetes. Linode 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 Linode Kubernetes account.

Built for: Worldwide. Languages: English.

Linode Kubernetes (BYOK) — Privacy Policy

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

What Linode Kubernetes (BYOK) is. Linode Kubernetes (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Linode Kubernetes data: Read your Linode Kubernetes Engine clusters, node pools, API endpoints, available Kubernetes versions and node pricing with your own personal access token. You bring your own Linode Kubernetes personal access token (read-only scopes are enough); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Linode 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.linode.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 Linode 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 Linode Kubernetes receives. The request we make on your behalf, including the key and the arguments, under Linode Kubernetes's own terms and privacy policy. Linode 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 Linode 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 Linode 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. Linode 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 Linode Kubernetes at any time to end all access.

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

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

Linode Kubernetes (BYOK) — Terms of Service

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

1. The Service. Linode Kubernetes (BYOK) provides: Read your Linode Kubernetes Engine clusters, node pools, API endpoints, available Kubernetes versions and node pricing with your own personal access token. 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 Linode Kubernetes credentials and only access data you are allowed to access. Linode Kubernetes's terms apply to your use of Linode 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 Linode Kubernetes. Linode 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 Linode Kubernetes returns, lightly trimmed; it may be incomplete, delayed or changed by Linode Kubernetes. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Linode 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 Linode 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; Linode 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 Linode 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 Linode 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-linode-lke

Linode Kubernetes (BYOK) support

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

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