This page connects Cursor to your fline account, so its AI can put your app online for you. You add a few lines to a settings file, then approve fline in your browser.

Setup steps, not yet tested from start to finish. Claude Code is the only AI coding app we've used with fline all the way to a live app. These steps match what your fline dashboard shows for Cursor, but we haven't followed them through to a live app ourselves. If you get stuck, Claude Code is the tested way.

Before you start

Your fline account is open, and you've opened your fline dashboard once. If not, see Getting your account. Connect after your account is open, or Cursor may keep asking you to sign in.
Your project is open in Cursor.

1. Add fline to Cursor's settings file

Cursor keeps its connections in a settings file called mcp.json. You can put fline in one of two places:

For every project: the file mcp.json in the .cursor folder of your home folder (~/.cursor/mcp.json on a Mac, %USERPROFILE%\.cursor\mcp.json on Windows). This is the one your dashboard shows.
For this project only: create a folder named .cursor at the top of your project folder, and a file named mcp.json inside it. You can do both from Cursor's file list.

Put these lines in the file. Your dashboard shows the same lines under Cursor, with a button to copy them:

{
  "mcpServers": {
    "fline": {
      "url": "https://mcp.dev.fline.sh/mcp"
    }
  }
}

If the file already has other connections in it, don't paste a second copy of the outer brackets. Add only the "fline": { ... } part inside the existing "mcpServers" list, with a comma between it and the entry before it.

Save the file.

Open Cursor's settings and go to the section for MCP. Find fline in the list and follow its prompt to log in. Your browser opens.

Cursor moves its menus from time to time. If you can't find the section, search Cursor's settings for "MCP".

3. Approve fline in your browser

If you're not signed in to fline in that browser, you see the fline sign-in page first. Sign in with your fline email address and password.

Then you see a page that asks you to approve the connection. It looks plainer than the rest of fline, and that's expected. At the top is the name the app gave itself when it connected. Only approve if you started this from Cursor a moment ago.

Make sure every permission box is ticked, then press Allow. Cursor gets only the permissions you tick, and it needs all of them to put your app online.

Code on the page	What it lets Cursor do
`openid`	Confirm which fline account you signed in with.
`offline_access`	Stay connected, so you don't have to approve fline again every time you use it.
`project:read`	See your projects: their progress, their link, what went wrong, what your app printed, what it uses, and the names of the passwords and keys your app uses (never their values).
`project:write`	Create and delete projects, send your project folder to fline, answer fline's questions about your app, give you the link to the private page where you type keys, save a key it already has, and create, pause, resume or delete a database.
`deploy`	Put your app online, restart it, and put an earlier version back.
`domain:write`	Attach a web address you own to your project, check it, and remove it.

No permission lets Cursor read a saved password or key back.

4. Check that it worked

In Cursor's AI chat, ask:

Paste this into Cursor

List my projects on fline.

If it says you have none, the connection works. Then ask it to put your project online. Put your app online walks through what happens next. It's written for Claude Code, and the steps are the same.

If something goes wrong

fline doesn't appear in Cursor's list. Check that the file is named mcp.json, sits in a folder named .cursor, and that every bracket and quote mark from the lines above is there. Restart Cursor.
Cursor keeps asking you to sign in to fline. Open your fline dashboard. If it says "You're on the list", your account isn't open yet.

Disconnect Cursor

On your fline dashboard, open Agents. Each connected AI app is listed with a button to disconnect it. Your app keeps running.

Next: Put your app online