Writ Cloud

app.usewritPublished by usewrit.appOfficial publisherv1.0.0Updated Oct 24, 2026

Read, crawl and act on websites, signed in as the user, and turn any site into an API.

Overview

AI-generated overview

Writ Cloud lets an assistant drive a real cloud browser, run saved web workflows, scrape and crawl sites, and turn websites into callable APIs.

What you can do
Open and drive a real browser session: navigate, click, fill forms, read the page and its network calls, then save the session as a replayable workflow or API function, handing CAPTCHAs, 2FA codes or sign-in to the user when needed. Run, inspect, edit, schedule, pin and publish saved workflows, and read, search or export the data they collected. Scrape single pages or listings as markdown, start and poll site crawls, and read saved crawls and captured files. Watch pages for changes and wire the change event to a notification, workflow or AI task, or create automations from events, webhooks and schedules. Sign in as saved personas, pay on a site with a user-approved card, and manage linked Wr
When to use it
Use it when you want an assistant to work with sites that need a real browser or a signed-in session, to reuse browser tasks you have already recorded, or to collect and query data from pages and whole sites on a schedule.
Requirements
A Writ account and an API key with the mcp scope, supplied as the WRIT_API_KEY environment variable. Runs as a remote endpoint at the Writ Cloud address or as a local npm package (writ-mcp) needing Node.js; a self-hosted coordinator can be targeted with a URL. Network access to the Writ service.
Before you install
The API key is a credential: pass it via WRIT_API_KEY rather than the command line, and scope it narrowly. Open cloud browser sessions bill until closed, and crawls are metered, so re-crawling is costly. The payment tool can spend money on a site with the user's card, though the user approves and confirms. Workflows, crawls, schedules, monitors and published endpoints write and change data in the account; persona credentials stay sealed server-side.

Installation

In SourceWeft

  1. Open Writ Cloud in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.usewrit%2Fwrit-cloud/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "writ-cloud": {
      "type": "http",
      "url": "https://api.usewrit.app/mcp"
    }
  }
}

README


writ-mcp connects a stdio MCP client — Claude Code, Claude Desktop, Cursor, Windsurf, Codex — to Writ, so the browser workflows you already recorded become tools your assistant can call: run them, read the data they collected, search past results, schedule them, expose them as REST endpoints, and kick off site crawls.

It is a transparent stdio↔HTTP proxy and nothing else. Every tool, schema and rule lives server-side, so what you get always matches what your instance can do — and a new tool never requires upgrading this package. Zero dependencies, one file, Node core only.

Clients that speak Streamable HTTP natively don't need this at all — point them straight at the /mcp endpoint with an Authorization: Bearer <key> header.

Quick start

1. Get an API key. In the Writ app: Settings → Developers → API keys. Keys look like wt_….

2. Add the server.

Against a self-hosted coordinator:

bash
claude mcp add writ-selfhost -e WRIT_API_KEY=<YOUR_API_KEY> -- npx -y writ-mcp --url https://writ.example.com

Against a coordinator on this machine:

bash
claude mcp add writ-selfhost -e WRIT_API_KEY=<YOUR_API_KEY> -- npx -y writ-mcp --url http://localhost:8000

Against a published per-workflow endpoint (an "Expose as MCP" slug URL is used verbatim — no path rewriting):

bash
claude mcp add my-tools -e WRIT_API_KEY=<YOUR_API_KEY> -- npx -y writ-mcp --url https://mcp.example.com/mcp/my-tools

3. Check it.

bash
claude mcp list

