Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Linode Node Balancers (BYOK) icon

Linode Node Balancers (BYOK)

Read Linode NodeBalancer pricing, port configs, backend nodes with health, firewalls, traffic stats and VPC attachments with your own personal access token

Unify Dynamics LLC

Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderLinode Node Balancersunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

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

How much does a Linode NodeBalancer cost?
Tools called
list_nodebalancer_types
How is my NodeBalancer 12345 configured and are its backends up?
Tools called
list_configs
Show the health check of NodeBalancer 12345 config 4321
Tools called
get_config
Which backend nodes of NodeBalancer 12345 are down?
Tools called
list_config_nodes
Is node 777 of NodeBalancer 12345 up?
Tools called
get_config_node
Which firewalls protect NodeBalancer 12345?
Tools called
list_nodebalancer_firewalls

About

Linode Node Balancers (BYOK) lets an AI assistant read your own Linode Node Balancers data through the Linode Node Balancers API with a key you supply (personal access token (read-only scopes are enough)). Read-only: 9 tools (list_nodebalancer_types, list_configs, get_config, list_config_nodes, get_config_node, list_nodebalancer_firewalls, get_nodebalancer_stats, list_nodebalancer_vpc_configs, get_nodebalancer_vpc_config). 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 Node Balancers. Linode Node Balancers and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Linode Node Balancers API (api.linode.com) with a BYOK key; documentation: https://techdocs.akamai.com/linode-api/reference/get-node-balancer-configs. 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

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

OpenAPI
Read your data9 tools
  • List nodebalancer typesList the NodeBalancer plan types with hourly and monthly price, regional prices and monthly transfer.
  • List configsList the port configs of a NodeBalancer with port, protocol, algorithm, health check settings and counts of nodes up and down.
  • Get configGet one NodeBalancer config: port, protocol, algorithm, stickiness, health check settings and counts of nodes up and down.
  • List config nodesList the backend nodes of a NodeBalancer config with address, mode, weight and up or down status.
  • Get config nodeGet one backend node of a NodeBalancer config: address, mode, weight and status.
  • List nodebalancer firewallsList the Cloud Firewalls attached to a NodeBalancer with status, tags and default inbound and outbound policy.
  • Get nodebalancer statsGet the last day of connection and traffic in and out data points for a NodeBalancer.
  • List nodebalancer vpc configsList the VPC subnet attachments of a NodeBalancer with VPC, subnet and IPv4 range.
  • Get nodebalancer vpc configGet one VPC attachment of a NodeBalancer: VPC, subnet and IPv4 range.

Information

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

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-linode-nodebalancers.connectorbay.com/mcp
RESTPOST https://byok-linode-nodebalancers.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-linode-nodebalancers.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 personal access token (read-only scopes are enough) in the X-Upstream-Key header (get one at cloud.linode.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Linode Node Balancers connector: questions and answers

What is the Linode Node Balancers connector?

Linode Node Balancers (BYOK) lets an AI assistant read your own Linode Node Balancers data through the Linode Node Balancers API with a key you… It is a hosted MCP server with 9 tools such as List nodebalancer types, List configs, Get config, List config nodes, Get config node, List nodebalancer firewalls, published by Unify Dynamics LLC. It is independent and not affiliated with Linode Node Balancers.

How do I connect Linode Node Balancers to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-linode-nodebalancers.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-linode-nodebalancers.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-linode-nodebalancers.json.

Do I need a Linode Node Balancers account or API key?

Yes: this is a bring-your-own-key connector. Create a personal access token (read-only scopes are enough) at https://cloud.linode.com/profile/tokens 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 Linode Node Balancers read-only?

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

Is the Linode Node Balancers 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

Meraki Device Diagnostics (BYOK)

Read per-device diagnostics of your Cisco Meraki hardware by serial: LLDP/CDP neighbors, WAN loss and latency, switch port status, AP radio status and appliance performance

Live · MCP + REST8 tools

Meraki Fleet Health (BYOK)

Read device model counts, availability, provisioning, power modules, WAN latency, license and end-of-life summaries of your Cisco Meraki fleet with your own key

Live · MCP + REST8 tools

Meraki Sensors (BYOK)

Read the latest and historical readings, alert counts and gateway links of your Cisco Meraki MT environmental sensors with your own Dashboard API key

Live · MCP + REST7 tools

Meraki Switches (BYOK)

