Claude Prefect connectorWhat Claude can do in your Prefect workspaces.
The Claude Prefect connector exposes 15 tools, all 15 reading, 0 writing, 0 undocumented. Here: what Claude can inspect in your Prefect Cloud workspaces, why it stops at diagnosis, what it asks before acting, and who in your organization can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can look inside Prefect
When a run fails, the manual route is to open the Prefect UI, find the run, scroll its logs, then check the work pool and the deployment. With this connector you ask Claude why the run failed, and it goes through runs, logs, pools and events itself before explaining what it found. Prefect describes the hosted tools as read-only: Claude diagnoses, it does not fix.
A failed run explained in plain words. A run ended in failure: get_flow_runs finds it, and get_flow_run_logs pulls its log entries with levels, timestamps and messages.
Late runs traced to their cause. Runs pile up as late: get_dashboard shows run statistics, pool status and active concurrency limits, while get_work_pools returns each pool's name, type, status and concurrency limit, a tool Prefect calls essential when runs are stuck or do not start.
Answers from the current docs. A question on a Prefect concept comes up: docs_search_prefect searches the Prefect documentation, and docs_get_release_notes checks what changed in a given version.
Now what the directory sheet does not say. Prefect's guide is explicit that creating or updating resources goes through the prefect CLI or SDK, not through these tools. The connector reaches Prefect Cloud workspaces you pick during sign-in; a self-hosted Prefect server needs another setup that Prefect documents separately. And nothing runs on its own: no tool wakes up when a run fails. For alerts that fire in the background you need an automation tool, a different job; the Integrations hub gathers that side.
The vocabulary in one minute
Five words you will meet while connecting Prefect.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do in that account. Claude picks the ones it needs; the directory sheet lists them by name.
- Authorization
- Prefect Cloud's own sign-in screen, where you choose what Claude may reach. Granted once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before it goes ahead with an action, shown in the conversation at the moment it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to a service outside it.
Setting up the Claude Prefect connector in three steps
- 01
Find Prefect in Claude
Open Claude's settings, go to Customize, then Connectors, and look for Prefect in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector before each member can sign in on their own.
- 02
Connect from its row
Click Connect on the Prefect row, then sign in to Prefect Cloud in the window the service opens itself. If the link breaks later, Disconnect and connect again.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to Prefect, not to Claude, and it is what decides how far the access reaches, including which workspaces Claude may read.
The 15 tools, split by what they do
Prefect gives Claude 15 tools: 15 that read your account, 0 that change something in it.
All fifteen look at your Prefect Cloud workspaces or at the Prefect documentation. Names stay exactly as Claude displays them.
- 15 read
What Claude reads (15)
15 toolsFifteen tools that inspect workflows and docs and leave your workspace untouched.
docs_get_release_notes
Fetches Prefect's open-source release notes, either the latest ones or those of a specific version, for a version-specific question. It is one of the documentation tools: it reads Prefect's public release notes, not your workspace.
docs_search_prefect
Searches the Prefect documentation for concepts, usage examples and recommended practices. Claude then answers from the documentation rather than from memory. Like the release notes tool, it does not touch your workspace data.
get_automations
Returns the automations of a workspace in a short summary, or in full detail with trigger settings and actions when you ask about specific ones.
get_dashboard
Gives a high-level overview: current flow run statistics, work pool status and every active concurrency limit. Prefect presents it as the first stop for delays and bottlenecks.
get_deployments
Lists deployments with optional filters, as short summaries by default. Asked about specific ones, it adds their parameters, job variables, work pool details and most recent runs.
get_flow_run_logs
Retrieves the log entries of one flow run, with their timestamps, levels and messages, so Claude can read the failure where it happened.
get_flow_runs
Finds flow runs matching filters, with compact summaries by default and full detail, including parameters and work pool, for the runs you name.
get_flows
Lists the flows registered in the workspace, with optional filters. It gives Claude the inventory of flows before it looks at runs or deployments. Prefect registers it, like the other inspection tools, as read-only in its server code.
get_identity
Reports which Prefect instance the connection points to: its API address, whether it is Cloud or open source, and user details when available.
get_object_schema
Returns the schema of a complex object type, automations in particular, so Claude understands how they are structured. Prefect's orientation tool lists schemas among the capabilities it supports.
get_task_runs
Lists task runs matching filters, with their details, inside the flows of the workspace.
get_work_pools
Shows work pools with optional filters, as compact summaries by default: name, type, status and concurrency limit. Prefect calls it essential for debugging runs that are stuck or never start.
list_authorized_workspaces
Lists the Prefect Cloud workspaces you selected when you authorized the connection, with their account handles, workspace handles and identifiers.
orientation
Gives Claude an overview of what the Prefect tools cover and where their boundaries lie, without reaching into your Prefect data.
read_events
Reads and filters the events of the Prefect instance and lays them out in a structured view.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes on an account on your behalf. Prefect's own guide tells you to approve tool calls when Claude prompts you.
All fifteen tools only look things up, and Prefect describes them as read-only. No source sets a confirmation rule for one Prefect tool in particular, so the default behaviour applies. On Team and Enterprise workspaces, owners decide whether members may let certain actions through without being asked, and they can restrict what a connector may do for the whole organization. Claude works with your Prefect rights only: what your account cannot see, Claude cannot see either.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. The answer, connector by connector, is not published anywhere: a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can sign in. For the current state, check the Prefect sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a run fails, a pool empties or a deployment changes.
By default the sheet only exposes reading, and that is an observed floor, not a promise: an administrator can open actions that no public sheet shows. This connector has no Claude help article of its own; what we know comes from the directory sheet, Prefect's guide and the code Prefect publishes for its server. The directory's verified badge is not a security audit, and Anthropic writes on every sheet that it does not control which tools a publisher exposes.
Need help connecting Prefect to Claude?
A person reads every message.