Give Claude Desktop real web actions on any site
Give Claude Desktop real web actions on any site (login, forms, multi-step tasks) over MCP.
{
"mcpServers": {
"writ-cloud": {
"url": "https://api.usewrit.app/mcp",
"headers": { "Authorization": "Bearer wt_your_api_key" }
}
}
} Writ tools, inside the desktop app
Claude Desktop speaks MCP natively. Point it at your Writ server and Claude can call every workflow you save; pin the ones you use most and each becomes its own tool: authenticated, on your own accounts, on sites that have no API of their own.
- 1
Claude reads each tool's description and input schema, so it picks the right Writ workflow for the task on its own.
- 2
Tools run the real browser flow (login, TOTP and mailbox-OTP 2FA, dynamic pages) and hand structured JSON back to the chat.
What Claude Desktop 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
Claude Desktop 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 Claude Desktop can read and act on - fields, not raw page text - so the agent can chain the result into the next step.
Add Writ to Claude Desktop 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 Claude Desktop → Settings → Developer → Edit Config.
- 2Step 2
Add the "writ-cloud" server block to mcpServers with your wt_ API key.
- 3Step 3
Restart Claude Desktop; your Writ workflows appear as tools.
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 Claude Desktop 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. Claude Desktop gets tools that handle them.
Because every tool runs the real site flow (a real browser when the site needs one), Claude Desktop 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 Claude Desktop 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
Claude Desktop + Writ questions
How do I add Writ tools to Claude Desktop?
What can Claude Desktop actually do with a Writ MCP tool?
Does it handle login and 2FA in Claude Desktop?
Is this read-only, like most website-to-MCP servers?
Give Claude Desktop 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.