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": {
"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 a recorded workflow with AI fallback, so it keeps working when a site's layout shifts under it.
What Cursor 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
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.
Add Writ to Cursor over HTTP
Paste the server block, authenticate with a scoped wt_ key, and your published workflows appear as tools.
{
"mcpServers": {
"writ": {
"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" config with your wt_ API key.
- 3Step 3
Enable the server; the tools appear in the agent.
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 Cursor as a callable 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 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.
Three ways to author a Cursor 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.
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
Publish a workflow once, then call it from your agent as an authenticated, action-taking MCP tool. Get started free.