Build internal tools with Claude Code, Codex, Cursor, and other coding agents. Deploy them behind your company login.

Tell your agent to deploy. Wirl hosts the app at a link only people at your company can open, with the Google account they already have.

claude mcp add wirl -- npx -y @wirl/mcp
Run this once. The first time you ask your agent to deploy, it shows you a link and a code; approve it in the browser and you are in.

Install once, then ask the agent to deploy. The first time, approve it in the browser. No agent yet? Join the waitlist.

candidate-pipelinebudget-linesspend-requests$1,240$380$95$2,400supplier-paymentsacme--supplier-payments.wirl.runSupplier paymentsNorthwind Freight$4,200PaidKelp & Co$1,180DueSign in with GoogleContinue as PriyaCOMPANYONLYcandidate-pipelinebudget-linesspend-requestssupplier-paymentsacme--supplier-payments.wirl.runSupplier paymentsNorthwind Freight$4,200PaidKelp & Co$1,180DueSign in with GoogleContinue as PriyaCOMPANYONLY

Right now, internal tools live wherever they can.

  • On someone's personal Vercel account, with a Stripe key pasted in.
  • On the intern's laptop, until the intern leaves.
  • In a pull request, waiting for an engineer to find time.
  • On a public URL that was never meant to be public.

Nobody has the list, and nobody knows which of them can read customer data.

  • Someone's personal Vercel
  • The intern's laptop
  • A PR waiting on an engineer
  • Public by accident

Point the agent at Wirl instead.

Tell your coding agent to deploy. Wirl does the rest.

  1. Install Wirl in your agent. One command.
  2. Approve it in your browser. The first time only, with a link and a code.
  3. Ask it to deploy. You get a link only your company can open.
codeKTQM-4821app.wirl.devConnect Claude Codeto acme.co?KTQM-4821Same code as your terminal.Approveacme--supplier-payments.wirl.run

Bring your own coding agent.

Wirl is an MCP server. Any agent your people already use can deploy to it.

Connect yours
  • Claude Code
    One command, shown above.
  • Codex
    Three lines in config.toml.
  • Cursor
    mcp.json, or one click.
  • Anything with MCP
    Same server, any client.
  • No MCP needed
    npx wirl skill writes a skill file.

What you don't have to build.

Every app on Wirl gets these. Nobody has to write them.

Your company's Google sign-in, on every app.

One work Google sign-in and your whole company is in. The first person creates its space.

Sign in with GoogleChoose an accountto continue to supplier-paymentsPriya Nairpriya@acme.coTom Abaratom@acme.coUse another accountNo invites

Company-only by default.

The builder can narrow it to named people, or open it up.

acme--supplier-payments.wirl.runOnly peopleat acme.cocan open this.alex@gmail.comWho can opensupplier-payments?Everyone at acme.co+209Only these peopleAnyone with the link

Keys go into a vault.

A person types each key into their own browser, straight into Wirl's vault. Never into the code, never through the agent.

pay.tsnew Stripe(env.STRIPE_KEY)// no key in hereapp.wirl.devKeys · supplier-paymentsSTRIPE_KEYSave to vaultAGENTNEVERSEES ITSaved to vault

Bad deploys undo themselves.

A deploy that fails in its first half hour goes back to the last healthy version, and the log says so.

v3Supplier paymentsv4Supplier payments5005 failures in 12 minROLLED BACKLive
09:41 wirl rolled supplier-payments back to v3

Share the link or the code.

Anyone who can open an app can pull its source, change it, and ship it again.

$ npx wirl pull supplier-payments

Same thing on your laptop. npx wirl dev gives you the same identity headers and API access locally as in production.

acme--supplier-payments.wirl.runPriyaCopy linkCopied!Tom's laptop$ npx wirl pull supplier-payments✓ pulled v4$ npx wirl devv5Supplier paymentsExport CSV

Admins get the complete view.

Every internal app on one screen.

  • Who built it, and with which agent.
  • What data it connects to.
  • Who can open it.
  • When it was last used.
  • Every call it makes, logged by host.

Questions people ask.

What is Wirl?

A place to host the internal tools your people build, behind your company's Google sign-in by default.

Does it work with AI coding agents?

Yes. Claude Code, Codex, Cursor, anything that speaks MCP.

Who can open an app?

Everyone at your company, unless the builder narrows it to named people or makes it public.

What does the log record?

Who deployed, shared, opened, was refused, changed a key, or was removed, and what each app called, by host. Never request contents, never a key.

Is it a Vercel replacement?

For internal tools, yes. Vercel is still for the site you show the world.

When can I use it?

Private beta now. Connect your agent and deploy something, or leave your email.

Let your people build.

Private beta. Leave your email and we'll get you in.

Private beta. No spam, no drip campaign.