Writ Cloud — Claude Code MCP server: what it does, how to install
Writ Cloud brings saved browser workflows and web scraping directly to your AI client via MCP. Run automations, pull clean markdown, and query collected datasets.
claude mcp add --transport http writ-cloud https://api.usewrit.app/mcpWhat Writ Cloud does
The writ-mcp connector operates as a transparent proxy between stdio-based clients and Writ Cloud. All tool definitions and schemas live on the coordinator side, meaning the connector requires zero updates when new tools become available. It runs on Node 18 or higher and consists of a single file with no external dependencies.
Assistants gain access to 39 tools to execute browser tasks, read extracted data tables, and scrape web pages into markdown. Users can schedule automated runs at set intervals or turn workflows into callable REST endpoints. Passing WRIT_API_KEY through environment variables avoids exposing your secret token to process inspection tools like ps.
What it helps with
- execute recorded browser automations and collect extracted datasets
- scrape webpage content into clean markdown
- schedule recurring runs on daily or interval timers
- publish existing browser tasks as callable REST endpoints
Example prompts for the agent
- Run the workflow for competitor pricing and display the extracted items.
- Scrape this documentation URL and convert the page content to markdown.
- Search previously gathered records for mentions of recent release notes.
How to install Writ Cloud
1Platform CLI: remote server
claude mcp add --transport http writ-cloud https://api.usewrit.app/mcp2Platform CLI
claude mcp add --env WRIT_API_KEY=<WRIT_API_KEY> --transport stdio writ-cloud -- npx -y writ-mcpReplace <…> with your own values
1Platform CLI: remote server
codex mcp add writ-cloud --url https://api.usewrit.app/mcp2Platform CLI
codex mcp add writ-cloud --env WRIT_API_KEY=<WRIT_API_KEY> -- npx -y writ-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"writ-cloud": {
"url": "https://api.usewrit.app/mcp"
}
}
}{
"mcpServers": {
"writ-cloud": {
"command": "npx",
"args": [
"-y",
"writ-mcp"
],
"env": {
"WRIT_API_KEY": "<WRIT_API_KEY>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"writ-cloud": {
"type": "http",
"url": "https://api.usewrit.app/mcp"
}
}
}{
"servers": {
"writ-cloud": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"writ-mcp"
],
"env": {
"WRIT_API_KEY": "<WRIT_API_KEY>"
}
}
}
}Replace <…> with your own values
1Platform CLI: remote server
gemini mcp add -t http writ-cloud https://api.usewrit.app/mcp2Platform CLI
gemini mcp add -e WRIT_API_KEY=<WRIT_API_KEY> writ-cloud npx -y writ-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Writ Cloud
How to install Writ Cloud in Claude Code?
For direct HTTP transport, run claude mcp add --transport http writ-cloud https://api.usewrit.app/mcp. If you prefer stdio via npx, use claude mcp add --env WRIT_API_KEY=<WRIT_API_KEY> --transport stdio writ-cloud -- npx -y writ-mcp.
What does Writ Cloud do?
It exposes your recorded Writ browser workflows to your AI assistant. The model can extract website data, poll crawling jobs, search historical run tables, and trigger remote tasks.
How should the API key be supplied?
Generate an API key starting with wt_ in the Writ dashboard under Settings → Developers → API keys. Pass it via the WRIT_API_KEY environment variable to keep it out of process argument lists.
