Skip to content
PrefectPrefect
Sign up
All agent resources

Prefect with Cursor

Connect Cursor to Prefect’s MCP server to look up runs, logs, and deployments from your editor.

Before you start

Cursor, uv installed and available on PATH, and a configured Prefect profile or environment variables for your target server. This setup uses local credentials, not the hosted plugin’s sign-in.

Setup

  1. Configure your Prefect connection

    Use the MCP setup guide to configure your Cloud workspace or self-hosted server locally. Keep API keys out of committed files.

    Prefect connection setup

  2. Add the MCP configuration

    Merge this entry into your project’s .cursor/mcp.json. Keep any other servers already configured there.

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

  3. Enable the server in Cursor

    Check Cursor’s MCP settings for the Prefect tools. If the server cannot start, confirm Cursor can find uvx and your Prefect configuration.

Ask Cursor to configure the connection

Paste this into your coding agent to walk through the setup.

Help me connect Cursor to Prefect using https://docs.prefect.io/v3/how-to-guides/ai/use-prefect-mcp-server. Check whether uvx is available and whether this project already has .cursor/mcp.json. Ask which Prefect Cloud workspace or self-hosted server I want to use. With my approval, merge the official prefect-mcp stdio configuration into the existing file without removing other servers. Keep credentials out of chat and version control. Verify the connection and report the active target without changing any workflows.

If the connection fails

An empty result can mean the server is using the wrong local profile. Check the configured API URL and authentication in the MCP setup guide; do not paste API keys into chat.

Documentation & source

Cursor configuration referencePrefect MCP documentation