How Google processes data
Necessary

Remember the site's theme and your choice in this window, in this browser's storage. Cloudflare's protective cookies protect the site from bots. Always on.

Google Analytics (Google Ireland Limited) counts visits and shows which sites and campaigns they come from. Cookies: _ga, _ga_*.

Google Ads (Google Ireland Limited) measures whether a visit from an ad ends with a click on the sign-up button. Cookies: _gcl_au and related.

List of cookiesHow Google processes data
Try 30 days free
How it worksTutorialsPricingFAQ
Sign in

Agents and consoles · step 2 of 8

Connect Cursor CLI by signing in through the browser

You connect Cursor CLI with an entry with no secret in Cursor’s file, and confirm the connection by signing in through the browser. On a computer with no browser, use the entry with the secret.

5 minutesreading time
Before you starta featureloom account, a Cursor account, Cursor CLI on a computer with a browser
All the steps in one recording, narrated.
Contents

  1. Copy the entry with no secret

    Open Integrations in the menu. On the Your consoles card, press Connect console and choose Cursor.

    The window shows the Add to Cursor button, but this time you don’t need it. Under step 1, in In the terminal and in Cloud Agents, press Show the entries, and at Terminal (Cursor CLI): entry with no secret press Copy the entry.

    The Connect Cursor window with In the terminal and in Cloud Agents open and the entry with no secret
    Entry with no secret, sign-in in the browser

    If the window first shows Confirm it’s you, confirm the way you sign in. Closing the window removes the unused secret, and a console signed in through the browser stays.

  2. Add the entry to Cursor’s file

    As the same computer user who runs Cursor CLI, open ~/.cursor/mcp.json in your home folder. If it isn’t there, create it with this entry. The entry holds no secret, only the server’s name and address:

    Entry with no secret, ~/.cursor/mcp.json
    {
  "mcpServers": {
    "featureloom": {
      "url": "https://mcp.featureloom.com/mcp"
    }
  }
}

    If the file already lists other servers, add featureloom next to them, inside mcpServers.

  3. Sign in from the terminal

    In a system terminal, go to your project’s folder, not your home folder itself, and run the sign-in command. Cursor CLI opens the featureloom sign-in in the browser on the same computer.

    Terminal
    agent mcp login featureloom

    If featureloom asks, sign in to your account. On the Connect a console screen, you see what the console will be able to do in the organization: it has the same rights as you. If you belong to more than one organization, first choose the one to connect it to. Press Connect.

    The Connect a console screen: consent connects Cursor to your account as your console, this console’s rights in the organization and the Decline and Connect buttons
    The console gets your rights

    If you see Confirm it’s you after pressing Connect, enter your password and, with two-step sign-in, the code from your app too. featureloom asks when your session hasn’t been confirmed in the last hour.

    On a remote computer you reach over SSH, no browser opens. There, use the entry with the secret, as in the tutorial Connect Cursor with a secret.

  4. Check the connection

    Check the connection in the system terminal, in the same project folder. Cursor CLI shows featureloom in its list of servers, with the state of its connection. If Cursor CLI suggests running the command again, skip that and check the connection right away.

    Terminal
    agent mcp list
featureloom: ready

    In the app, on the Your consoles card, you see the new Cursor console marked signed in through the browser.

    The Your consoles card with the console Cursor, its line Cursor · signed in through the browser and the state Live
    The new console, signed in through the browser

  5. Give your console a plan

    Start Cursor CLI with agent in the folder you work in. Open a plan with a prompt, copy the command under its contents, in Command for a console, and paste it in Cursor CLI. For plan INV-14 the command is:

    Cursor CLI
    featureloom realizer INV-14

    The agent reads the plan, realizes it and reports that on the board.

Good to know

  • In your home folder itself, Cursor CLI reads ~/.cursor/mcp.json as a project’s file and shows not loaded (needs approval). Any folder under your home folder will do.
  • Cursor CLI keeps a sign-in per folder. In another folder, agent mcp list shows requires_authentication: sign in there with the same command.
  • Cursor CLI waits 15 minutes for your consent in the browser. After that it says Timed out waiting for the OAuth callback: run the sign-in command again.
  • The Cursor editor and Cursor CLI are two separate consoles, so the Your consoles card shows two Cursor rows.
  • Cursor CLI uses the same MCP server settings as the Cursor editor.
  • A sign-in lasts 90 days from your consent, and ends sooner if the console doesn’t work for 30 days.
  • You have up to 10 consoles at once, those connected by signing in included. When you run out of room, featureloom disconnects the one you haven’t used for the longest time.
  • You connect the Cursor editor with one button. The tutorial Connect the Cursor editor with one button shows how.
  • The Cursor integration page shows how Cursor works with your board and what it may do.

Updated: November 8, 2026

Next

Role prompts: your team’s process as console commands

Your console is connected: write your team’s rules as prompts it fetches with one command.

See the tutorial