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

Cloud 66 (BYOK)

Read your Cloud 66 stacks, servers, deployments and services with BYOK

Unify Dynamics LLC

Tools5read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderCloud 66unofficial, not affiliated
Works withMCP · RESTany agent

Try asking

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

What stacks do I have on Cloud 66, and are they healthy?
Tools called
list_stacks
Show details of this Cloud 66 stack
Tools called
get_stack
Which servers does this Cloud 66 stack run on?
Tools called
list_servers
Did the latest Cloud 66 deployments succeed?
Tools called
list_deployments
Which services does this Cloud 66 stack run?
Tools called
list_services

About

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.

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.

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

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

OpenAPI
Read your data5 tools
  • List stacksList the Cloud 66 stacks (applications) you can access with environment, cloud, language, status, health and last activity.
  • Get stackGet one Cloud 66 stack by UID: environment, cloud, domain, language, framework, status, health and timestamps.
  • List serversList the servers of a Cloud 66 stack with address, OS, roles, region, health state and creation time.
  • List deploymentsList the deployments of a Cloud 66 stack with outcome, type, commit hash, start and finish times and live flag.
  • List servicesList the Docker services of a Cloud 66 stack with name, image, branch and timestamps.

Information

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

More like this

More in Other

Smithsonian Open Access (BYOK)

Search the Smithsonian Open Access collections of museum objects, archives and specimens and read their records with your own api.data.gov key

Live · MCP + REST5 tools

Lens (BYOK)

Search scholarly works and patents on Lens and read their records, citations and legal status with your own API access token

Live · MCP + REST5 tools

Cincopa (BYOK)

Read your Cincopa hosted videos, images and audio assets, galleries, tags, portals and live streams with your own API token

Live · MCP + REST7 tools

Guru (BYOK)

Read your Guru knowledge cards, collections, folders, tags, version history and team trust statistics with your own user email and API token

Live · MCP + REST10 tools

Paragraph (BYOK)

Read your Paragraph newsletter publication, posts, drafts, subscriber count and content groups, and search public posts, with your own API key

Live · MCP + REST11 tools

Localazy (BYOK)

Read your Localazy localization projects, files, source keys and translations, glossary, screenshots and CDN release tags with your own API token

Live · MCP + REST8 tools

Get Cloud 66 (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Cloud 66 personal access token (public scope is enough). Create one at https://app.cloud66.com/oauth/authorized_applications, 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 Cloud 66. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Cloud 66.