Connect while to Cursor in 2026: the command and the authorization
Cursor already writes your code. Connected to while over MCP, it also puts it on while, with its data, and leaves what matters for you to approve. Here is the connection, the authorization, and what Cursor can do next.
By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 19, 2026.
Cursor already writes your code. Connected to while over MCP, it also puts it on while: while builds the code, runs its tests, gives it an HTTPS address, watches it and tells you when it breaks2. The connection takes a minute, and you stay in control of what matters.
The short version. Three lines in the ~/.cursor/mcp.json file are enough. On the first call, while opens a page in your browser: you choose where Cursor acts, one tool or the whole organization, and its level, Read, Read and act, or Administer. What matters, like a production release, then waits for a person’s approval.
The connection at a glance
| The moment | What you do |
|---|---|
| Connect | Three lines of settings, below |
| Authorize | A page in the browser: the tool or the organization, and the level |
| Try without an account | The trial server, named while-essai |
| No browser, in CI | A token in the Authorization header, confirmed with a link |
Step 1: connect while to Cursor
{
"mcpServers": {
"while": { "url": "https://app.while.sh/mcp" }
}
}
To connect every AI tool on your computer at once, while’s install script does the same thing2:
curl -fsSL https://app.while.sh/install.sh | sh
Step 2: authorize Cursor
Ask Cursor for a first action on while. On the first tool call, while opens the authorization page in your browser: you sign in, then choose where Cursor acts, one tool or the whole organization, and its level, Read, Read and act, or Administer2. Then open a new chat in Cursor so while shows up among its tools2.
You, to your AI: Put this tool on while, with its data, and keep it for the team.
What Cursor does next
Over MCP, Cursor puts the tool on while, reads logs and errors, queries the data and rolls back when a version causes trouble2.
- Put the tool on while. Cursor writes the while.yaml file, sends the code, and while builds it, runs its tests and returns the address.
- Understand an error. Cursor reads the logs and the errors grouped in while, finds the cause and fixes it.
- Roll back. If the latest version breaks something, Cursor puts the previous one back.

What waits for your approval
Some actions wait for a person, and Cursor gives you the link. A production release, deleting a database, an outside API or an access: a person in the organization decides. At the Read and act level, an administration action, like adding a person, creating a token or granting a role, is confirmed with one click2. Your AI never approves.
The credentials of your software stay in while, and Cursor never sees them. The details are on our security page, and in connect an API with no credentials in the code.
Without an account: the trial
The trial server, https://app.while.sh/essai, needs no sign-in: the same commands, named while-essai. The tool has its address for a limited time, and Cursor gives you a link to keep it by creating your account2.
Once the tool is on while, keep it for your colleagues with their email account, or share it with a client through a link and a password. The same guides exist for Claude Code, Codex and Gemini CLI.
Try it with Cursor
Give this message to Cursor. The trial is free, with no sign-up, and your tool has its address in 3 minutes.
Read while.sh/agents and help me get started with while.
Sources
- Cursor, Model Context Protocol, accessed November 19, 2026
- while, the page for AI tools, accessed November 19, 2026