Prefect MCP Server

io.github.PrefectHQPublished by GitHub account PrefectHQv0.0.1-beta.13Updated Oct 24, 2026

MCP server for Prefect. Monitor and debug workflows, deployments, and automations.

Overview

AI-generated overview

Local MCP server for Prefect that lets an assistant monitor and debug workflows, deployments and automations.

What you can do
  • Monitor and debug Prefect workflows, deployments and automations.
  • No tool list is published, so the exact operations available are not documented in the supplied material.
When to use it
Useful when you run Prefect for data or application workflows and want an assistant to help inspect and troubleshoot runs, deployments and automations from the same session.
Requirements
Runs as a local process over stdio, installed from the PyPI package prefect-mcp, so a Python environment is needed. No environment variables, headers or authentication are declared; it presumably needs access to a Prefect instance, but the input does not specify how that is configured.
Before you install
No credentials or secrets are declared, and no tool list is published, so what the server can read or change in your Prefect workspace cannot be verified from the supplied material. Review its behavior before pointing it at production workflows.

Installation

In SourceWeft

  1. Open Prefect MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.0.1-beta.13LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.