This page is for connecting an AI app that doesn't have its own page here. It gives the setup steps your fline dashboard shows for Grok, Antigravity and "Something else", and it says plainly which apps can't put an app on fline yet.

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. Nothing on this page has been followed through to a live app. If you get stuck, Claude Code is the tested way.

What every AI app needs

fline gets your app as a copy of your project folder, packed up and sent by the AI app. So the AI app has to:

run on your computer and be able to open your project folder;
be able to run commands there, to pack the folder and send it;
support remote MCP servers, which is how AI apps connect to services like fline, with a browser sign-in.

The address to connect to is:

https://mcp.dev.fline.sh/mcp

Before you connect, your fline account must be open and you must have opened your fline dashboard once. See Getting your account.

Grok

In Terminal, the app on your computer where you type commands, in your project folder, paste this line and press Return:

grok mcp add --transport http fline https://mcp.dev.fline.sh/mcp

Your browser opens the first time Grok uses fline. If it doesn't, this line checks the setup and the connection:

grok mcp doctor fline

Antigravity

Antigravity keeps its connections in the file ~/.gemini/config/mcp_config.json. In Antigravity you can open it from the agent panel: Manage MCP Servers, then View raw config. Put these lines in it:

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

The word is serverUrl, not url. Antigravity ignores an entry that says url without telling you.

Something else

Most AI apps that connect to remote MCP servers use a settings file with an mcpServers list. Try this first:

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

If your app can only start programs on your computer and can't connect to an address, use this bridge instead. It needs Node.js installed. It runs the same browser sign-in on your computer and passes everything through to fline:

{
  "mcpServers": {
    "fline": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.dev.fline.sh/mcp"]
    }
  }
}

Approving fline in your browser

Whichever app you use, your browser opens. If you're not signed in to fline there, sign in first. Then a plainer page asks you to approve the connection. At the top is the name the app gave itself when it connected: only approve if you started this a moment ago. Make sure every permission box is ticked, then press Allow.

Connect Claude Code has the full list of permissions and what each one lets the app do. No permission lets an app read a saved password or key back. You can disconnect any app from Agents on your fline dashboard, and your app keeps running.

The Claude desktop app

The Claude desktop app has a Chat tab and a Code tab.

The Chat tab can't put an app on fline. It can't pack up a project folder on your computer and send it.
The Code tab is not yet tested with fline.
Adding fline in the Claude app's own settings, as a custom connector with no Terminal, may work, but we haven't tested it, so we don't offer it yet.

The tested way today is Claude Code in your computer's Terminal app. See Connect Claude Code.

ChatGPT, Claude on the web, and app builders

These can't put an app on fline today:

ChatGPT and Claude on the web. A chat in your browser can't reach the project folder on your computer, so it can't send fline your project.
App builders such as Lovable, Bolt, Replit and Base44. They can't send fline a project. Apps made inside a builder often keep their database and sign-in inside that builder, so downloading the code isn't always enough to run it somewhere else. We haven't tested sending a downloaded builder project with Claude Code.

fline also can't take a GitHub link, and there's no upload button on the dashboard yet. If your app was made in one of these, use the publish option in the app you built it in.

Next: Put your app online