MCP

MCP

The coordinator speaks the Model Context Protocol. Attach an AI client and your saved workflows become tools it can run, read, schedule, expose — and build, by driving a live recording session.

Setting it up

1. Create an API key with mcp:execute, plus whichever resource scopes you want the assistant to have (workflows:read, workflows:execute, runs:read, datasets:read is a good start). Without mcp:execute every call fails.
2. Add the connector. The Connect page generates the snippet for your client, prefilled with your endpoint.

Claude Code

claude mcp add writ-selfhost -- npx -y writ-mcp --url https://writ.example.com --api-key <YOUR_API_KEY>

Claude Desktop / Cursor

{
  "mcpServers": {
    "writ-selfhost": {
      "command": "npx",
      "args": ["-y", "writ-mcp", "--url", "https://writ.example.com", "--api-key", "<YOUR_API_KEY>"]
    }
  }
}

Any Streamable-HTTP client, no Node

{
  "mcpServers": {
    "writ-selfhost": {
      "type": "http",
      "url": "https://writ.example.com/mcp",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

It registers as writ-selfhost on purpose, so it coexists with the Writ desktop app (which registers as writ). The server identifies itself as "Writ Self-Host Coordinator".

writ-mcp is a zero-dependency Node bridge (Node 18+). It also ships in the repo at connectors/writ-mcp, so npx is a convenience rather than a requirement.

The tools

25, plus a run_<name> tool per saved workflow.

Family	Tools
Operate	writ_list_workflows · writ_run_workflow · writ_workflow_data · writ_search_data · writ_export_data · writ_workflow_runs
Automate	writ_set_schedule · writ_expose_workflow_api · writ_create_automation · writ_create_monitor · writ_wire_monitor
Crawl	writ_crawl_site · writ_crawl_status
Build	writ_record_start · writ_record_act · writ_record_context · writ_record_network · writ_record_save · writ_record_cancel
Drive a browser	writ_browser_use · writ_browser_act · writ_browser_context · writ_browser_network · writ_browser_save · writ_browser_cancel

Building by recording

Building is un-guided: the assistant drives a live record session on your fleet and asks you for clarifications in the chat. What it produces is an ordinary workflow — replayable, editable, and free to run.

Answer from data first

writ_search_data queries everything already collected. For most questions that is the right first move: it is instant and costs nothing, where re-running a workflow costs a browser session.