Hetzner Cloud Catalog (BYOK)
Read the Hetzner Cloud server types, load balancer types, OS images, ISOs and price list with your own project API token
Read your Signadot Kubernetes preview environments: sandboxes, route groups, connected clusters and resource plugins, with your own API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_organizationslist_sandboxesget_sandboxlist_route_groupsget_route_grouplist_clustersSignadot (BYOK) lets an AI assistant read your own Signadot data through the Signadot API with a key you supply (Signadot API key). Read-only: 9 tools (list_organizations, list_sandboxes, get_sandbox, list_route_groups, get_route_group, list_clusters, get_cluster, list_resource_plugins, get_resource_plugin). 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.signadot.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Signadot. Signadot and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Signadot API (api.signadot.com) with a BYOK key; documentation: https://www.signadot.com/docs/guides/admin/api-keys. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
9 tools, grouped by job. Every one is read-only or compute-only.
https://byok-signadot.connectorbay.com/mcpThree ways in, the same 9 tools.
https://byok-signadot.connectorbay.com/mcpPOST https://byok-signadot.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-signadot.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at app.signadot.com).Signadot (BYOK) lets an AI assistant read your own Signadot data through the Signadot API with a key you supply (Signadot API key). It is a hosted MCP server with 9 tools such as List organizations, List sandboxes, Get sandbox, List route groups, Get route group, List clusters, published by Unify Dynamics LLC. It is independent and not affiliated with Signadot.
Add the MCP endpoint https://byok-signadot.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-signadot.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-signadot.json.
Yes: this is a bring-your-own-key connector. Create a Signadot API key at https://app.signadot.com and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read the Hetzner Cloud server types, load balancer types, OS images, ISOs and price list with your own project API token
Read the structure of your Front knowledge bases: bases, categories and articles with locales, slugs and dates (no article text), with your own API token
Read how your Front workspace is set up: teams, teammate groups, rules (names only), shifts, ticket statuses, tags and custom field definitions, with your own API token
Read how access is organised in Pipedrive: roles, role settings, permission sets, teams and users (no email or phone) with your own personal API token
Read aggregate Pipedrive sales figures: deal totals, pipeline conversion and movement statistics and goals with progress, using your own personal API token
Read your Pipedrive field definitions, activity types, lead labels and sources, currencies and saved filters with your own personal API token
https://byok-signadot.connectorbay.com/mcpPOST https://byok-signadot.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-signadot.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-signadot.connectorbay.com/health · Tool schemas: https://byok-signadot.connectorbay.com/tools.jsonSignadot (BYOK) lets an AI assistant read your own Signadot data through the Signadot API with a key you supply (Signadot API key). Read-only: 9 tools (list_organizations, list_sandboxes, get_sandbox, list_route_groups, get_route_group, list_clusters, get_cluster, list_resource_plugins, get_resource_plugin). 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.signadot.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Signadot. Signadot 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:
list_organizations: List the Signadot organizations the API key can access, with the organization name needed by the other tools.list_sandboxes: List the sandboxes in a Signadot organization with routing key, cluster, description, preview endpoints and status.get_sandbox: Get one sandbox: routing key, cluster, description, preview endpoints and readiness status.list_route_groups: List the route groups in a Signadot organization with routing key, cluster, endpoints and matched sandboxes.get_route_group: Get one route group: routing key, cluster, endpoints, and status with matched sandboxes.list_clusters: List the Kubernetes clusters connected to a Signadot organization with creation time and operator version.get_cluster: Get one connected cluster: creation time and Signadot operator version (cluster tokens are not exposed).list_resource_plugins: List the resource plugins registered in a Signadot organization with creation and update time and status.get_resource_plugin: Get one resource plugin: creation and update time and status.You bring your own Signadot Signadot API key (https://app.signadot.com). 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.signadot.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.
Live from the Signadot API (api.signadot.com) with a BYOK key; documentation: https://www.signadot.com/docs/guides/admin/api-keys. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Signadot. Signadot 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 Signadot account.
Built for: Worldwide. Languages: English.
Effective 16 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Signadot (BYOK) is. Signadot (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Signadot data: Read your Signadot Kubernetes preview environments: sandboxes, route groups, connected clusters and resource plugins, with your own API key. You bring your own Signadot Signadot API key; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Signadot 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.signadot.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 Signadot 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 Signadot receives. The request we make on your behalf, including the key and the arguments, under Signadot's own terms and privacy policy (https://www.signadot.com/terms-of-service). Signadot acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Signadot 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 Signadot 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. Signadot (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 Signadot at any time to end all access.
Children. Signadot (BYOK) is a general-audience service operated by the adult using the assistant, under Signadot's own age rules.
Changes. We will post changes here with a new effective date.
Effective 16 October 2026. These terms govern use of the Signadot (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-signadot.connectorbay.com/mcphttps://byok-signadot.connectorbay.com/openapi.jsonWhen 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. Signadot (BYOK) never asks for them.