Terminal
Terminal/Skill
Helps diagnose failing Prefect workflows, deployments and work pools using read-only Prefect MCP tools, and points to the CLI for changes.
By Prefect
Works with
npx skills add prefecthq/prefect-mcp-server --skill workflowsUse the Prefect MCP tools as the canonical source for Prefect state, documentation, and release notes. They return structured data with complete identifiers and are read-only unless a tool explicitly says otherwise.
The hosted MCP server authenticates with Prefect Cloud OAuth. If a tool needs a
workspace_id and the user has not selected one:
list_authorized_workspaces.workspace_id consistently to subsequent tool calls.Never guess a workspace ID or copy one from an unrelated result.
Start broad and narrow only as needed:
get_dashboard for an overview of recent failures, lateness, deployments,
and work-pool health.get_flow_runs to inspect the affected run and preserve its full UUID.get_deployments, get_work_pools, get_task_runs, or read_events for
the specific layer implicated by the run.Do not repeatedly fetch broad lists when a specific ID is already known.
Use the Prefect documentation tools for current CLI, SDK, deployment, and release information. For release questions, search for the current structured release notes and report the exact version and release date returned by the source.
Do not answer version-sensitive questions from memory when the documentation tools are available.
The hosted Prefect MCP surface is read-only. Do not claim that it triggered, cancelled, created, updated, or deleted anything unless an exposed tool actually performed that operation.
A local Prefect CLI is a separate, advanced path. Use it only when all of these are true:
prefect version succeeds;Otherwise, explain that the connected MCP tools are read-only and provide the exact CLI command for the user to run without pretending it was executed.
When a configured local CLI is appropriate:
prefect --no-prompt for commands that would otherwise prompt;prefect api or -o json when machine-readable output is needed;Common commands:
prefect deployment run 'flow-name/deployment-name'
prefect --no-prompt flow-run cancel <flow-run-uuid>
prefect automation create --from-file automation.yaml