Does it handle login and 2FA in Windsurf?

Yes. Writ runs the workflow in a real browser on your own account, handling login, TOTP and mailbox-OTP two-factor, and dynamic pages - so the tool completes authenticated tasks the agent could not reach otherwise.

src ▸ client linked 0

Give Windsurf real web actions on any site

Give Cascade real web actions on any site via MCP, authenticated and on your own accounts.

Get started free See all MCP clients

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

mcp_config.jsonHTTP

HTTP

{
  "mcpServers": {
    "writ": {
      "serverUrl": "https://api.usewrit.app/mcp",
      "headers": { "Authorization": "Bearer wt_your_api_key" }
    }
  }
}

read ▸ what it is 01

what it is

Writ tools, inside the Cascade agent

Windsurf's Cascade agent supports MCP servers. Connect Writ and Cascade can take real actions on the web (log in, fill, click, extract) and return typed results into the flow you're building.

1
Register the Writ server in Windsurf and refresh; every published workflow shows up as a tool Cascade can reach for.
2
Workflows run on your own credentials in a real browser, so Cascade can finish authenticated tasks a read-only tool can't.

tools ▸ what they do 02

tools

What Windsurf can do with a Writ tool

Each tool is a published browser workflow - it acts on the live site, then returns structured output.

⊘

Authenticated actions

Windsurf acts on your own accounts - log in, pass TOTP and mailbox-OTP 2FA, then click, fill, and submit. Not a read-only crawl.

◍

Any site, no API required

Each tool is a recorded browser workflow, so it reaches sites that ship no API at all - internal dashboards, vendor portals, no-API web apps.

{ }

Typed, structured output

Every tool returns typed JSON Windsurf can read and act on - fields, not raw page text - so the agent can chain the result into the next step.

wire ▸ connect it 03

connect

Add Writ to Windsurf over HTTP

Paste the server block, authenticate with a scoped wt_ key, and your published workflows appear as tools.

mcp_config.jsonHTTP

HTTP

{
  "mcpServers": {
    "writ": {
      "serverUrl": "https://api.usewrit.app/mcp",
      "headers": { "Authorization": "Bearer wt_your_api_key" }
    }
  }
}

1
Step 1
Open Windsurf → Settings → Cascade → MCP servers.
2
Step 2
Add the "writ" server with your wt_ API key.
3
Step 3
Refresh; the Writ tools are available to Cascade.

What this client gets Web-action tools inside Cascade

{ }

The tool list is your workflow list. Anything you publish in Writ - a recorded flow, an AI-built workflow, a discovered API - shows up to Windsurf as a callable tool with a typed schema. See how MCP tools work or read the developer MCP docs.

auth ▸ logged-in web 04

the hard web

Login, 2FA, and dynamic pages - handled

The sites worth automating are usually the hard ones. Windsurf gets tools that handle them.

Because every tool runs the real browser flow, Windsurf can complete tasks a read-only MCP server never could: sign in, pass two-factor, navigate pages that render with JavaScript, and submit. It runs on your own accounts and credentials, on sites you are authorized to use.

PersonasTOTP & mailbox OTP AI navigationReal Chromium rendering 30+ step types

build ▸ the tool 05

build

Three ways to author a Windsurf tool

All three produce the same callable workflow - which becomes a tool the moment you publish it.

●

Record it

Do the task once in a real browser; the recorder captures every step into a workflow.

✦

Describe it

Tell an AI session your goal in plain language; it drives the page to build the workflow for you.

⌖

Discover it

Let API discovery watch a site's own network calls as you browse, then turn them into a fast workflow.

Get started free See workflows

also ▸ other clients 06

other clients

Use Writ tools in any MCP client

MCP clientClaude Desktop MCP tools ▸Give Claude Desktop real web actions on any site (login, forms, multi-step tasks) over MCP.MCP clientClaude Code MCP tools ▸Give Claude Code callable web actions on any site: one command to add the Writ MCP server.MCP clientCursor MCP tools ▸Give the Cursor agent real web actions on any site via MCP, without leaving the editor. OverviewAll MCP tools ▸How Writ exposes any website as authenticated, action-taking MCP tools. For developersREST API ▸Every workflow is also a callable REST endpoint, not just an MCP tool.

faq ▸ questions answered 07

faq

Windsurf + Writ questions

How do I add Writ tools to Windsurf?

Open Windsurf → Settings → Cascade → MCP servers. Add the "writ" server with your wt_ API key. Refresh; the Writ tools are available to Cascade. Each workflow you publish in Writ appears as a tool, selected by its description and typed input schema.

What can Windsurf actually do with a Writ MCP tool?

It takes real actions on a website: log in, fill forms, click through multi-step flows, extract fields, and submit - then return structured JSON. Because each tool is a real browser workflow, it works on sites that have no API. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

Is this read-only, like most website-to-MCP servers?

No. Most website-to-MCP tools only read page text. Writ tools act - they log in, fill, click, and complete multi-step tasks, then return typed output. Windsurf calls the tool; Writ runs the real workflow on your account.

How is a tool authorized?

Every call carries a scoped wt_ API key. You can issue a separate key per project or per Windsurf setup, and revoke it without touching the rest.

rec ▸ ready ●

Give Windsurf tools that act

Publish a workflow once, then call it from your agent as an authenticated, action-taking MCP tool. Get started free.

Get started