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

Prefect Cloud Ops (BYOK) — connector documentation

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

What Prefect Cloud Ops (BYOK) is for

Prefect Cloud Ops (BYOK) lets an AI assistant read your own Prefect Cloud Ops data through the Prefect Cloud Ops API with a key you supply (API key). Read-only: 11 tools (list_work_queues, list_work_pool_queues, list_work_pool_workers, list_flow_run_task_runs, list_automations, list_global_concurrency_limits, list_block_types, list_artifacts, list_variable_names, get_flow_run, get_deployment). 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 Ops. Prefect Cloud Ops 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 work queues are paused or backed up?"
  • "Which queues does the Prefect work pool default-pool have?"
  • "Are the workers of Prefect work pool default-pool alive?"
  • "Which tasks of Prefect flow run 7a3b2c1d-0000-0000-0000-000000000000 failed?"
  • "Which Prefect automations are enabled?"
  • "Which Prefect concurrency limits are fully used?"

What it does

  • list_work_queues: List work queues of a Prefect workspace with pool, priority, paused flag, concurrency limit, active slots, status and last poll time.
  • list_work_pool_queues: List the work queues of one work pool with priority, paused flag, concurrency limit, status and last poll time.
  • list_work_pool_workers: List the workers of one work pool with status and last heartbeat time.
  • list_flow_run_task_runs: List the task runs of one flow run with state, run count, start and end time and run time. Inputs and results are not returned.
  • list_automations: List automations (triggers and the actions they run) with name, description, enabled flag and tags. Trigger and action definitions are not returned.
  • list_global_concurrency_limits: List global concurrency limits with limit, active slots, slot decay and active flag.
  • list_block_types: List block types (the kinds of configuration blocks a workspace can hold) with name, slug, description and protected flag. No block contents are returned.
  • list_artifacts: List artifacts (markdown, links, tables and progress records created by runs) with key, type, description and the run that created them. Artifact data is not returned.
  • list_variable_names: List the names, tags and timestamps of workspace variables. Variable values are not returned.
  • get_flow_run: Get one flow run: state, deployment, work pool and queue, start and end time, run time, run count, tags and who created it. Parameters and logs are not returned.
  • get_deployment: Get one deployment: flow, paused flag, schedules, work pool and queue, tags, entrypoint, concurrency limit, status and last poll. Parameters, job variables and pull steps are not returned.

BYOK key

You bring your own Prefect Cloud Ops 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 Ops API (api.prefect.cloud) with a BYOK key; documentation: https://docs.prefect.io/v3/api-ref/rest-api. 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 Ops. Prefect Cloud Ops 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 Ops account.

Built for: Worldwide. Languages: English.