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

Signadot (BYOK)

Read your Signadot Kubernetes preview environments: sandboxes, route groups, connected clusters and resource plugins, with your own API key

Unify Dynamics LLC

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

Try asking

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

Which Signadot organizations can my key access?
Tools called
list_organizations
Which Signadot sandboxes are running in my org?
Tools called
list_sandboxes
Show the Signadot sandbox checkout-pr-482
Tools called
get_sandbox
Which Signadot route groups do I have?
Tools called
list_route_groups
Show the Signadot route group payments-rg
Tools called
get_route_group
Which clusters are connected to my Signadot org?
Tools called
list_clusters

About

Signadot (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.

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 organizationsList the Signadot organizations the API key can access, with the organization name needed by the other tools.
  • List sandboxesList the sandboxes in a Signadot organization with routing key, cluster, description, preview endpoints and status.
  • Get sandboxGet one sandbox: routing key, cluster, description, preview endpoints and readiness status.
  • List route groupsList the route groups in a Signadot organization with routing key, cluster, endpoints and matched sandboxes.
  • Get route groupGet one route group: routing key, cluster, endpoints, and status with matched sandboxes.
  • List clustersList the Kubernetes clusters connected to a Signadot organization with creation time and operator version.
  • Get clusterGet one connected cluster: creation time and Signadot operator version (cluster tokens are not exposed).
  • List resource pluginsList the resource plugins registered in a Signadot organization with creation and update time and status.
  • Get resource pluginGet one resource plugin: creation and update time and status.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-signadot.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-signadot.connectorbay.com/mcp
RESTPOST https://byok-signadot.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-signadot.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 Signadot API key in the X-Upstream-Key header (get one at app.signadot.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Signadot connector: questions and answers

What is the Signadot connector?

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.

How do I connect Signadot to Claude, ChatGPT or Cursor?

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.

Do I need a Signadot account or API key?

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.

Is Signadot read-only?

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

Is the Signadot 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

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

Live · MCP + REST7 tools

Front Knowledge Base (BYOK)

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

Live · MCP + REST7 tools

Front Workspace (BYOK)

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

Live · MCP + REST12 tools

Pipedrive Access (BYOK)

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

Live · MCP + REST8 tools

Pipedrive Reports (BYOK)

Read aggregate Pipedrive sales figures: deal totals, pipeline conversion and movement statistics and goals with progress, using your own personal API token

Live · MCP + REST5 tools

Pipedrive Settings (BYOK)

Read your Pipedrive field definitions, activity types, lead labels and sources, currencies and saved filters with your own personal API token

Live · MCP + REST10 tools

Documentation

Back to top

Signadot (BYOK) — connector documentation

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

What Signadot (BYOK) is for

Signadot (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:

  • "Which Signadot organizations can my key access?"
  • "Which Signadot sandboxes are running in my org?"
  • "Show the Signadot sandbox checkout-pr-482"
  • "Which Signadot route groups do I have?"
  • "Show the Signadot route group payments-rg"
  • "Which clusters are connected to my Signadot org?"

What it does

  • 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.

BYOK key

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.

Data 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.

What it is not

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.

Privacy policy

Back to top

Signadot (BYOK) — Privacy Policy

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.

Terms of service

Back to top

Signadot (BYOK) — Terms of Service

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

  1. The Service. Signadot (BYOK) provides: Read your Signadot Kubernetes preview environments: sandboxes, route groups, connected clusters and resource plugins, 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 Signadot credentials and only access data you are allowed to access. Signadot's terms (https://www.signadot.com/terms-of-service) apply to your use of Signadot; 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 Signadot. Signadot 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 Signadot returns, lightly trimmed; it may be incomplete, delayed or changed by Signadot. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Signadot 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 Signadot'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; Signadot 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 Signadot 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 Signadot 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-signadot

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

Get Signadot (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Signadot Signadot API key. Create one at https://app.signadot.com, 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 Signadot. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Signadot.