Skip to main content
The Prefect integration is an operational connector for an externally-operated Prefect instance (Cloud or OSS). Agents can monitor flow runs, deployments, task runs, and work pools, and — with approval — trigger or cancel runs. An admin configures the connection once and it is shared tenant-wide.

​
What you’ll need

  • The API URL of your Prefect instance (a Prefect Cloud workspace URL or your OSS API endpoint).
  • An API key (Prefect Cloud) or auth string (OSS), if your instance requires one.

​
How it connects

An admin enters the credentials in the Integrations admin modal. Aperium detects Cloud versus OSS and stores the secret encrypted against the tenant; routing metadata (API URL, account and workspace ids) is derived from the input. Setup does no network I/O — the URL is not dialed at save time, which avoids an SSRF vector against the operator-submitted host. Connectivity is validated on the first tool call.

​
Setup

1

Open the Prefect setup form

In the admin onboarding flow or the Admin Console’s MCP Servers tab, open the Prefect connector’s setup form.
2

Enter the API URL and credential

Fill in Prefect API URL and Credential Type (non-secret), then paste the API Credential (secret). Click Enable.

​
What agents can read

Ten read tools cover monitoring conversations:
  • Searches over flow runs, deployments, task runs, flows, and work-pool workers. These adapt into queryable datasets, so charting or counting run history is a single query plan.
  • Snapshots — identity, a composed dashboard, flow-run logs, work pools, and automations.

​
What agents can write

Two write tools are available, both approval-gated and restricted by a tenant-admin role floor — the agent must surface the action for a human to approve before it runs:
  • Trigger a deployment run.
  • Cancel a flow run.
This connector points at your own externally-operated Prefect instance. It does not author flows or deployments, and it never manages the Prefect server itself.