Pav Staz
03/30/2026, 12:17 PMMarvin
03/30/2026, 12:17 PMMarvin
03/30/2026, 12:18 PM{
"mcpServers": {
"prefect-files": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"--rootDir",
"/path/to/prefect-repo-or-docs"
]
}
}
}
Example using a GitHub MCP server:
{
"mcpServers": {
"prefect-github": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-github"
],
"env": {
"GITHUB_TOKEN": "YOUR_TOKEN"
}
}
}
}
Helpful links:
- MCP overview and registry: modelcontextprotocol.io
- Claude Desktop + MCP: Claude MCP docs
- Prefect docs: docs.prefect.io
- Prefect repo: PrefectHQ/prefect
2) Operator tools (let Claude run Prefect commands safely)
- Give Claude a constrained “process/shell” MCP server or a small custom MCP server that exposes just the Prefect operations you’re comfortable with (e.g., listing work pools, checking deployments, inspecting runs).
- This keeps execution safe and auditable while enabling hands-on help when you ask “what’s failing?” or “deploy this flow.”
3) Your workspace integration (query Prefect Cloud/Server)
- Wrap Prefect’s REST API as MCP tools so Claude can answer questions grounded in your workspace data (flows, deployments, run states).
- You’d provide PREFECT_API_URL and PREFECT_API_KEY in the tool/server environment.
- API reference: Prefect API reference
If you tell me which of these you want:
- A) Docs/citation only
- B) Run local Prefect commands
- C) Inspect your Prefect workspace data
I can share a minimal, copy/paste config (and a tiny starter server if needed) tailored to your OS and setup.