← usewrit.app

INDIVIDUAL MCP TOOL

writ_help

The full reference of any Writ tool (every parameter and its rules) and the complete guide.

usewrit.appnone authenticationAvailability not checked

LIVE ENDPOINT

https://api.usewrit.app/mcp

No auth detected

Connect to this endpoint to inspect the live schema for writ_help and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

usewrit.app

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.writ-cloud]
url = "https://api.usewrit.app/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "writ-cloud": {
      "type": "http",
      "url": "https://api.usewrit.app/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: writ-cloud
Remote MCP URL: https://api.usewrit.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "writ-cloud": {
      "url": "https://api.usewrit.app/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "writ-cloud": {
      "type": "http",
      "url": "https://api.usewrit.app/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "writ-cloud",
  "transport": "streamable-http",
  "url": "https://api.usewrit.app/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • writ_browser_use — A REAL CLOUD BROWSER FOR A TASK ON A SITE: the user's signed-in account (a persona_id from writ_personas: the password stays sealed in Writ, and sessions never ask for a password), a click, form, submit or search inside an app, or a page a plain fetch cannot open (login wall, 403, CAPTCHA).
  • writ_record_website — Records a repeatable task on a site as a workflow (goal + start url): the same session as writ_browser_use, labelled with its goal, driven with writ_browser_act and saved with writ_browser_save.
  • writ_website_to_api — TURNS A WEBSITE INTO A CALLABLE API (named functions with inputs, returning JSON), built by the caller in a real browser.
  • writ_discovery_status — Status of a website-to-API build (a guided one, or one started in the Writ app).
  • writ_browser_act — Runs one batch of actions on an open session and returns the fresh page.
  • writ_browser_context — Re-reads an open session: section=page (url, fields, buttons, cleaned DOM), lists (the page's repeating rows with a live-tested define_function payload for writ_browser_compose), map (the evidence of the build the session is bound to).
  • writ_browser_network — Searches (operation=search, query, method) or reads in full (operation=detail, index) the backend requests the page made after capture_network: the site's real API.
  • writ_browser_compose — Authors the workflow in an open session beyond a recording: named API functions (define_function with a `flow`, preferred in an API build, or a captured call's index or a lists payload; live-tested as defined; compile_function for an authenticated request), set_inputs, add_steps, test_function, remove_function, remove_step, list.