Does it handle login and 2FA in Cursor?

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 linked0

Give Cursor real web actions on any site

Give the Cursor agent real web actions on any site via MCP, without leaving the editor.

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.

.cursor/mcp.jsonHTTP

HTTP

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

read ▸ what it is01

what it is

Writ tools, inside the editor agent

Cursor's agent can call MCP tools. Add your Writ server and the agent gains authenticated, action-taking tools for the exact sites your project touches: internal dashboards, vendor portals, no-API web apps.

1
Add the Writ server in Cursor's MCP settings and the tools appear to the agent automatically, selected by description.
2
Each tool is a recorded workflow with AI fallback, so it keeps working when a site's layout shifts under it.

tools ▸ what they do02

tools

What Cursor can do with a Writ tool

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

⊘

Authenticated actions

Cursor 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 Cursor can read and act on - fields, not raw page text - so the agent can chain the result into the next step.

wire ▸ connect it03

connect

Add Writ to Cursor over HTTP

Paste the server block, authenticate with a scoped wt_ key, and every saved workflow is callable - the ones you pin appear as their own tools.

.cursor/mcp.jsonHTTP

HTTP

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

1
Step 1
Open Cursor → Settings → MCP → Add new server.
2
Step 2
Paste the "writ" config with your wt_ API key.
3
Step 3
Enable the server; the tools appear in the agent.

What this client getsWeb-action tools inside the editor agent

{ }

Every workflow is callable; the ones you pin are tools. Anything you save in Writ - a recorded flow, an AI-built workflow, a discovered API - is callable from Cursor through writ_run_workflow; pin a workflow and it shows up as its own tool with a typed schema. See how MCP tools work or read the developer MCP docs.

auth ▸ logged-in web04

the hard web

Login, 2FA, and dynamic pages - handled

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

Because every tool runs the real browser flow, Cursor 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 OTPAI navigationReal Chromium rendering30+ step types

build ▸ the tool05

build

Three ways to author a Cursor tool

All three produce the same callable workflow - which becomes its own tool the moment you pin 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 clients06

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 clientWindsurf MCP tools ▸Give Cascade real web actions on any site via MCP, authenticated and on your own accounts.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 answered07

faq

Cursor + Writ questions

How do I add Writ tools to Cursor?

Open Cursor → Settings → MCP → Add new server. Paste the "writ" config with your wt_ API key. Enable the server; the tools appear in the agent. Every saved workflow is then callable through writ_run_workflow; each one you pin appears as its own tool, selected by its description and typed input schema.

What can Cursor 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. Cursor 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 Cursor setup, and revoke it without touching the rest.

rec ▸ ready●

Give Cursor 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