Share a tool built with ChatGPT with your team, without being a developer (2026)
ChatGPT helped you build a tool, and you want your colleagues to use it, without each of them needing a ChatGPT account. The path depends on your plan, and for Plus or Pro, it goes through Codex and a GitHub repository. Here are the steps, one by one.
By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 18, 2026.
ChatGPT is an excellent workshop: in a few exchanges, it helps you build a quote tracker, a stock board or a request form. Making it serve your colleagues is another story, especially if they do not all have a ChatGPT account. This guide shows the path that works today, depending on your plan.
The short version. With ChatGPT Business or Enterprise, an admin adds while in ChatGPT, and you are done. With Plus or Pro, Codex puts the tool on while through a GitHub repository: you try each version before approving it, and your colleagues use it with no ChatGPT account.
Your plan decides the path
| Your ChatGPT plan | The path |
|---|---|
| Business, Enterprise or Edu | An admin adds while as an MCP server, and ChatGPT puts the tool on while from the conversation |
| Plus or Pro | Codex builds the tool in a GitHub repository linked to while, and each approved version is made available |
Adding your own MCP server in ChatGPT is limited to the Business, Enterprise and Edu plans, and on Business to workspace admins1. For the Plus and Pro plans, Codex, included in the subscription, makes the link through GitHub2.
With Plus or Pro: the Codex path, in five steps

- Create the tool in while. In the console, open Tools, then New tool: a name, an address, and the tool exists. The Free plan is enough to start.
- Link a GitHub repository to the tool. Create an empty repository on GitHub, then, in the tool’s settings, under Code and budget, choose Link a repository. Paste the repository and a GitHub token limited to it, and the page tells you which permissions to give it. See keeping GitHub as your main repository.
- Ask Codex for the tool. On chatgpt.com/codex, connect your GitHub account, choose the repository, and describe the tool, or paste what ChatGPT already built. Codex writes the code and opens a pull request.
- Try the new version. while builds the pull request and turns it into a preview, whose address arrives as a comment on GitHub. You use it to try it.
- Approve. You merge the pull request on GitHub, and while makes the new version available to the people who use it.
You, to your AI: Build a quote tracker in this repository, and read while.sh/agents first so it works on while.
From then on, each improvement follows the same path: you ask Codex, you try it, you approve it.
With Business or Enterprise: adding while in ChatGPT
In a Business or Enterprise workspace, an admin adds while from Plugins, with the plus button, then Add custom MCP server, at https://app.while.sh/mcp1. ChatGPT then puts the tool on while itself, from the conversation, with no repository and no Codex.
Choosing who uses the tool
In both cases, you choose who uses it, and nobody needs ChatGPT:
- 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.
- A client or a supplier. They use the tool with an access link and a password, valid for 1, 7 or 30 days.
- Everyone. A person on your team approves opening it first.
The tool keeps its data, backed up every day, and the credentials for your other software stay in while, out of ChatGPT’s reach. Your tools are hosted in France by Nextmap. To compare with ChatGPT Sites, which keeps the tool inside ChatGPT, read ChatGPT Sites or while, and if your custom GPTs worked as tools, what to do with them before December 11, 2026.
Try it
To try while without an account, give this message to an AI that connects to while, like Claude or Codex. 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.
In the docs: Previews.
Sources
- OpenAI, Connecting custom MCP servers in ChatGPT, accessed November 18, 2026
- OpenAI, Introducing Codex, accessed November 18, 2026