Give Windsurf real web actions on any site
Give Cascade real web actions on any site via MCP, authenticated and on your own accounts.
{
"mcpServers": {
"writ-cloud": {
"serverUrl": "https://api.usewrit.app/mcp",
"headers": { "Authorization": "Bearer wt_your_api_key" }
}
}
} 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 saved workflow is callable, and each one you pin 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.
What Windsurf 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
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 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 Windsurf can read and act on - fields, not raw page text - so the agent can chain the result into the next step.
Add Writ to Windsurf 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.
{
"mcpServers": {
"writ-cloud": {
"serverUrl": "https://api.usewrit.app/mcp",
"headers": { "Authorization": "Bearer wt_your_api_key" }
}
}
} - 1Step 1
Open Windsurf → Settings → Cascade → MCP servers.
- 2Step 2
Add the "writ-cloud" server with your wt_ API key.
- 3Step 3
Refresh; the Writ tools are available to Cascade.
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 Windsurf 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.
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 site flow (a real browser when the site needs one), 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.
Three ways to get a Windsurf 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.
Use Writ tools in any MCP client
Windsurf + Writ questions
How do I add Writ tools to Windsurf?
What can Windsurf actually do with a Writ MCP tool?
Does it handle login and 2FA in Windsurf?
Is this read-only, like most website-to-MCP servers?
Give Windsurf 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.