Give Cursor real web actions on any site
Give the Cursor agent real web actions on any site via MCP, without leaving the editor.
{
"mcpServers": {
"writ-cloud": {
"url": "https://api.usewrit.app/mcp",
"headers": { "Authorization": "Bearer wt_your_api_key" }
}
}
} 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 an API with auto-repair behind it, so it keeps working when a site's layout shifts under it.
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.
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.
{
"mcpServers": {
"writ-cloud": {
"url": "https://api.usewrit.app/mcp",
"headers": { "Authorization": "Bearer wt_your_api_key" }
}
}
} - 1Step 1
Open Cursor → Settings → MCP → Add new server.
- 2Step 2
Paste the "writ-cloud" config with your wt_ API key.
- 3Step 3
Enable the server; the tools appear in the 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.
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.
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.
Use Writ tools in any MCP client
Cursor + Writ questions
How do I add Writ tools to Cursor?
What can Cursor actually do with a Writ MCP tool?
Does it handle login and 2FA in Cursor?
Is this read-only, like most website-to-MCP servers?
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.