Prefect MCP Server

uvx --from prefect-mcp prefect-mcp-server

{
  "mcpServers": {
    "prefect-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "prefect-mcp",
        "prefect-mcp-server"
      ]
    }
  }
}

Prefect's own server is deliberately read-only: it inspects deployments, flows, flow runs, task runs, work pools and automations, pulls execution logs and events, and proxies Prefect documentation so an assistant can quote current CLI and SDK guidance instead of guessing. That scope makes it a debugging tool — the agent explains why a run failed, and a human decides what to do about it. Prefect Cloud users can attach the hosted endpoint through a client plugin and authorize workspaces over OAuth; self-hosted instances run the same server locally, where stdio mode picks up the active profile from ~/.prefect/profiles.toml or explicit API URL and key variables. The repository states plainly that the project is experimental and its surface may change.