Prefect MCP Server
Prefect workflow resources and documentation access via MCP integration.
Data last scanned today · Reviewed today
Overview
The Prefect MCP Server provides AI assistants with read-only access to Prefect Cloud and self-hosted instances. It allows models to inspect flow runs, logs, and workspace health directly, alongside a built-in documentation proxy for retrieving current CLI, SDK, and deployment guidance.
Our verdict
With a security score of 38/100, this server is classified as high risk. The evaluation reflects that authentication methods and read-only mode implementations have not yet been editorially reviewed, and the project is community-maintained rather than official. It is suitable for experimental use by developers comfortable with active development, but should be avoided in environments where strict, verified security protocols are required.
- Zero direct dependencies minimize supply-chain surface area.
- Active development with commits occurring within the last day.
- Open source project under the MIT license.
- Includes documentation proxy for technical guidance.
- Experimental project subject to frequent, unannounced breaking changes.
- Authentication mechanisms lack independent security review.
- Not maintained by the official Prefect organization.
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›Can this MCP server modify my Prefect flow runs or workspace state?
No, the Prefect MCP server provides read-only tools and cannot change your Prefect state.
›Do I need a local Prefect installation to use the plugins for Claude Code or Codex?
No, the plugins for Claude Code and Codex connect to a hosted MCP server and do not read your local configuration files.
›How do I ensure a local MCP server instance is targeting the correct Prefect workspace?
You should call the get_identity tool before performing actions to confirm which target workspace is currently active.
›Does the local MCP server setup respect my existing Prefect profiles?
Yes, when run locally via stdio, the server automatically uses your local Prefect configuration from ~/.prefect/profiles.toml if it is available.
›How can I connect the server to a self-hosted Prefect instance that requires basic authentication?
You can configure authentication by setting the PREFECT_API_AUTH_STRING environment variable in your local MCP configuration.
Alternatives
Changelog
- Fix0.0.1-beta.13
2026-09-01
- Fix0.0.1-beta.12
2026-06-24
- Improved0.0.1-beta.11
2026-06-18
- Breaking0.0.1-beta.10
2026-02-20
- Newsynchronize all registries
2025-11-03
- Fixhaunted by annotations of versions past
2025-11-03
- Improved0.0.1-beta.7
2025-10-17
- Improved0.0.1-beta.6
2025-10-17
- Improved0.0.1-beta.5
2025-10-17
- Improved0.0.1-beta.4
2025-10-17
Badge
Maintain this server? Add the live badge to your README.