Integration · Cursor
Cursor takes plans from your board.
featureloom connects to Cursor as a remote MCP server. One button in the app adds featureloom to the Cursor editor, and Cursor CLI connects with an entry you copy from the same window. The agent gets your team’s prompt and the whole plan, delivers it and reports on the board, and you accept the work.
MCP server address: https://mcp.featureloom.com/mcp. A console acts with the rights of the person who connected it. Each person has up to 10 consoles at once.
What Cursor gets
The prompt, the plan and what was built before. In one command.
Your organization’s prompts as commands
Your organization’s prompts work as commands in Cursor. The command from a plan, such as featureloom realizer INV-14, gives the agent the prompt with your team’s process, the whole plan document and the documents of the delivered plans it directly depends on.
- You copy the command from the plan, in Command for a console
- The agent takes the next ready plan itself and, when it is missing something, asks in the plan
- Reporting the work moves the card on the board, and you give the verdict
With its person’s rights
A Cursor console acts with the rights of the person who connected it. It always reads, and it delivers, writes and deletes plans only when that person has the right to. The server refuses the rest.
- The tool list in Cursor follows the rights and refreshes when the console reconnects
- Only a person gives the acceptance verdict, in the app
- People set the column and the order of plans on the board
How you start
Three steps to your first plan.
Connect a console in the app
In the app, open Integrations, press Connect console on the Your consoles card, then choose Cursor. In the Connect Cursor window, press Add to Cursor. The button opens Cursor on this computer and carries no secret.
Approve in Cursor and sign in
Cursor asks whether to install the featureloom server: press Install. In Cursor’s list of servers, beside featureloom, press Authenticate: the sign-in opens in the browser. Choose the organization and press Connect. Back in Cursor, featureloom shows how many tools are enabled, and the window in the app shows Connected: Cursor.
Give your console a plan
Open a plan with a prompt and copy the command under its contents, in Command for a console. Paste it in the agent’s chat in Cursor: it reads the plan, delivers it and reports that on the board. For plan INV-14 the command is:
Working in Cursor CLI? The same window gives you an entry for Cursor’s file, with no button.
Tutorial: Connect the Cursor editor with one buttonQuestions about Cursor and featureloom
Does featureloom run Cursor for me?
No. The Cursor editor and Cursor CLI run on your computer. featureloom gives them plans and prompts over MCP and shows their work on the board.
How do I connect Cursor CLI?
In the Connect Cursor window, in In the terminal and in Cloud Agents, press Show the entries. Cursor CLI gets the entry with no secret for ~/.cursor/mcp.json and signs in through the browser with agent mcp login featureloom. On a computer with no browser, use the entry with the secret. The editor and Cursor CLI are two separate consoles, so the Your consoles card shows two Cursor rows. The tutorials Connect Cursor CLI by signing in through the browser and Connect Cursor with a secret show it step by step.
How long does the connection work?
A sign-in through the browser lasts 90 days from your consent, and ends sooner if the console doesn’t work for 30 days. The secret in the entry works for 90 days from issue and expires sooner after 14 days without use. You get a new secret for the same console with Reconnect on the Your consoles card.
Does featureloom work with Claude Code and Codex too?
Yes. You connect Claude Code and Codex with one connect command from the app, and they get the same plans and prompts. The Claude Code integration and Codex integration pages show how.
Give Cursor the plans. Keep the decisions.
30 days free, no payment card needed. You connect Cursor in a few minutes.