Read the port configuration, port status, port usage, client counts, LLDP/CDP neighbors and PoE draw of your Cisco Meraki switches with your own Dashboard API key

Live · MCP + REST7 tools

Meraki Usage Summary (BYOK)

Read top-N usage summaries of your Cisco Meraki organization: busiest appliances, devices, device models, SSIDs, applications, switches by energy and networks by status

Live · MCP + REST8 tools

Meraki Wireless (BYOK)

Read access point channel utilization, packet loss, Ethernet status, client counts and BSSID status of your Cisco Meraki wireless network with your own Dashboard API key

Live · MCP + REST7 tools

Documentation

Back to top

Linode Node Balancers (BYOK) — connector documentation

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

What Linode Node Balancers (BYOK) is for

Linode Node Balancers (BYOK) lets an AI assistant read your own Linode Node Balancers data through the Linode Node Balancers API with a key you supply (personal access token (read-only scopes are enough)). Read-only: 9 tools (list_nodebalancer_types, list_configs, get_config, list_config_nodes, get_config_node, list_nodebalancer_firewalls, get_nodebalancer_stats, list_nodebalancer_vpc_configs, get_nodebalancer_vpc_config). 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 Node Balancers. Linode Node Balancers 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 does a Linode NodeBalancer cost?"
  • "How is my NodeBalancer 12345 configured and are its backends up?"
  • "Show the health check of NodeBalancer 12345 config 4321"
  • "Which backend nodes of NodeBalancer 12345 are down?"
  • "Is node 777 of NodeBalancer 12345 up?"
  • "Which firewalls protect NodeBalancer 12345?"

What it does

  • list_nodebalancer_types: List the NodeBalancer plan types with hourly and monthly price, regional prices and monthly transfer.
  • list_configs: List the port configs of a NodeBalancer with port, protocol, algorithm, health check settings and counts of nodes up and down. TLS keys are not returned.
  • get_config: Get one NodeBalancer config: port, protocol, algorithm, stickiness, health check settings and counts of nodes up and down.
  • list_config_nodes: List the backend nodes of a NodeBalancer config with address, mode, weight and up or down status.
  • get_config_node: Get one backend node of a NodeBalancer config: address, mode, weight and status.
  • list_nodebalancer_firewalls: List the Cloud Firewalls attached to a NodeBalancer with status, tags and default inbound and outbound policy.
  • get_nodebalancer_stats: Get the last day of connection and traffic in and out data points for a NodeBalancer.
  • list_nodebalancer_vpc_configs: List the VPC subnet attachments of a NodeBalancer with VPC, subnet and IPv4 range.
  • get_nodebalancer_vpc_config: Get one VPC attachment of a NodeBalancer: VPC, subnet and IPv4 range.

BYOK key

You bring your own Linode Node Balancers 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

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

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Linode Node Balancers (BYOK) — Privacy Policy

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

What Linode Node Balancers (BYOK) is. Linode Node Balancers (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Linode Node Balancers data: Read Linode NodeBalancer pricing, port configs, backend nodes with health, firewalls, traffic stats and VPC attachments with your own personal access token. You bring your own Linode Node Balancers 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 Node Balancers 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 Node Balancers 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 Node Balancers receives. The request we make on your behalf, including the key and the arguments, under Linode Node Balancers's own terms and privacy policy. Linode Node Balancers 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 Node Balancers 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 Node Balancers 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 Node Balancers (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 Node Balancers at any time to end all access.

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

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

Terms of service

Back to top

Linode Node Balancers (BYOK) — Terms of Service

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

  1. The Service. Linode Node Balancers (BYOK) provides: Read Linode NodeBalancer pricing, port configs, backend nodes with health, firewalls, traffic stats and VPC attachments 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 Node Balancers credentials and only access data you are allowed to access. Linode Node Balancers's terms apply to your use of Linode Node Balancers; 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 Node Balancers. Linode Node Balancers 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 Node Balancers returns, lightly trimmed; it may be incomplete, delayed or changed by Linode Node Balancers. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Linode Node Balancers 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 Node Balancers'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 Node Balancers 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 Node Balancers 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 Node Balancers 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-nodebalancers

Linode Node Balancers (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. Linode Node Balancers (BYOK) never asks for them.

Get Linode Node Balancers (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Linode Node Balancers personal access token (read-only scopes are enough). Create one at https://cloud.linode.com/profile/tokens, 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 Linode Node Balancers. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Linode Node Balancers.