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

Prefect Cloud Ops (BYOK)

Read Prefect Cloud work queues, workers, task runs, automations, concurrency limits, block types, artifacts and variable names, plus single flow runs and deployments, with your own API key

Unify Dynamics LLC

Tools11read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderPrefect Cloud Opsunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

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

Which Prefect work queues are paused or backed up?
Tools called
list_work_queues
Which queues does the Prefect work pool default-pool have?
Tools called
list_work_pool_queues
Are the workers of Prefect work pool default-pool alive?
Tools called
list_work_pool_workers
Which tasks of Prefect flow run 7a3b2c1d-0000-0000-0000-000000000000 failed?
Tools called
list_flow_run_task_runs
Which Prefect automations are enabled?
Tools called
list_automations
Which Prefect concurrency limits are fully used?
Tools called
list_global_concurrency_limits

About

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.

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.

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

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

OpenAPI
Read your data11 tools
  • List work queuesList work queues of a Prefect workspace with pool, priority, paused flag, concurrency limit, active slots, status and last poll time.
  • List work pool queuesList the work queues of one work pool with priority, paused flag, concurrency limit, status and last poll time.
  • List work pool workersList the workers of one work pool with status and last heartbeat time.
  • List flow run task runsList the task runs of one flow run with state, run count, start and end time and run time.
  • List automationsList automations (triggers and the actions they run) with name, description, enabled flag and tags.
  • List global concurrency limitsList global concurrency limits with limit, active slots, slot decay and active flag.
  • List block typesList block types (the kinds of configuration blocks a workspace can hold) with name, slug, description and protected flag.
  • List artifactsList artifacts (markdown, links, tables and progress records created by runs) with key, type, description and the run that created them.
  • List variable namesList the names, tags and timestamps of workspace variables.
  • Get flow runGet one flow run: state, deployment, work pool and queue, start and end time, run time, run count, tags and who created it.
  • Get deploymentGet one deployment: flow, paused flag, schedules, work pool and queue, tags, entrypoint, concurrency limit, status and last poll.

Information

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

More like this

More in Other

Freshservice Releases (BYOK)

Read your Freshservice release records, release form fields, requester groups and requester field definitions with your own API key

Live · MCP + REST5 tools

Freshservice Projects (BYOK)

Read your Freshservice projects, project templates, fields, task statuses, priorities, task types, sprints and versions with your own API key

Live · MCP + REST8 tools

Freshservice Status Page (BYOK)

Read your Freshservice status pages: service components and their status, incidents, planned maintenances and status labels with your own API key

Live · MCP + REST6 tools

Freshservice ITAM (BYOK)

Read your Freshservice IT Asset Management inventory: devices, assets, physical subtypes, lifecycle events, cloud accounts and cloud resources with your own API key

Live · MCP + REST6 tools

Freshservice Asset Config (BYOK)

Read your Freshservice asset types, asset fields, products, vendors, contracts, contract types, purchase orders and relationship types with your own API key

Live · MCP + REST9 tools

Freshservice Org Config (BYOK)

Read your Freshservice departments, locations, agent groups, roles, workspaces, announcements and ticket, change and problem form fields with your own API key

Live · MCP + REST10 tools

Get Prefect Cloud Ops (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Prefect Cloud Ops API key. Create one at https://app.prefect.cloud/my/api-keys, 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 Prefect Cloud Ops. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Prefect Cloud Ops.