INDIVIDUAL MCP TOOL

writ_devices

The user's linked Writ desktops (there can be several): which are connected right now, and how many local workflows and personas each offers.

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_devices and invoke it with your own arguments.

{}

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.

CONNECT WITH APPROVAL

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.

writ_browser_use — A REAL CLOUD BROWSER FOR A TASK ON A WEBSITE: the user's own signed-in account (email, social, shop, bank or work portal, through a persona_id from writ_personas: the password stays sealed in Writ, and sessions never ask for a password), a click, form, submit, search inside an app, setting change, booking or post, or a page a plain fetch cannot open (login wall, 403, CAPTCHA).
writ_record_website — Records a repeatable website task as a workflow that replays on demand.
writ_website_to_api — Turns a website into a callable API: the one tool for this, every lane.
writ_discovery_status — Status of a build started by writ_website_to_api.
writ_browser_act — Runs one batch of actions on an open browser session and returns the fresh page.
writ_browser_context — Reads context for an open browser session.
writ_browser_network — Searches or reads the requests the live page has made: the site's real backend API, as opposed to its HTML.
writ_browser_compose — Authors the workflow being built in an open browser session: named functions, inputs and explicit steps that make what the session drove a real, complex, callable workflow rather than a replay of clicks.