Writ Cloud is the default target when you pass no --url (https://api.usewrit.app). Pass --url to point the connector at your own coordinator instead. See Status.

Pass the key through the environment, not the command line. --api-key works, but it puts your key in the process's argument list where any local process can read it via ps, and your shell records it in history. The connector prints a note when you use it.

Your running coordinator also hands out these one-liners, pre-filled, on its Connect page and at GET /api/mcp/connect-info:

Claude Desktop / Cursor (config file)

Add to claude_desktop_config.json (Claude Desktop) or ~/.cursor/mcp.json (Cursor). The env form is recommended — it keeps the key out of the argument list:

json
{  "mcpServers": {    "writ-selfhost": {      "command": "npx",      "args": ["-y", "writ-mcp"],      "env": {        "WRIT_COORDINATOR_URL": "https://writ.example.com",        "WRIT_API_KEY": "<YOUR_API_KEY>"      }    }  }}

Without npm

A self-host install bundles this connector at connectors/writ-mcp. There is no build step, so you can run it straight from disk:

bash
node /path/to/writ/connectors/writ-mcp/index.js --url https://writ.example.com

It coexists with the other Writ servers. Each surface registers under its own slug on purpose — the desktop app is writ, Writ Cloud is writ-cloud, a self-hosted coordinator is writ-selfhost — and each identifies itself to the assistant with a distinct title. Keep any combination connected at once.

Tools you get

Served by the server you connect to, not by this package, so a new server tool reaches you without a connector update. Writ Cloud lists the 39 tools below; a self-hosted coordinator lists the ones marked in its column.

ToolWhat it doesWrit CloudSelf-hosted
writ_list_workflowsYour saved workflows (a run_<name> tool is added only for workflows you pin)yesyes
writ_run_workflowRun one and wait for the extracted datayesyes
writ_pin_workflow_toolPin or unpin a workflow as its own run_<name> tool — off by default, capped; everything still runs via writ_run_workflowyesyes
writ_update_workflowRead a workflow's outline or edit it in place (settings, steps, functions, its agent skill)yesyes
writ_diagnose_http_workflowShow what every request of a run was answered with, and whether it ran without a browseryesno
writ_create_http_extractionAuthor a multi-request browserless extraction from captured requestsyesno
writ_workflow_dataRead a workflow's accumulated data tableyesyes
writ_search_dataSearch across everything already collectedyesyes
writ_export_dataExport a workflow's data as CSV/JSONyesyes
writ_workflow_runsRun history and statusyesyes
writ_set_scheduleSchedule a workflow (interval / daily / weekly)yesyes
writ_expose_workflow_apiPublish a workflow as a callable REST endpointyesyes
writ_scrapeRead a page, or several, as clean markdown (Cloud also reads a listing's top N)yesyes
writ_crawl_site / writ_crawl_statusStart and poll a distributed site crawlyesyes
writ_crawl_filesThe original documents a crawl captured (PDFs, office files, images)yesno
writ_saved_crawls / writ_run_saved_crawl / writ_saved_crawl_dataSaved crawls (see below)yesyes
writ_update_saved_crawlInspect or change a saved crawl's settingsyesno
writ_personasSee your saved sign-in identities and get them ready (see below)yesyes
writ_paymentPay with a card the user approves; Writ places the order once they confirmyesno
writ_devicesYour linked Writ desktops: list them, or point this connection at oneyesno
writ_create_automationEvent or clock → run a workflow, notify, or wake an agentyesyes
writ_list_webhooksYour inbound webhook URLs and the automations they fireyesyes
writ_create_monitor / writ_wire_monitorWatch a page and react to changesyesyes
writ_browser_useOpen a real browser your assistant drives turn by turnyesyes
writ_record_websiteRecord a repeatable task as a workflowyesyes
writ_website_to_apiTurn a website into a callable APIyesyes
writ_discovery_statusFollow an API build to its resultyesno
writ_browser_act / _context / _network / _save / _cancelAct in the browser, read the page and its network calls, save or close the sessionyesyes
writ_browser_composeDefine named functions, inputs and explicit steps in a sessionyesno
writ_browser_ask_userHand a CAPTCHA, a code or a decision to the user in the live browseryesno
writ_browser_sessionsOpen browser sessions you can resumeyesno
writ_record_start / _act / _context / _network / _save / _cancelOlder names of the browser loop, kept for compatibilitynoyes

The build tools (writ_browser_use, writ_record_website, writ_website_to_api, then writ_browser_act / _context / _network / _save / _cancel) are on both targets; neither has a writ_build tool, so use writ_record_website. Your assistant opens a real browser, drives it turn by turn, and saves the session as a reusable workflow that afterwards replays with no model in the loop. Writ Cloud runs it on Writ's fleet; a self-hosted coordinator runs it on your own fleet agent. Either way your assistant is the brain — no second model key is involved.

Reusing a recent result (max_age)

Running a workflow drives a real browser, so asking the same question twice in one session costs two full runs and two waits. Every workflow tool takes an optional max_age (seconds) meaning a recent answer is good enough:

jsonc
{ "name": "run_price_check", "arguments": { "sku": "B0C123", "max_age": 300 } }
  • omitted or 0 — always run fresh (the default; nothing goes stale on its own).
  • N — reuse a result younger than N seconds, otherwise run.

A reused answer carries _cache: {hit: true, age_seconds: N} so the assistant can tell how current it is.

max_age works identically against Writ Cloud and a self-hosted coordinator, and on a pinned workflow's own run_<name> tool as well as writ_run_workflow.

Calling a saved crawl (writ_run_saved_crawl)

A whole-site crawl is slow and metered, so re-crawling to answer the same question is the most expensive mistake an assistant can make. A saved crawl is a stored crawl configuration with a stable name, and the same max_age contract applies to it:

jsonc
{ "name": "writ_run_saved_crawl", "arguments": { "crawl": "docs", "max_age": 86400 } }
  • hit — the pages that crawl already collected come back inline, instantly, with nothing crawled and nothing metered.
  • miss — the site is crawled again with the saved settings, and you get a crawl id to poll with writ_crawl_status (a crawl outlives a single tool call).

Three tools cover the surface:

ToolWhat it does
writ_saved_crawlsList saved crawls. Check here before crawling a site again.
writ_run_saved_crawlRun one, reusing recent data when max_age allows.
writ_saved_crawl_dataRead what one already collected, at any age. Never crawls.

To create one, pass save_as to writ_crawl_site — that saves the settings and runs them, so the crawl becomes callable by REST as well. Re-using the same save_as updates that saved crawl instead of piling up duplicates. Saving needs an admin-scoped credential (it creates reusable, callable configuration); running one needs only run.

Sites behind a login (writ_personas)

A persona is a saved sign-in identity — username, credentials sealed server-side, optional 2FA, and a warm signed-in session. writ_personas lists yours (with per-persona readiness), inspects one (get), refreshes its session by running its login workflow (sign_in), or has the AI record the sign-in flow once so the persona can sign itself in from then on (record_login). The assistant then passes a persona_id to writ_run_workflow (and each pinned run_<name> tool), writ_crawl_site, or writ_scrape — plus writ_browser_use on Writ Cloud — and the task runs signed in, with 2FA codes minted server-side.

By design the connector can only use personas, never manage them: creating, editing or deleting one involves credentials, and no credential or one-time code ever crosses the MCP connection in either direction. Personas are created in the Writ dashboard.

If a tool call times out

It comes back as status: "running" with retryable: true. The run was not cancelled — calling the tool again starts a second run. Wait, then retry with a max_age wide enough to pick up the first run's result once it lands.

Configuration

Flags take precedence over environment variables.

FlagEnvDefaultPurpose
--urlWRIT_COORDINATOR_URL / WRIT_URLhttps://api.usewrit.appTarget base URL. A URL whose path is already /mcp or /mcp/<slug> is used verbatim.
--api-keyWRIT_API_KEY— (required)Key for Authorization: Bearer. Prefer the env var.
--insecureWRIT_INSECURE_TLS=1offAccept a self-signed local-CA cert. Private networks only.
--timeoutWRIT_MCP_TIMEOUT_MS600000Per-request timeout (ms); covers long writ_run_workflow waits.
--help / --version——Print usage or version and exit.

HTTPS with a local CA (self-host): trust the CA (recommended) and use the https:// address, or set NODE_EXTRA_CA_CERTS=/path/to/ca.pem. Use --insecure only for localhost testing — it disables certificate verification entirely, which exposes your key to a man-in-the-middle.

Security

This process exists to carry a credential, so everything that could expose one is made loud rather than convenient. Full detail in SECURITY.md.

  • The key goes to --url and nowhere else. No telemetry, no analytics, no update check. Zero dependencies means there is no transitive code in the process that could phone home — and CI fails the build if that ever changes.
  • Redirects are never followed. Replaying your Authorization header to whatever origin a Location header names would hand your key to a host you didn't choose. A 3xx becomes an error telling you to point --url at the final URL.
  • Credentials in a URL are redacted from every diagnostic. MCP clients write a server's stderr to a log file on disk; https://user:pass@host/ would otherwise be written down in plaintext.
  • Loud warnings, on stderr, for every way a key leaks: TLS verification disabled, plaintext http:// to a non-loopback host, or a key passed on the command line.
  • Retries never double-run a workflow. Only read-only methods are retried; tools/call is sent exactly once, because a retry could re-execute a side effect the connector cannot see.
  • Responses are bounded at 32 MB, so a broken endpoint can't grow this process until the OS kills your session.
  • No request is ever left unanswered — a hung MCP client is a denial of service on your assistant, and that is the failure this connector works hardest to make impossible.

Scope your keys. Give a key only workflows:read / workflows:execute unless a tool you actually use needs more.

Verifying what you install

Releases are published from CI with npm provenance, so the tarball is cryptographically linked to the commit and workflow that built it:

bash
npm audit signatures

Troubleshooting

SymptomCause and fix
Unauthorized: … rejected the API keyThe key is wrong, disabled, or lacks scope. Recreate it under Settings → Developers with workflows:read / workflows:execute.
Cannot reach …Wrong --url, or the target is down. For a self-signed cert see the local-CA note above.
… redirected (HTTP 301)Your reverse proxy redirects (usually http → https). Point --url at the final URL.
The API key contains characters that cannot be sent in an HTTP headerA newline or control character got into the key — usually a copy-paste artifact. Re-copy it.
No tools listedThe connector could not reach the coordinator, or the key was rejected — see the rows above. With a working connection the static writ_* tools are always listed, even before you save a workflow.
A workflow has no run_<name> toolDerived tools are opt-in and off by default. Pin the workflow with writ_pin_workflow_tool (or the app's Expose as MCP tool switch) and it appears on the next tools/list, up to 20 per account. Every workflow runs through writ_run_workflow either way.
Client won't connect, no errorRead the connector's stderr — your client logs it. Claude Code: ~/Library/Caches/claude-cli-nodejs/<project>/mcp-logs-<name>/.

Status

Self-hosted coordinatorSupported and verified end to end.
Published /mcp/<slug> endpointsSupported.
Writ Cloud (https://api.usewrit.app, the no---url default)Supported. Used automatically when no --url is passed.

Development

bash
npm test

No dev dependencies — the suite uses Node's built-in node:test and drives the real index.js as a subprocess against a mock MCP server, exercising the same stdio path an MCP client uses. It runs in about six seconds. npm publish runs it automatically via prepublishOnly.

See CONTRIBUTING.md — note the two hard rules: zero dependencies, permanently, and no tool logic here.

The rest of Writ

usewrit/writThe self-host coordinator — web UI, API, your data. Start here.
usewrit/writ-agentThe Rust fleet worker that does the actual browsing.
writ-mcp (this repo)The MCP connector.

License

MIT — see LICENSE.

This package is deliberately permissive because it runs inside your MCP client, not inside the coordinator, so it has to be embeddable anywhere. The coordinator it talks to is AGPL-3.0-only; the two licenses are not interchangeable.

Source: README.md at commit 9af09e7

Tools

41

writ_browser_use

Open a browser

A REAL CLOUD BROWSER FOR A TASK ON A SITE: the user's signed-in account (a persona_id from writ_personas: the password stays sealed in Writ, and sessions never ask for a password), a click, form, submit or search inside an app, or a page a plain fetch cannot open (login wall, 403, CAPTCHA). Opens the browser and returns the first page; writ_browser_act drives it (Writ runs no model here). Recording is always on: writ_browser_save turns the session into a workflow that replays without a browser, writ_browser_cancel closes it (an open browser bills). The start answer carries the action vocabulary, the recording rules and, with a persona, the 2FA rules. NOT FOR: reading pages (writ_scrape). An API: writ_website_to_api opens this same browser, bound to a build.

Parametersurlrequiredgoalauth_modefresh_exitpersona_iduse_residentialexecution_targetresidential_country

writ_record_website

Record a website task

Records a repeatable task on a site as a workflow (goal + start url): the same session as writ_browser_use, labelled with its goal, driven with writ_browser_act and saved with writ_browser_save. A goal that asks for an API opens as a writ_website_to_api build instead: the same browser, bound to the build.

Parametersurlrequiredgoalrequireddeviceauth_modefresh_exitpersona_idskip_existinguse_residentialskip_marketplaceresidential_country

writ_website_to_api

Turn a website into an API

TURNS A WEBSITE INTO A CALLABLE API (named functions with inputs, returning JSON), built by the caller in a real browser. url = the page that already shows the rows (search results or a listing, not the home page); goal = the inputs and fields wanted. The call first proposes the user's matching saved workflows and marketplace APIs (skip_existing / skip_marketplace build fresh), then opens a cloud browser bound to the build: capture_network records the site's own calls, writ_browser_network reads them, api_call probes them; a failed probe is evidence, not the end. Functions: HTTP flows first (writ_browser_compose define_function `flow`; writ_help('http_flows')), single requests (from_index) mixed in, DOM extraction last. writ_browser_save, then run_example on two inputs. mode=intelligent: Writ builds it alone (+ writ_discovery_status wait=true), on request.

Parametersurlgoalmodelevelscopedevicesave_asbuild_idanonymouspersona_idai_superviseskip_existing+5 more

writ_discovery_status

Check an API build

Status of a writ_website_to_api build. wait=true is one held call (up to 75 s) that follows the build to its newest rung and returns when it is done or parked. Answers: succeeded (workflow_id, functions, run_example), failed, cancelled, or needs_guidance (the build is the caller's to finish with writ_website_to_api mode=guided build_id=<id>; its map comes with it).

Parameterswaitbuild_idrequiredtimeout_seconds

writ_browser_act

Act in a browser session

Runs one batch of actions on an open session and returns the fresh page. Each action is an object, e.g. {"action":"click","selector":"#go"}. DRIVE: navigate, click, fill, type_text, select, check, hover, submit, press_key, scroll, back, wait, wait_for. SEE: query_dom, find_text, read_text, count, get_attributes, inspect, list_candidates, get_dom, get_screenshot. NETWORK: capture_network, get_request, rotate_exit. CODE: evaluate_js, search_scripts, read_script. RECORD: extract {variable,script}, api_call, login_post, probe_write, confirm_write. 2FA: twofa {challenge_method}. A value written {{name}} with its real value in `inputs` becomes a workflow input. Each action's arguments: the session's start answer, or writ_help('writ_browser_act').

Parametersinputsactionsrequiredmax_charssession_idrequired

writ_browser_context

Read a browser session

Re-reads an open session: section=page (url, fields, buttons, cleaned DOM), lists (the page's repeating rows with a live-tested define_function payload for writ_browser_compose), map (the evidence of the build the session is bound to).

Parametersoffsetsectionmax_charssession_idrequired

writ_browser_network

Read a session's network calls

Searches (operation=search, query, method) or reads in full (operation=detail, index) the backend requests the page made after capture_network: the site's real API. writ_browser_act api_call probes one with other values (a `flow`: several requests); an index feeds writ_browser_compose define_function from_index.

Parametersindexquerymethodoffsetmax_charsoperationsession_idrequired

writ_browser_compose

Compose a workflow in a session

Authors the workflow in an open session beyond a recording: named API functions (define_function with a `flow` (preferred in an API build), from a captured call's index, or a lists payload; live-tested as defined; compile_function for an authenticated request), set_inputs, add_steps, test_function, remove_function, remove_step, list. Payload shapes: writ_help('writ_browser_compose').

Parameterspayloadoperationrequiredsession_idrequired

writ_browser_save

Save a session as a workflow

Saves the open session as a replayable workflow and closes the browser, in the place its browser ran: the user's desktop library or Writ Cloud. Composed functions become callable API functions, declared inputs become its parameters. The answer carries the steps, the inputs and a run_example; the workflow runs at zero AI cost through writ_run_workflow. A save that references something no run could resolve is refused with the reasons, and the browser stays open.

Parametersnamesave_tokeep_opensession_idrequireddescriptionallow_no_data

writ_browser_ask_user

Ask the user to step in

Hands an open session to the Writ user: kind='captcha' (they complete a security check in the live browser), 'twofa' (they supply the one-time code and Writ types it; the code never reaches this conversation), 'sign_in' (they sign in on the live page; no persona applies) or 'question' (their text answer). The call that opens the ask returns at once with user_link + tell_user to relay; later calls hold up to 60 s and answer answered, waiting_for_user (the same call again) or expired. Their answer is kept if your turn ends first.

Parameterskindquestionsession_idrequiredwait_seconds

writ_browser_cancel

Close a browser session

Closes an open browser session (an open cloud browser bills until it is closed). Unsaved work that did more than visit pages is auto-saved first and the reply names it; discard=true keeps nothing.

Parametersdiscardsession_idrequired

writ_browser_sessions

List open browser sessions

Lists the account's open cloud browser sessions (each resumable by its session_id).

Parameterslimitinclude_closed

writ_personas

Use the user's saved sign-ins

The user's own accounts on websites (personas): how Writ signs in as them. No password passes through this tool or the conversation, and its answers never ask for one: credentials are typed only into a Writ window. action='list' domain=<site> shows the personas usable there; with none it answers persona_needed: a tell_user for the user, a create_url (a small Writ window with only the sign-in form, pre-filled for the site) and a link_id. action='wait' link_id=<id> is one held call that answers when the user saves it, with its persona_id. Also get, request (a link for another account), sign_in (refresh the session) and record_login. A persona_id works on writ_scrape, writ_crawl_site, writ_browser_use and writ_run_workflow; a desktop persona ('device:...') signs in on that desktop, from its own vault.

Parameterswhywaitforceactionrequireddevicedomainlink_idlogin_urlpersona_idinclude_runsexecution_target

writ_payment

Pay with a card the user approves

Pays on a site with one of the user's cards; card numbers never reach this conversation. request (site, max_amount, purpose) returns a tell_user and an open_url where the user approves; wait (grant_id or confirmation_id); checkout pauses at the order button for the user's confirmation, then Writ places the order; fill; list (card handles only). Details: writ_help('writ_payment').

Parameterssitestepsactionrequiredfieldspurposesessionsummarycurrencygrant_idmax_amountautomation_idtotal_selector+3 more

writ_devices

Choose a linked desktop

The user's linked Writ desktops: list, use (scope this connection to one: runs, browsers, personas and monitors then target it), clear, monitors, datasets.

Parametersactiondevice

writ_list_workflows

List saved workflows

Lists the workflows saved in the Writ account; each runs on demand without live browsing. Returns id, name, declared inputs, schedule, and whether it is pinned as its own run_<name> tool.

Parameterssearch

writ_run_workflow

Run a saved workflow

Runs a saved workflow by workflow_id or name and returns its extracted data (it waits by default). Inputs go as top-level fields or under `inputs`; function_name runs one function of a multi-function API (with the sign-in it needs). max_age reuses a recent result at no cost. A write function previews with mutation_mode='dry_run'. Runs sign in as the workflow's persona or persona_id; no password is ever passed. Venue, network, files and output shape: writ_help('writ_run_workflow').

Parameterswaitfilesdeviceinputsoutputmax_ageworkflowpersona_idworkflow_idfunction_namemutation_modefunction_names+4 more

writ_update_workflow

Edit a saved workflow

Inspects or edits a saved workflow: an outline, one function's source, targeted function or step edits, a settings patch. copy_to keeps a linked copy on Writ Cloud or the user's desktop. Every option: writ_help('writ_update_workflow').

Parameterspathlimitpatchdeviceoffsetcopy_tosectionstep_idverboseoperatorworkflowmax_chars+8 more

writ_create_http_extraction

Build an HTTP extraction

Drafts or revises a multi-request browserless HTTP extraction (loops, GraphQL, cursor pagination) from captured requests and a plain-language goal. Every option: writ_help('writ_create_http_extraction').

Parametersgoalrequiredapplyworkflowstep_indexworkflow_idrequirementsdesired_inputsrequest_samplesresponse_sample

writ_diagnose_http_workflow

Diagnose a workflow's HTTP lane

Explains why a saved workflow's run returned nothing or failed: HTTP-lane readiness and, with task_id, the run's requests and responses.

Parameterstask_idworkflowworkflow_id

writ_pin_workflow_tool

Pin a workflow as a tool

Pins (or unpins) a saved workflow as its own run_<name> tool on this server.

Parameterspinnedworkflowworkflow_id

writ_workflow_data

Read a workflow's collected data

Reads a saved workflow's collected data as a table: q filters, run_id picks one run, refs returns full records.

Parametersqrefsviewlimitdeviceoutputrun_idworkflowworkflow_idpreview_chars

writ_search_data

Search collected data

Searches everything the account's workflows already collected for a term, without running anything.

Parametersqrequiredlimitdeviceworkflowworkflow_idpreview_chars

writ_export_data

Export collected data

Exports a workflow's full data table as CSV or JSON.

Parametersqviewformatworkflowworkflow_id

writ_workflow_runs

List workflow runs

Run history (status, timing, errors, venue) of one workflow or all of them.

Parameterslimitdevicestatusworkflowworkflow_id

writ_set_schedule

Schedule a workflow

Schedules a saved workflow: every_minutes, or kind='daily'/'weekly' with time (HH:MM) and days. functions + inputs schedule chosen functions of a multi-function API.

Parameterstzdayskindtimeinputsenabledfunctionworkflowfunctionsworkflow_idevery_minutes

writ_expose_workflow_api

Publish a workflow as a REST API

Publishes a saved workflow as a REST endpoint (a POST URL that waits and returns its JSON). Repeated calls reuse it.

Parameterslabelworkflowworkflow_idwait_timeouttimeout_seconds

writ_crawl_site

Crawl a site into a dataset

COLLECTS a site or a section into a queryable, change-tracked dataset (one row per page). Scope: intent (a section, in plain words), rank_cap=N (the top N items of a listing), seed_urls (known pages), or the whole site capped by page_budget. Modes: markdown (default, no AI), extract_mode='schema' (uniform records), executor='ai' + extract_prompt (per-page understanding, 5x the page rate). A bounded crawl answers with its rows; an open one returns a crawl_id for writ_crawl_status wait=true. NOT FOR: reading a few pages now (writ_scrape). Every option: writ_help('writ_crawl_site').

Parametersurlrequirednamewaitlimitspeeddeviceintentoutputmax_agesave_asdelay_msexecutor+23 more

writ_saved_crawls

List saved crawls

Lists the crawls saved for re-running, with their scope.

Parameterslimit

writ_update_saved_crawl

Edit a saved crawl

Inspects or changes a saved crawl's settings in place.

Parametersnamecrawlrequiredsettingsdescriptiondefault_max_age_seconds

writ_run_saved_crawl

Run a saved crawl

Runs a saved crawl; max_age returns its recent data at no cost instead of re-crawling.

Parameterswaitcrawlrequiredlimitoutputmax_agepreview_charstimeout_seconds

writ_saved_crawl_data

Read a saved crawl's data

Reads the data a saved crawl collected on its last completed run, without crawling.

Parameterscrawlrequiredlimitoutputpreview_chars

writ_scrape

Read web pages

READ PAGES NOW, no browser session: one page (url), up to 20 pages in parallel (urls), or a listing plus its top N item pages (url + top_n). Returns clean markdown in 2-10 s, including pages a plain fetch cannot read: rendered by JavaScript (render_mode='browser'; a read that only got the page's shell says so and gives the retry), behind a bot wall or 403 (an automatic residential retry), or behind the user's sign-in (persona_id). Discussion threads keep their comments. format='html' returns the raw HTML for selectors. NOT FOR: a site-wide dataset (writ_crawl_site) or clicking and typing (writ_browser_use).

Parametersurlurlstop_ndeviceformatpersona_idrender_modeinclude_pathspreview_charsrespect_robotsuse_residentialresidential_country

writ_crawl_status

Check a crawl

Status of a crawl by crawl_id; wait=true holds up to 75 s and returns the collected rows when it converges.

Parameterswaitlimitoutputcrawl_idrequiredpreview_charstimeout_seconds

writ_crawl_files

List a crawl's captured files

The original files (PDFs, office documents, images, CSVs) a crawl captured, with short-lived download URLs.

Parametersrunscrawllimitcrawl_id

writ_create_automation

Create an automation

Creates an automation: on an event (a workflow or crawl completed, a monitor change, a webhook, a schedule) it runs a workflow, sends a notification templated over the event's data, and/or wakes an AI agent. Event, template and webhook options: writ_help('writ_create_automation').

Parametersnamerequiredwhentitleblocksinputsnotifyenabledchannelspriorityscheduleai_prompttarget_id+13 more

writ_list_webhooks

List inbound webhook URLs

The account's inbound webhook URLs and the automations they fire.

Parameterswebhook_trigger_id

writ_create_monitor

Watch a page for changes

WATCHES a page for changes: Writ checks it on a schedule and fires change_detected when the page, a CSS selector's text, a value read by `extract`, or a visual zone changes. Returns the monitor_id that writ_wire_monitor connects to an alert, a workflow or an AI task (a price watch takes a threshold there). Without `interval` the answer is needs_input: this plan's options and a tell_user for the user, nothing created. The page is read first: a sign-in answers needs_persona, a bot check offers use_residential.

Parametersurlrequiredmodewatchdeviceenabledextractintervalselectorzone_textpersona_idsession_idtry_anyway+5 more

writ_wire_monitor

Connect a monitor to an action

Connects a monitor's change_detected event to an action: action='notify' (channels and recipients the account has configured), 'workflow' (runs a saved workflow), or 'ai_task' (an AI agent opens the page and works `prompt`). A price watch takes `threshold` (+ threshold_op): the action then runs once, when a check reads a price at or below it. Buying at a price (`buy`): writ_help('writ_wire_monitor').

Parametersbuynametitleactionrequireddevicepromptenabledmessagechannelsworkflowentry_urlmax_steps+7 more

writ_help

Writ tool reference

The full reference of any Writ tool (every parameter and its rules) and the complete guide. topic = a tool name (e.g. 'writ_browser_compose', a 'run_<workflow>' tool), 'guide' for the manual (recurring digests, HTTP flow building, buying on a price, crawl and build modes), 'actions' / 'recording' / '2fa' for the browser rules, 'http_flows' / 'flow_operators' for writing an HTTP flow, or empty for the list of topics.

Parameterstopic

writ_browser_live_view

Live browser view

The live browser card's own access: the card ChatGPT and Claude show under writ_browser_use and writ_record_website calls it to read the session's state and get one-time passes for the session's screencast and its take-over channel. The user watches the page in the card and can take it over there. It is not part of a conversation's work.

Parameterssession_idrequired

Version history

1
  1. v1.0.0LatestOct 10, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts