wirldocs
The wirl npm package is not published yet, so the npx wirl … commands on these pages will not run today. Until it ships, connect your agent to the hosted endpoint: the first command in the Quickstart.

Quickstart

Connect an agent, or sign in yourself, then build, run, deploy and share.

Connect an agent#

If your agent speaks MCP over HTTP, run this once:

claude mcp add --transport http wirl https://app.wirl.dev/mcp

It opens your browser to sign in. If your agent only supports local MCP servers, run this instead:

claude mcp add wirl -- npx -y @wirl/mcp

Either way, the first time you ask the agent to deploy something it signs in, shows you a link and a code, and carries on once you approve.

With no agent at all, sign in from the terminal:

npx wirl login

It prints a link and a short code. Approve the code in the browser and the terminal is signed in — there is nothing to copy back.

Build something#

Scaffold a server-backed app:

npx wirl init my-tool --server

This writes a wirl.json and a working server.mjs. Run it locally:

cd my-tool
npx wirl dev

wirl dev runs the same bundle a deploy would, signed in as a stub user.

Deploy it#

npx wirl deploy

This builds, scans and deploys the directory, creating the app if it is new, and prints its URL. The app is private until you share it.

Share it#

npx wirl share dana@acme.test

That person can now open the app. Add --role editor if they should be able to deploy it too.

What you see#

Anyone who signs in at app.wirl.dev sees a hub listing the apps they can open. Each deployed app also gets its own address on wirl.run — for example https://acme--churn-dashboard.wirl.run — which is the link you actually share.

Need it to run itself on a timer? See Schedules. Need Slack, Stripe or GitHub to reach it? See Public paths.