Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Cloud 66 (BYOK) — connector documentation

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

What Cloud 66 (BYOK) is for

Cloud 66 (BYOK) lets an AI assistant read your own Cloud 66 data through the Cloud 66 API with a key you supply (personal access token (public scope is enough)). Read-only: 5 tools (list_stacks, get_stack, list_servers, list_deployments, list_services). 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 app.cloud66.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Cloud 66. Cloud 66 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:

  • "What stacks do I have on Cloud 66, and are they healthy?"
  • "Show details of this Cloud 66 stack"
  • "Which servers does this Cloud 66 stack run on?"
  • "Did the latest Cloud 66 deployments succeed?"
  • "Which services does this Cloud 66 stack run?"

What it does

  • list_stacks: List the Cloud 66 stacks (applications) you can access with environment, cloud, language, status, health and last activity.
  • get_stack: Get one Cloud 66 stack by UID: environment, cloud, domain, language, framework, status, health and timestamps. The redeploy hook is not returned.
  • list_servers: List the servers of a Cloud 66 stack with address, OS, roles, region, health state and creation time.
  • list_deployments: List the deployments of a Cloud 66 stack with outcome, type, commit hash, start and finish times and live flag. Who triggered them is not returned.
  • list_services: List the Docker services of a Cloud 66 stack with name, image, branch and timestamps. Commands are not returned.

BYOK key

You bring your own Cloud 66 personal access token (public scope is enough) (https://app.cloud66.com/oauth/authorized_applications). 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 app.cloud66.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.

Notices

List answers return the first page (30 items); the page request parameter is not documented by Cloud 66. Redeploy hooks and git URLs are never returned.

Data sources

Live from the Cloud 66 API (app.cloud66.com) with a BYOK key; documentation: https://developers.cloud66.com/v3. 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 Cloud 66. Cloud 66 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 Cloud 66 account.

Built for: Worldwide. Languages: English.