local ▸ runs on your machine 0

Give any AI agent an API for any website.

Writ Desktop turns website tasks into local APIs and MCP tools that AI agents can create and call directly - no Writ account required.

Download for macOS Windows Linux
Free · account optional · local REST + MCP · macOS, Windows, and Linux
local ▸ nothing leaves the box 01
01
Local-first

Your data never leaves this machine.

Workflows, logins, cookies, and extracted data live only on your computer. Writ's cloud never sees them - there is nothing to leak.

◍ Your machine · logins · data · AI keys Writ cloud · never sees it
your network nothing opened caller your code · your AI front door api.usewrit.app Writ agent on your laptop

What this required from your firewall: no inbound rule · no public hostname · no port opened

Nothing dials in. The agent holds one outbound connection, and the call rides back down it. There is no inbound rule to write and no port to open.

Your own machine — free, no account, runs while it’s awake; only the result leaves.

The agent dials out. Nothing dials in — a system behind your VPN becomes callable without opening a single inbound port. Local callers can stay entirely local; add Uplink only when a remote caller needs to reach a workflow behind your firewall.

call ▸ local run, cloud trigger 02
02
Cloud-callable

Runs local. Reachable from anywhere.

Connect a cloud account and the cloud relays a schedule, an API call, or an MCP trigger. Your machine runs it; only the result comes back.

✓ schedule ✓ REST ✓ MCP ✓ webhook
ai ▸ agents drive writ 03
03
Agent-native

Your AI agent can create the API itself.

Connect Claude, Cursor, or any MCP-compatible agent directly to Writ Desktop. Without a Writ login, it can record website tasks, create callable APIs and MCP tools, test them, and run them on your machine.

Turn this supplier portal into an API my agent can call...
See how AI agents operate Writ
mcp ▸ agent wired to the app 04
04
your agent, your app

Point your agent at Desktop. Its work lands in the app.

Writ Desktop ships a loopback MCP server. Point Claude, Cursor, or any MCP client at it, and every workflow the agent records or builds is a real object in this app - it appears in Workflows the moment it saves, ready to inspect, edit, replay by hand, schedule, or expose as an API. One workspace, shared by you and your agent; nothing stays hidden inside an agent sandbox.

your ai agent

writ_record_website({
  url:  "supplier.acme.co",
  goal: "check inventory"
})  ✓ saved
MCP · loopback

writ desktop · workflows

Acme Portal · GetOrders
Retail Dashboard · SalesReport
Supplier Dashboard · CheckInventoryjust now
How the MCP server works
engine ▸ everything local 05
05
the full engine

Everything Writ does, on your machine.

Desktop is not a lite client — it is the full engine, and local runs are permanently unmetered. One exception is honest: crawls launch from the app but run on the Writ fleet. Each capability links to its own chapter.

01 Workflows Record once, replay on your machine — offline included 02 Monitors Watch pages on a local cadence, alert from your machine 03 Automations Triggers chained to actions, executed locally 04 Harvest crawl Launch site-wide crawls from the app — runs in Cloud, free account to start 05 Personas & 2FA Credentials sealed on-device; TOTP handled locally 06 Local REST + MCP A loopback API and MCP server any agent can call 07 BYO AI keys Your model, your keys — AI is never proxied through us
run ▸ three ways to run 06
06
runways

Three ways to run the same engine.

Same recorder, step types, API and MCP surfaces. Pick where it runs.

Writ Desktop

This app

A native, account-optional app for your machine. Install it and let any MCP-compatible agent create and call website APIs locally.

  • Free, local-first
  • Data stays on your PC
  • Any MCP-compatible AI agent
  • Link Cloud only for always-on
Download

Self-host

Open core

The same engine on your own server, via one Docker command.

  • Always-on on your infra
  • Your own agent fleet
  • Full API + MCP surfaces
  • You run the ops
Learn more

Managed cloud

Zero ops

We run it. Always-on, metered by running time, scales on demand.

  • Runs when your PC is off
  • Elastic concurrency
  • Always-on managed execution
  • Teams + marketplace
Learn more
ask ▸ answered 07
07
faq

Questions

Is Writ Desktop free?
Yes. Sign in with your free Writ account and run workflows on your own machine at no charge - local runs use no cloud compute. Paid plans add managed, always-on cloud execution. Prefer fully offline? A local-only mode works without an account: everything stays on this machine, with your own AI keys - no cloud, no sync, no marketplace.
Does my data leave my computer?
No. Workflows, recorded steps, credentials, and extracted data live only on your machine. When you connect a cloud account, the cloud relays a trigger and your machine runs it - only the result comes back.
Do I need Docker?
No. Writ Desktop is a native app you install and run. Docker is only for the separate open-core self-host path, which runs the same engine as a server.
Can an AI agent use Writ Desktop directly?
Yes. Connect Claude, Cursor, or any MCP-compatible agent to the local MCP server. It can create, test, expose, and call website APIs directly without a Writ login. Your own Anthropic, OpenAI, or Ollama keys can also stay local and are never billed by Writ.
How is it different from self-hosting?
Writ Desktop is a one-click native app for a single machine. Self-hosting runs the open-core engine on a server via Docker for always-on, multi-agent fleets you operate yourself.
Which platforms are supported?
macOS, Windows, and Linux.
get ▸ download writ 08
08
download

Run it on your own machine.

Download for macOS Windows Linux

Free with your Writ account - local-only mode available. macOS 12+, Windows 10+, or Linux. Prefer a server? Self-host with Docker.

Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.