Skip to content
Cursor integration

Connect Cursor to your Agiflow board

Connecting Cursor to Agiflow over MCP lets the editor read and update your Agiflow projects, work units, tasks, and comments, scoped by the connection URL you authorize.

Give Cursor scoped access to Agiflow projects, work units, tasks, and comments so implementation work can stay tied to the board it came from.

Add to Cursor opens Cursor with a placeholder MCP config; paste your Agiflow connection URL from Settings → Connections to finish.

Last updated May 31, 2026 · Published by Agiflow, based on Agiflow product documentation and Cursor public MCP documentation captured 2026-05-31.

Cursor and Agiflow — connect Cursor to your Agiflow board over MCP.

Work from the board without leaving Cursor

Cursor is an AI code editor by Anysphere. The Agiflow MCP connection lets Cursor work with the project context your team already maintains: projects, work units, tasks, task comments, and members. Use it when a coding task needs the actual board state, not a copied brief.

Agiflow scopes each connection to the organization, project, work unit, or task you choose. Cursor can then read and update the Agiflow data exposed by that connection, subject to the authorization you approve.

Cursor uses MCP in Agent mode and may ask for approval before tool calls depending on your Cursor settings.

Give Cursor the work context it needs

Projects and work units

Let Cursor inspect project structure and the work units that break larger initiatives into shippable pieces.

Tasks and comments

Let Cursor read task details, update task records, and use comments as implementation context.

Scoped access

Choose the Agiflow connection scope before connecting, so Cursor only receives the board context intended for that project, work unit, or task.

Connect Agiflow to Cursor

Use the connection URL Agiflow gives you. Do not paste a generic endpoint.

  1. Step 1. Copy your Agiflow connection URL

    Log in to Agiflow, open Settings → Connections, and copy the URL shown for the scope you want Cursor to use.

  2. Step 2. Add Agiflow to Cursor

    Create .cursor/mcp.json in the code project and paste this config, replacing YOUR_AGIFLOW_URL with the URL copied from Agiflow:

    {
      "mcpServers": {
        "agiflow": {
          "type": "http",
          "url": "YOUR_AGIFLOW_URL"
        }
      }
    }

    Use the project settings file when Agiflow should only be available in this code project. Use Cursor’s user-level settings file when you want the same connection available across projects.

  3. Step 3. Restart Cursor

    Close and reopen Cursor so it picks up the new MCP settings.

  4. Step 4. Turn on Agiflow and sign in

    Open Cursor settings, enable the Agiflow entry, then complete the browser sign-in flow. Log in to Agiflow and click Authorize. Cursor remembers the connection after authorization.

  5. Step 5. Try a board prompt

    Ask Cursor:

    What tasks do I have in my Agiflow board?

If Cursor does not show Agiflow

Wrong URL

Copy the connection URL again from Agiflow Settings → Connections and replace YOUR_AGIFLOW_URL.

Sign-in keeps looping

Restart Cursor, open the Agiflow server entry again, and repeat the browser authorization flow.

Wrong board appears

Create a new scoped connection URL in Agiflow for the organization, project, work unit, or task you meant to expose.

Agiflow is not listed

Check the .cursor/mcp.json path and JSON shape, then restart Cursor.

FAQ

Does Cursor connect to Agiflow over remote HTTP MCP?

Yes. The Agiflow setup uses Cursor’s MCP configuration file with an HTTP server entry named agiflow and a url value. Paste the Agiflow connection URL you copied from Settings → Connections into .cursor/mcp.json as YOUR_AGIFLOW_URL, save the file, then restart Cursor.

Can I limit what Cursor can see in my Agiflow board?

Yes. Agiflow connection URLs are scoped before you connect them to Cursor. Choose the organization, project, work unit, or task scope in Agiflow, then copy that connection URL. Cursor only receives the Agiflow context exposed by the URL and authorization you approve for that connection.

Do I need an Agiflow API key, or is browser sign-in enough?

Browser sign-in is the recommended setup path for Cursor. After adding the Agiflow MCP entry, enable it in Cursor and complete the Agiflow browser authorization flow. Agiflow MCP can support Bearer API-key auth generally, but this page follows the shipped Cursor guide unless product docs change.

Why shouldn’t I paste a generic Agiflow endpoint into Cursor?

The Cursor guide uses a scoped connection URL copied from Agiflow, not a fixed public endpoint. A generic endpoint can point Cursor at the wrong surface or omit the intended scope. Use the URL shown in Agiflow Settings → Connections and replace YOUR_AGIFLOW_URL.

Where do I find my Agiflow connection URL?

Log in to Agiflow, open Settings → Connections, choose the scope you want Cursor to use, and copy the URL shown there. Use that value in .cursor/mcp.json, restart Cursor, then enable Agiflow and authorize the connection from the browser prompt.

Build your own Agiflow integration

Agiflow speaks MCP, so any compatible client can connect to the same project context with the right scope and authorization.

Read the MCP docs