Every workflow, a tool.

The writ-cloud MCP server turns your account into tools an AI agent can call: twenty-five built-in tools for recording, workflows, data, crawls, monitors and automations — plus one tool per saved workflow. Auth is a wt_ API key.

connect ▸ one url

One server for the whole account.

Transport is Streamable HTTP: every message is a POST to /mcp on api.usewrit.app — JSON-RPC 2.0, a single object or a batch array per request. GET /mcp is a health probe. Authenticate with Authorization: Bearer and a wt_ API key; this endpoint takes no OAuth.

{
  "mcpServers": {
    "writ-cloud": {
      "type": "http",
      "url": "https://api.usewrit.app/mcp",
      "headers": {
        "Authorization": "Bearer wt_xxxxxxxxxxxx"
      }
    }
  }
}

# Confirm the server is reachable and see the tools it exposes
curl -X POST https://api.usewrit.app/mcp \
  -H "Authorization: Bearer $WRIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'

tools ▸ twenty-five built in

Twenty-five tools, every account.

The built-in set covers the loop an agent actually runs: find a workflow, run it, read and search what it collected, schedule it, expose it, crawl, watch, automate.

tools ▸ one per workflow

Each saved workflow is its own tool.

tools/list also carries one run_<name> tool per saved workflow, its input schema derived from the workflow’s declared inputs. Names are slugified; a collision dedupes to _2, _3; the built-in writ_* names always win. Every run tool takes the same three controls:

rules ▸ no side door

A tool call is an API call.

MCP adds a protocol, not a side door. Every tool call executes under exactly the rules of the REST API called with the same key: tenant isolation, key scopes, plan limits and metering all apply unchanged.

publish ▸ /mcp/{slug}

Published servers at /mcp/{slug}.

Publishing also mints standalone MCP servers at /mcp/{slug} — Streamable HTTP on POST /mcp/{slug}, with optional SSE at GET /mcp/{slug}/sse. They accept a wt_ key or an OAuth access token, so you can hand one workflow to a client without handing over an account key.

OAuth for MCP clients

A rejected call answers with WWW-Authenticate whose resource_metadata points at …/.well-known/oauth-protected-resource/mcp/{slug} — standard MCP OAuth discovery. The authorization-server metadata lives at GET /api/oauth/.well-known/oauth-authorization-server, and clients self-register through RFC 7591 dynamic registration at POST /api/oauth/register — public PKCE clients only, no client secret. Built for Claude custom connectors, Cursor, and any client that speaks the flow.

Tool configuration

Each published tool is a small contract; the server slug is always derived from the name.

Published MCP tools are capped per plan (the max_mcp_tools limit) — a cap on how many tools you publish, never on how often they are called:

faq

MCP questions, answered.

reference ▸ next

Keep wiring.