---
title: "Share a tool built with Cursor with your team (MCP server, 2026)"
url: https://while.sh/en/guides/share-cursor-tool-with-team/
author: "Aloïs Oddon, co-founder of Nextmap"
updated: 2026-11-18
---

# Share a tool built with Cursor with your team, through while's MCP server (2026)

Your tool runs in Cursor, and your colleagues in sales or accounting could use it. They do not have Cursor, and do not want it. Here is how Cursor puts it on while in one request, so they use it in their browser.

Cursor is where your tool takes shape, but it is also where it stays. Your colleagues in sales, accounting or at the front desk do not have Cursor, and have no reason to install it. **The good news is that Cursor can put the tool on while itself**, in one request, so they use it in their browser.

> **The short version.** Add while's MCP server to Cursor, ask Cursor to put the tool on while, then choose who uses it. Your colleagues need no Cursor account.

## Why go through while rather than Cursor Apps

Cursor Apps also hosts tools, with their data and sign-in, but **always behind Cursor sign-in**: everyone who uses them goes through a Cursor account, and only individual plans can make a tool public (source 2). For a tool that must serve the whole team, or a client, that is where while makes the difference. We compare the two in detail in [Cursor Apps or while](/en/comparisons/cursor-apps-vs-while-2026/).

## Putting the tool on while, in three steps

<figure class="illus"><img src="/illustrations/cursor-equipe-mcp-1200.webp" srcset="/illustrations/cursor-equipe-mcp-768.webp 768w, /illustrations/cursor-equipe-mcp-1200.webp 1200w" sizes="(min-width: 48rem) 46rem, 100vw" width="1536" height="1024" loading="lazy" decoding="async" alt="Adding while's MCP server to Cursor: the Cursor editor linked to while's server, and the authorization page that opens on the first call to share the tool with the team" /><figcaption>Once while's MCP server is added, Cursor puts the tool on while from your project.</figcaption></figure>

1. **Add while's MCP server to Cursor.** The simplest way is the "Install in Cursor" button on while's GitHub page. Otherwise, add it to Cursor's `~/.cursor/mcp.json` file (source 1):

```json titre="~/.cursor/mcp.json"
{
  "mcpServers": {
    "while": { "url": "https://app.while.sh/mcp" }
  }
}
```

2. **Ask Cursor to put the tool on while.** Without an account, it does so as a free trial, and gives you a link to keep it. With an account, a while page opens in your browser on the first call, to authorize Cursor.

> You, to your AI: Put this tool on while, and restrict it to the team.

3. **Choose who uses it**, once the tool is kept in your account (see below).

### What Cursor does

Cursor describes the tool in a small file, `while.yaml`, at the root of the project: its name, its service, its port and the page that says it is healthy. It then sends the code to while, which builds the tool and gives it its address.

```yaml titre="while.yaml"
apiVersion: while/v1
project: order-tracking
services:
  - name: web
    port: 3000
    health:
      path: /health
```

## Choosing who uses the tool

Once the tool is kept in your account, **you choose who uses it**, and nobody needs Cursor:

- **Only your colleagues.** They sign in with a while account, up to 3 people on the Free plan, or with their email account, Google or Microsoft, on the Pro plan. See [restricting a tool to your colleagues](/en/guides/internal-tool-company-sign-in/).
- **A client or a supplier.** They use the tool with [an access link and a password](/en/guides/share-app-with-password/), valid for 1, 7 or 30 days.
- **Everyone.** A person on your team approves opening it first.

## Keeping the tool alive from Cursor

The tool stays yours, and **you keep improving it in Cursor**: each request can put its new version on while.

- **Your data.** Ask Cursor to keep what people enter in the tool: it adds what is needed to store it in two lines of `while.yaml`, and **while backs it up every day**.
- **Your GitHub repository.** If your code lives on GitHub, [link the repository to the tool](/en/guides/keep-github-gitlab/): each merge to the main branch makes the new version available.
- **Going back.** A version that disappoints is rolled back in a few seconds, and Cursor reads what broke.

The credentials for your other software [stay in while](/en/security/), and Cursor never sees them. Your tools are hosted in France by Nextmap.

## Try it with your tool

To try it, give this message to Cursor. The trial is **free, with no sign-up**, and your tool has its address **in 3 minutes**.

```text titre="The message to give your AI"
Read while.sh/agents and help me get started with while.
```

## Sources

1. [Cursor, Model Context Protocol (MCP)](https://cursor.com/docs/context/mcp), 2026-11-18
2. [Cursor, Build Live Apps in Cursor](https://cursor.com/changelog/build-live-apps), 2026-11-18

## Questions

### Do my colleagues need Cursor?

No. On while, they use the tool in their browser: with a while account for up to 3 people, or with their email account on the Pro plan.

### Do I need a while account to start?

No. Without an account, Cursor puts the tool on while as a free trial. To keep it, you create your account from the link it gives you.

### What about Cursor Apps, Cursor's own feature?

It hosts the tool behind Cursor sign-in: your colleagues then need a Cursor account. Only individual plans can make a tool public (source 2).

### Can I keep my code on GitHub?

Yes. Link the repository to the tool in while: each merge to the main branch makes the new version available.

### Can the tool keep its data?

Yes. Ask Cursor: it adds what is needed to store it in two lines, and while backs it up every day.
