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

Prefect Cloud (BYOK) — connector documentation

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

What Prefect Cloud (BYOK) is for

Prefect Cloud (BYOK) lets an AI assistant read your own Prefect Cloud data through the Prefect Cloud API with a key you supply (API key). Read-only: 8 tools (get_my_accounts, get_account, get_account_usage, list_workspaces, list_flows, list_deployments, list_flow_runs, list_work_pools). 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.prefect.cloud. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Prefect Cloud. Prefect Cloud 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 Prefect Cloud accounts do I belong to?"
  • "What is the name and handle of my Prefect Cloud account?"
  • "How many deployments and work pools does each Prefect workspace have?"
  • "Which workspaces are in my Prefect Cloud account?"
  • "Which flows are registered in my Prefect workspace?"
  • "Which Prefect deployments are paused?"

What it does

  • get_my_accounts: List the Prefect Cloud accounts the key can access, with account id, name, handle, your role and plan type.
  • get_account: Show one Prefect Cloud account: name, handle and creation time.
  • get_account_usage: Show Prefect Cloud usage per workspace: number of deployments, automations and work pools.
  • list_workspaces: List workspaces in a Prefect Cloud account with id, name, handle and visibility.
  • list_flows: List flows registered in a Prefect workspace with name, tags and creation time.
  • list_deployments: List deployments in a Prefect workspace with flow id, work pool, paused and schedule flags and last update.
  • list_flow_runs: List flow runs in a Prefect workspace with flow, deployment, state, start and end time and total run time. Parameters and logs are not returned.
  • list_work_pools: List work pools in a Prefect workspace with type, paused flag, concurrency limit, status and last poll time.

BYOK key

You bring your own Prefect Cloud API key (https://app.prefect.cloud/my/api-keys). 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.prefect.cloud 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 Prefect Cloud API (api.prefect.cloud) with a BYOK key; documentation: https://api.prefect.cloud/api/openapi.json. 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 Prefect Cloud. Prefect Cloud 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 Prefect Cloud account.

Built for: Worldwide. Languages: English.