src ▸ client linked 0

Give Cursor real web actions on any site

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

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-cloud": {
      "url": "https://api.usewrit.app/mcp",
      "headers": { "Authorization": "Bearer wt_your_api_key" }
    }
  }
}
read ▸ what it is 01
01
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. 1

    Add the Writ server in Cursor's MCP settings and the tools appear to the agent automatically, selected by description.

  2. 2

    Each tool is an API with auto-repair behind it, so it keeps working when a site's layout shifts under it.

tools ▸ what they do 02
02
Action-taking tools

What Cursor can do with a Writ tool

Each tool is an API Writ built from one sentence: it acts on the live site (a real browser only when the site needs one), 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 was built and tested on the live site, 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 it 03
03
Connect it

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-cloud": {
      "url": "https://api.usewrit.app/mcp",
      "headers": { "Authorization": "Bearer wt_your_api_key" }
    }
  }
}
  1. 1
    Step 1

    Open Cursor → Settings → MCP → Add new server.

  2. 2
    Step 2

    Paste the "writ-cloud" config with your wt_ API key.

  3. 3
    Step 3

    Enable the server; the tools appear in the agent.

What this client gets Web-action tools inside the editor agent
{ }

Every workflow is callable; the ones you pin are tools. Anything you save in Writ - an API Scribe built, a ready-made one you rebuilt, a recorded step - 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 web 04
04
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 site flow (a real browser when the site needs one), 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 OTP AI auto-repairReal Chromium rendering 30+ step types
build ▸ the tool 05
05
Build a tool

Three ways to get a Cursor tool

All three produce the same callable API - which becomes its own tool the moment you pin it.

✦

Describe it

Tell Scribe your goal in one sentence; it drives the live site, tests the result and hands you the API.

⌖

Pick a ready-made API

The marketplace lists APIs other people built and Writ checks daily: call one as is in the cloud, or rebuild it locally on Writ Desktop.

●

Record the difficult part

When a login or a picker needs your hands, click through just that step in a real browser; Writ builds the rest around it.

faq ▸ questions answered 07
07
FAQ

Cursor + Writ questions

How do I add Writ tools to Cursor?
Open Cursor → Settings → MCP → Add new server. Paste the "writ-cloud" 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 was built on the live site, 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.
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.
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.
api ▸ ready ●

Give Cursor tools that act

Describe the site once; Writ builds the API, and your agent calls it as an authenticated, action-taking MCP tool. Get started free.