ag ▸ agent connected 0
Writ Desktop · MCP

Your AI agent can build the website API itself.

Connect an MCP-compatible agent to Writ Desktop. It gets a private local browser, records successful actions as a durable workflow, exposes the result as an API and MCP tool, and replays it later without rebuilding.

Download Writ Desktop Read the MCP guide
  • No Writ account required
  • No second AI provider key
  • Local browser + encrypted library
  • Cloud linking is optional
fl ▸ request to api 3
01
the flow

From a request to a reusable API

The connected agent does the reasoning. Writ supplies the browser, recording engine, API surfaces, and deterministic runtime.

01Ask normallyTell your agent what the website API should do or return. No special Writ syntax is required.
02The agent drives WritWrit opens its private browser. The agent navigates through MCP observations and structured actions while Writ records successful steps.
03Writ saves and exposes itThe live-tested workflow appears in Desktop and becomes a typed MCP tool. Local REST and OpenAI-compatible endpoints can be enabled too.
04Replay without rebuildingLater calls run the saved deterministic workflow. The agent can also schedule it, read its latest data, and inspect failures.

Ask your agent

"Turn this supplier portal into an API that accepts a product code and returns current stock, price, and delivery date."

Writ creates

  • A recorded, live-tested workflow
  • Typed inputs and structured output
  • A reusable MCP tool
  • Optional local REST + OpenAI-compatible URLs
cap ▸ one connection 7
02
capabilities

Creation and operation, through one MCP connection

CreateOpen the local browser, record a repeatable website task, and save it into the encrypted Desktop library.
ExposeTurn an existing workflow into a secured local REST or OpenAI-compatible API without starting another server.
RunCall a saved workflow by name or id with structured inputs and return live extracted data.
ScheduleConfigure interval, daily, or weekly runs, then read the latest successful results without reopening the browser.
ObserveList workflows, inspect recent runs and errors, and reuse what already exists instead of creating duplicates.
Intervene safelyLogins, CAPTCHA, and 2FA can pause for visible user intervention inside Writ; secrets are not relayed through the agent.
mcp ▸ connect any client 11
03
quick start

Connect any MCP-capable AI agent

Open Writ Desktop once and choose Use locally. In Connect, copy the configuration generated for your operating system and add it to any AI client that supports local stdio MCP servers.

Claude, Cursor, and other MCP clients use the same bundled writ-agentd server. No Writ token, Cloud account, or provider key belongs in the MCP configuration.

json 
{
  "mcpServers": {
    "writ": {
      "command": "/absolute/path/to/writ-agentd",
      "args": ["mcp"],
      "env": {}
    }
  }
}
loc ▸ local or cloud 15
04
where it runs

Local by default. Cloud only when you want always-on.

The agent-native path works with no Writ user and no Cloud account. Workflows, credentials, browser state, and results stay on the computer. If an API later needs to run while that computer is off, open Writ Desktop and link a Cloud account, and the local workflow remains the same.

Use locally

  • Account optional
  • Loopback-only API by default
  • Your MCP client is the AI
  • Unlimited local execution

Link Writ Cloud later

  • Always-on managed execution
  • Runs while the computer is off
  • Schedules, teams, and managed capacity
  • Explicit opt-in from the Desktop UI
sec ▸ tools not secrets 19
05
security

The agent gets tools, not your secrets

Writ rejects secret answers over the MCP mission surface. Passwords, API keys, and one-time codes stay in the local vault or are entered visibly in Desktop. Local API keys are minted by the user, shown once, and never sent through the connected agent.

q ▸ common questions 23
06
faq

FAQ

Does this require a Writ account?
No. Choose Use locally in Writ Desktop. The local MCP server, browser engine, workflow library, schedules, and loopback API work without linking Writ Cloud.
Does Claude need a separate Anthropic API key inside Writ?
No. For work initiated over MCP, the connected client is already the AI. Writ provides tools and browser observations; it does not invoke the provider-backed Concierge. Writ's built-in assistant still uses a provider configured inside Writ.
Is this only for Claude?
Claude is the documented quick-start example. The connector is a local stdio MCP server, so another AI client can use it when that client supports MCP tool discovery and calls.
Does the agent browse from scratch every time?
No. Repeatable tasks are saved as deterministic workflows. Later calls replay the saved steps without another browser-planning mission or additional planning tokens.
Can the resulting API be always on?
Yes. Locally, the computer and Writ engine must be running. When you want managed always-on execution, open Desktop and explicitly link a Writ Cloud account.
go ▸ download desktop 27
07
get started

Give your AI agent a durable local browser.

Install Writ Desktop, connect your MCP client, and ask it to turn a website into an API.

Download Writ Desktop Read the MCP guide