Guides to build, share and keep your tools running
Each guide shows what you ask your AI, and what it does with while.
Connect your AI
- Connect while to Claude, on the web or in the app, over MCP
Claude already writes your pages and small tools in the conversation. Connected to while with a connector, it also deploys them, with their database, without leaving the conversation.
- Connect while to ChatGPT over MCP, to deploy your apps
ChatGPT already writes your tools in the conversation. Connected to while over MCP, it also deploys them, with their database, and asks for your approval on what matters.
- Connect while to Mistral Vibe, formerly Le Chat, in 2026
Mistral’s Le Chat is now called Vibe. Connected to while through an MCP connector, it puts the tools it builds in the conversation on while, with their data, and leaves what matters for you to approve. Here is the connection, step by step.
- Connect while to Claude Code in 2026: the command and the authorization
Claude Code 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 Claude Code can do next.
- 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.
- Connect while to Codex in 2026: the command and the authorization
Codex 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 Codex can do next.
- Connect while to Gemini CLI in 2026: the command and the authorization
Gemini CLI 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 Gemini CLI can do next.
Share a tool
- How to share a Claude artifact with your colleagues, even without a Claude account (2026)
Claude just built you a useful artifact: a calculator, a schedule, a small form. To make it serve the whole team, there are two paths, and the right one depends on your colleagues: do they all have a Claude account, or does it need to be shared without one.
- Move a tool out of Lovable and share it elsewhere, with its data (2026)
Your tool was born in Lovable, and now the whole team uses it. Keeping it elsewhere requires neither rebuilding it nor knowing how to code: its code leaves through GitHub, and your AI handles the rest. Here is the path, data included.
- Move a tool out of Bolt and share it elsewhere, with its data (2026)
Your tool was born in Bolt, and now the whole team uses it. Keeping it elsewhere requires neither rebuilding it nor knowing how to code: its code leaves through GitHub, and your AI handles the rest. Here is the path, data included.
- Move a tool out of v0 and share it elsewhere, with its data (2026)
Your tool was born in v0, and now the whole team uses it. Keeping it elsewhere requires neither rebuilding it nor knowing how to code: v0 already pushes its code to GitHub, and your AI handles the rest. Here is the path, data included.
- Put your company’s logo and colors on the tools you built with AI (2026)
A tool the team recognizes at first glance earns trust, and a client takes it seriously. On while, your logo, your color and everyone’s photo go on every tool your AI built, without touching their code. Here is how to set them, and where they appear.
- Put your app on your own domain name, over HTTPS, with your AI (2026)
Your app runs on its while.sh address, and you want it on yours. Ask your AI: it declares the domain, gives you the DNS records to add, and the HTTPS certificate follows.
Choose who uses it
- Restrict a tool built with AI to your colleagues, with Google Workspace or Microsoft 365 (2026)
Your AI built you a useful tool, and it must serve your colleagues only: a leave tracker, a sales board, an internal directory. With while, they use it with their email account, Google Workspace or Microsoft 365, with no extra account and no sign-in page to write.
- Give a client access to a tool with a link and a password, no account needed (2026)
Your client needs to track their orders, approve a quote or check their dashboard. No way you are creating an account for them, or opening the tool to everyone. With while, a link, a password and a duration are enough, and your AI sets it all up without ever seeing the password.
Connect your software
- Connect Stripe, Brevo or any API to your app with no credential in the code (2026)
An API key in the code always ends up leaking: in a repository, a log, a conversation with your AI. With while, your app calls Stripe or Brevo without ever holding the key, and every call is recorded.
- Call Claude, GPT or Mistral from your app without exposing the API key (2026)
Your app talks to an AI model, and its key costs a lot if it leaks. With while, your app calls Claude, GPT or Mistral without ever holding the key, every call is recorded, and your AI connects it all over MCP.
Keep the tool running
- Run a script at a set time with your AI, with no server (2026)
A report every morning, an import every night? Tell your AI the time: connected to while over MCP, it schedules your script, and you always know whether it ran.
- Roll back to the previous version in one second, with your AI (2026)
A new version breaks your app: ask your AI to roll back, and the previous version takes the traffic again in a second. Then your AI reads the error, fixes it and deploys again.
- Restore your PostgreSQL database to a precise moment, or from a pg_dump (2026)
A failed migration, a table emptied by mistake: your database goes back to the moment before, with a simple request to your AI. A safety backup is taken first, and in production, nothing happens without your approval.
- See every new version before production, like a staging environment (2026)
You want to see a version before it reaches production. Your AI opens a preview of every version, at its own address, with its own databases. It removes it after 24 hours, or after the time you set. Your colleagues point out what’s wrong, right on the page.
- Track your app’s errors with a Sentry SDK, with no Sentry account (2026)
Your app crashes, and you find out from a customer. With while, its errors arrive through a Sentry SDK, with no Sentry account to open, and a never-seen-before error alerts your AI, which reads the stack trace and fixes it.
- Your app’s environment variables and secrets, out of the code (2026)
A key in the code or in a .env file ends up leaking. On while, your AI sets your app’s variables over MCP, and your secrets live in an encrypted vault: your app receives them, and your AI cannot read them back.
For developers: a framework, an API or a container
- Deploy a Next.js app with your AI, over MCP (2026)
Your AI wrote your Next.js app. Connected to while over MCP, it also deploys it, over HTTPS, and you choose who can open it: everyone, your customers or your colleagues.
- Deploy a React app built with Vite with your AI, over MCP (2026)
Your AI wrote your React app with Vite. Connected to while over MCP, it also deploys it, over HTTPS and in France, and every page opens from its link, even after a reload.
- Deploy a Nuxt app with your AI, over MCP (2026)
Your AI wrote your Nuxt app. Connected to while over MCP, it deploys it too, over HTTPS, and you choose who can open it.
- Deploy a SvelteKit app with your AI, over MCP (2026)
Your AI wrote your SvelteKit app. Connected to while over MCP, it also deploys it, over HTTPS and in France, with its forms and its server routes, and without a Dockerfile.
- Deploy an Astro site with server rendering with your AI, over MCP (2026)
Your Astro site renders some pages on demand. Connected to while over MCP, your AI deploys it in France with the Node adapter, without a Dockerfile, and you choose who can open it.
- Deploy a NestJS API with your AI, over MCP (2026)
Your AI wrote your NestJS API. Connected to while over MCP, it also deploys it, over HTTPS, without touching its code.
- Deploy a Django app and its PostgreSQL database with your AI, over MCP (2026)
Your AI knows Django inside out. Connected to while over MCP, it also deploys your app, with its PostgreSQL database backed up every day, in France, with no Dockerfile or server to manage.
- Deploy a Flask app with your AI, over MCP (2026)
Your Flask app runs locally. Connected to while over MCP, your AI deploys it in France, served by gunicorn rather than the development server, with its PostgreSQL database backed up every day.
- Deploy a Streamlit app with your AI, over MCP (2026)
Your Streamlit dashboard runs on your laptop. Connected to while over MCP, your AI deploys it in France, and your colleagues sign in with the company account.
- Deploy a Ruby on Rails app and its PostgreSQL database with your AI, over MCP (2026)
Your Rails app is leaving Heroku, or never went there. Connected to while over MCP, your AI deploys it in France, with its PostgreSQL database backed up every day and a ready-made Rails Dockerfile.
- Deploy a Laravel app and its PostgreSQL database with your AI, over MCP (2026)
Your AI already knows how to write Laravel. Connected to while over MCP, it also deploys your app, in France, with its PostgreSQL database backed up every day and a Laravel Dockerfile ready to go.
- Deploy a static site with Astro, Vite or HTML with your AI, over MCP (2026)
Is your site ready? Connected to while over MCP, your AI builds it and deploys it, over HTTPS, on your own domain if you want.
- Deploy a Spring Boot app with your AI, over MCP (2026)
Your Spring Boot app runs locally. Connected to while over MCP, your AI deploys it in France, with its PostgreSQL database backed up every day, and a ready-made Java Dockerfile, for Maven or Gradle.
- Deploy an ASP.NET Core app with your AI, over MCP (2026)
Your ASP.NET Core API or app is ready. Connected to while over MCP, your AI deploys it in France, with a ready-made .NET Dockerfile and its PostgreSQL database backed up every day.
- Deploy a Docker container with your AI, over MCP (2026)
Does your project have a Dockerfile? Connected to while over MCP, your AI deploys it as is, over HTTPS, whatever the language.
- Host a Discord bot 24/7 with your AI, over MCP (2026)
Does your bot work on your computer? Connected to while over MCP, your AI keeps it running 24/7, and the bot restarts on its own if it stops.
- Deploy a Node.js API and its PostgreSQL database with your AI, over MCP (2026)
Your AI already knows how to write your Node.js API. Connected to while over MCP, it deploys it too, with its PostgreSQL database backed up every day, and you never touch a server.
- Deploy a FastAPI API with your AI, over MCP (2026)
Your AI wrote your FastAPI API. Connected to while over MCP, it also deploys it, over HTTPS, with no Dockerfile or nginx to configure.
- Deploy a Go API with your AI, over MCP (2026)
Your AI wrote your Go API. Connected to while over MCP, it deploys it too, over HTTPS, with no server to maintain and no nginx to configure.
- Deploy a Rust API with your AI, over MCP (2026)
Your Rust API compiles. Connected to while over MCP, your AI deploys it in France, with a Dockerfile ready to go: built in release mode, run in a minimal image, without admin rights.
For developers: leave another host
- Leave Heroku without rewriting your app, with your AI (2026)
Is your Heroku bill climbing? Connected to while over MCP, your AI takes your app as it is, copies your database, and deploys it in France.
- Leave Vercel without rewriting your Next.js app, with your AI (2026)
Is your Vercel bill climbing, or does your data have to stay in France? Connected to while over MCP, your AI takes your Next.js app as it is, with its database and its jobs, and deploys it in France.
- Leave Render without rewriting your app, with your AI (2026)
Your customers want their data in France, or you want your AI to deploy for you? Connected to while over MCP, it takes over your Render app as is, copies the database and deploys it.
- Leave Railway without rewriting your app, with your AI (2026)
Your customers want their data in France, or you want your AI to deploy for you? Connected to while over MCP, it takes over your Railway app as is, copies the database and deploys it.
- Leave Fly.io without rewriting your app, with your AI (2026)
Your customers want their data in France, or you want your AI to deploy for you? Connected to while over MCP, it takes over your Fly.io app as is, copies the database and deploys it.
For developers: host open-source software
- Self-host n8n in France, with its PostgreSQL database, with your AI (2026)
Self-hosted n8n, with no server to maintain. Connected to while over MCP, your AI deploys your instance in France, with its workflows in a PostgreSQL database backed up every day and its webhooks over HTTPS.
- Self-host Metabase in France, with its PostgreSQL database, with your AI (2026)
Your dashboards deserve better than a forgotten server. Connected to while over MCP, your AI deploys Metabase in France, with its settings in a PostgreSQL database backed up every day, and private to your colleagues if you want.
- Self-host NocoDB in France, with its PostgreSQL database, with your AI (2026)
An Airtable alternative of your own, hosted in France. Connected to while over MCP, your AI deploys NocoDB, with your tables in a PostgreSQL database backed up every day.
- Self-host Directus in France, with its PostgreSQL database, with your AI (2026)
A back office and an API for your content, with no server to maintain. Connected to while over MCP, your AI deploys Directus in France, with its content in a PostgreSQL database backed up every day.
- Deploy Strapi and its PostgreSQL database with your AI, over MCP (2026)
Your Strapi runs locally. Connected to while over MCP, your AI deploys it in France without a Dockerfile, with its PostgreSQL database backed up every day and your media kept safe in a bucket.
For developers: data and background jobs
- PostgreSQL behind PgBouncer: Prisma, Django, Rails and your migrations (2026)
Your PostgreSQL database on while goes through PgBouncer, to handle hundreds of clients at once. Your AI knows what that changes for your code, and sets it up for you.
- Add a Redis-compatible cache to your app with your AI (2026)
Is your app slowing down under load? Ask your AI for a cache: connected to while over MCP, it declares one in three lines, and your app finds it in REDIS_URL.
- Store your app’s files in an S3 bucket, with your AI (2026)
Do your users upload photos or PDFs? Ask your AI for a bucket: connected to while over MCP, it declares it in two lines, and your app connects to it with the AWS SDK.
- Run a background worker with BullMQ, Celery or Sidekiq, with your AI (2026)
Sending emails, running exports and heavy processing don’t belong in your requests. Connected to while over MCP, your AI deploys the worker that handles them in the background, with its queue.
- AI acceptable use policy for a small business: the template to adapt in 2026
Your employees already use AI, and some already turn it into real tools. A one-page policy is enough to say what is allowed, what is not, and where the tools go. Here is a template in six rules, to adapt to your company.
- Book your small business rooms and vehicles with Claude or ChatGPT (2026)
In a small business, the meeting room and the vehicles are often booked on a whiteboard, a shared calendar or by word of mouth, and two people end up wanting the same car on the same morning. Your AI can build you a simple booking tool, with no double booking and what to record on return. Here is how.
- Build a PTO and vacation tracker for your small business with Claude or ChatGPT (2026)
Time off in a small business often goes through emails, a spreadsheet and a shared calendar nobody quite keeps up to date. Your AI can build you a tool that brings it all together: the request, the approval, the team calendar and the summary for payroll. Here is how.
- Build a quote tracker for your small business with Claude or ChatGPT (2026)
A quote sent and never followed up is a sale lost without a sound. In many small businesses, quote tracking lives in an inbox and a spreadsheet. Your AI can build you a tool that tracks every quote, reminds you of follow-ups and shows what was signed. Here is how.
- Build a simple CRM for your small business with Claude or ChatGPT (2026)
Many small businesses track their clients in a spreadsheet, rather than pay for a full CRM for every salesperson. Your AI can now build you a custom one that tracks exactly what you track. Here is how to describe it, bring in your contacts, and share it with the team.
- Build a small business inventory tracker with low stock alerts using Claude or ChatGPT (2026)
A small business’s inventory often lives in a spreadsheet updated whenever someone remembers. The day an item runs out, nobody saw it coming. Your AI can build you an inventory tool that tracks stock in and out, and warns you in time. Here is how.
- Build an expense tracker for your small business with Claude or ChatGPT (2026)
A small business’s expense reports often arrive in a mess: crumpled receipts, a spreadsheet to fill in, and a month-end spent reconciling everything. Your AI can build you a tool where everyone photographs their receipt, the manager approves, and accounting exports it all. Here is how.
- Build your small business cash flow forecast with Claude or ChatGPT (2026)
A small business’s cash flow forecast often lives in a spreadsheet only the owner opens, updated whenever they think of it. Your AI can build you a tool that starts from the real bank balance, adds the invoices to collect and to pay, and warns you before a low point. Here is how.
- Build your small business management dashboard with Claude or ChatGPT (2026)
A small business owner’s dashboard is often rebuilt by hand on Sunday night, from three pieces of software and a spreadsheet. Your AI can build you a tool that reads your numbers where they live, puts them on a single page and sends you the Monday summary. Here is how.
- Build your workshop production schedule with Claude or ChatGPT (2026)
A workshop schedule often lives on a whiteboard, photographed on Monday and out of date by Tuesday. Your AI can build you a schedule that says who does what, on which machine, and that everyone checks on their phone. Here is how.
- Connect Airtable to a tool built with Claude or ChatGPT (2026)
Your team lives in Airtable, and your tool built with Claude needs to read or update its tables. The Airtable token acts as your own account, and it must end up neither in the code nor in the conversation. On while, it stays in while, and your AI never sees it. Here is how.
- Connect Axonaut to a tool built with Claude or ChatGPT (2026)
Your small business manages customers, quotes and invoices in Axonaut, and your tool built with Claude needs to use them. The Axonaut credential opens the management of the whole company, and it must end up neither in the code nor in the conversation. On while, it stays in while, and your AI never sees it. Here is how.
- Connect Brevo to a tool built with Claude or ChatGPT (2026)
Your tool built with Claude needs to add contacts to Brevo, or send an email when a quote goes out. The Brevo credential opens your whole email marketing account, and it must end up neither in the code nor in the conversation. On while, it stays in while, and your AI never sees it. Here is how.
- Connect Google Sheets to a tool built with Claude or ChatGPT (2026)
Your tool built with Claude needs to read or fill in a Google Sheet the team already knows. The usual path goes through a service account and a credentials file, which you should never paste into the code or the conversation. On while, it stays in while. Here is how.
- Connect HubSpot to a tool built with Claude or ChatGPT (2026)
Your tool built with Claude needs to read HubSpot contacts or deals. The classic risk is pasting the HubSpot credential into the code or the conversation. On while, it stays in while, and your AI never sees it. Here is how, with the service keys that replace private apps.
- Connect Mailchimp to a tool built with Claude or ChatGPT (2026)
Your tool built with Claude needs to add trade show sign-ups to your Mailchimp audience, or show the results of the last campaign. The Mailchimp credential opens your whole account, and it must end up neither in the code nor in the conversation. On while, it stays in while, and your AI never sees it. Here is how.
- Connect monday.com to a tool built with Claude or ChatGPT (2026)
Your team tracks its projects in monday.com, and your tool built with Claude needs to read or update its boards. The monday.com token has exactly your permissions, and it must end up neither in the code nor in the conversation. On while, it stays in while, and your AI never sees it. Here is how.
- Connect Notion to a tool built with Claude or ChatGPT (2026)
Your procedures, client records or task lists live in Notion, and your tool built with Claude needs to read them. The risk is pasting the Notion credential into the code or the conversation. On while, it stays in while, and your AI never sees it. Here is how.
- Connect Pennylane to a tool built with Claude or ChatGPT (2026)
Your tool built with Claude needs to read Pennylane’s invoices to track unpaid bills or cash flow. The Pennylane token opens the company’s accounting, and it must end up neither in the code nor in the conversation. On while, it stays in while, and your AI never sees it. Here is how.
- Connect Pipedrive to a tool built with Claude or ChatGPT (2026)
Your sales team lives in Pipedrive, and your tool built with Claude needs to read deals or add contacts. The Pipedrive token acts on your behalf across the whole CRM, and it must end up neither in the code nor in the conversation. On while, it stays in while, and your AI never sees it. Here is how.
- Connect Qonto to a tool built with Claude or ChatGPT (2026)
Your tool built with Claude needs to read Qonto’s transactions to track cash flow, or prepare quotes and invoices there. The Qonto secret opens the company’s accounts, and it must end up neither in the code nor in the conversation. On while, it stays in while, and your AI never sees it. Here is how.
- Connect Slack to a tool built with Claude or ChatGPT (2026)
Your tool built with Claude needs to alert the team in Slack: a signed quote, low stock, a request to approve. The reflex is to paste the Slack token into the code, where it ends up leaking. On while, it stays in while, and your AI never sees it. Here is how, in about ten minutes.
- Connect Stripe to a tool built with Claude or ChatGPT (2026)
Your tool built with Claude needs to read Stripe’s payments: failed charges to follow up, unpaid invoices, the month’s revenue. The Stripe credential touches your customers' money, and it must end up neither in the code nor in the conversation. On while, it stays in while, and your AI never sees it. Here is how.
- Connect Typeform to a tool built with Claude or ChatGPT (2026)
Your customers answer in Typeform, and your tool built with Claude needs to sort their responses, track them and follow up. The Typeform token can read and delete your forms, and it must end up neither in the code nor in the conversation. On while, it stays in while, and your AI never sees it. Here is how.
- Handle your small business purchase requests with Claude or ChatGPT (2026)
A small business’s purchase requests often arrive by email, by message or at the coffee machine, and nobody knows anymore what was approved or ordered. Your AI can build you a tool where everyone makes their request, the right person approves based on the amount, and the order is tracked through to delivery. Here is how.
- Keep GitHub or GitLab as your main repository, and deploy on every push (2026)
Your code stays on GitHub or GitLab. A push to the default branch updates production, every merge request opens a preview whose address arrives as a comment, and every commit gets its status.
- Move a tool out of Replit and share it elsewhere, with its data (2026)
Your tool was born in Replit, and the whole team now uses it. Keeping it elsewhere requires neither rebuilding it nor knowing how to code: its code goes to GitHub, its data follows, and your AI takes care of the rest. Here is the path, data and secrets included.
- Replace a shared Excel file with a tool built with AI, no developer needed (2026)
A shared Excel file is often a small business’s first internal tool: the quote tracker, the schedule, the stock list. It works while the team is small, then overwritten rows and duplicate versions pile up. Here is when to replace it, and how to do it with your AI, without a developer.
- Run your small business employee onboarding with Claude or ChatGPT (2026)
A new hire’s arrival in a small business often depends on someone’s memory: the laptop ordered in time, the accounts set up, the mentor told. Your AI can build you a tool that prepares the arrival, guides the newcomer week after week and reminds everyone of what they have to do. Here is how.
- Run your small business performance reviews with Claude or ChatGPT (2026)
A small business’s annual reviews often live in a Word document copied for each person, sent by email and filed who knows where. Your AI can build you a tool where each employee prepares their review, the manager completes it, and HR tracks the cycle. Here is how.
- Shadow AI: govern the tools your employees build with ChatGPT or Claude (2026)
Your employees use ChatGPT or Claude, often with their own account, and some already turn them into real tools: a calculator, a tracker, a small client portal. Banning them pushes them further into the shadows, and ignoring them leaves your data anywhere. Here is how to govern them while keeping what works.
- 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.
- 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.
- Stop every team from building its AI tools on its own (2026)
Sales built its quote calculator, the workshop its schedule, accounting its expense tracker, each with its own AI and on its own. Six months later, nobody knows which tools exist, or who uses them. Here is how to bring them together, without slowing down the people who build.
- Track your small business customer orders with Claude or ChatGPT (2026)
A small business’s orders are often tracked in a spreadsheet, emails and the memory of whoever took them. The day a customer calls to ask where theirs stands, someone has to go looking. Your AI can build you a tool where each order has its status, visible to the whole team, and the customer is kept informed. Here is how.
- Track your small business equipment loans with Claude or ChatGPT (2026)
In a small business, loaned equipment is often tracked in a notebook or from memory: the drill, the spare laptop, the measuring device. Your AI can build you a tool that says who has what, since when, and sends a reminder when a return is late. Here is how.
- Track your small business field service jobs with Claude or ChatGPT (2026)
A small business’s field jobs are often tracked with a spreadsheet schedule, calls to the technician and paper job sheets typed up in the evening. Your AI can build you a tool where the technician sees their day on their phone, takes photos, gets the customer to sign, and the report goes out on its own. Here is how.
- What to do with your custom GPTs before they retire on December 11, 2026
On December 11, 2026, OpenAI retires custom GPTs and replaces them with plugins. We read closely what the move keeps and what it leaves behind, and the answer mostly depends on one thing: whether your GPT serves you alone or a whole team.
Give your AI the message, and it takes care of the rest
Give this to your AI
Read while.sh/agents and help me get started with while.
Copy the messageIn 3 minutes, with no sign-up, the tool has its own address. To keep it, create your account.
For a company project, write to the while team: hello@while.sh