Turn any website into an MCP tool

Enter a site and a goal to generate a ready-to-paste MCP server config your AI agent can read. A scaffold to start from - connect a real Writ workflow to make it act and transact.

Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

run ▸ generate mcp.json 3

This generates a scaffold. The stub describes the tool; a real Writ workflow makes it log in, act, and return structured output. Sample keys use the wt_ prefix.

seq ▸ how it works 7

how it works

From a goal to a callable tool

The generator gives you the shape. Writ gives you the action.

Describe the site and goal

Enter the URL and what you want an agent to do there.

Generate the config

We scaffold an MCP server entry and a tool stub with a typed input.

Paste into your client

Drop it into your MCP client config (Claude, Cursor, or your own).

Connect a real workflow

Wire it to a Writ workflow so the tool actually logs in, acts, and returns structured output.

dif ▸ why writ mcp 11

what's different

A tool that acts, not just reads

Most website-to-MCP tools stop at page text. A Writ tool signs in and gets the job done - on your own authenticated account.

Logs in for you

Handles the login, TOTP, and mailbox OTP so agents reach pages behind an account, not just the public web.

Clears the hard web

Two-factor prompts and dynamic, JS-rendered pages that ordinary tools choke on - on sites with no API.

Acts, then transacts

Fills forms, clicks, completes multi-step tasks, and can buy - driven by a real Writ workflow, not a guess.

Returns typed JSON

A typed input schema in, structured JSON out - so your agent gets a clean, predictable result every run.

nb ▸ a real scaffold 15

A scaffold, not a finished server. The config is ready to paste, but it won't act until you connect a real workflow. Writ MCP exposes authenticated, action-taking tools to Claude, Cursor, and any MCP client - for sites that have no API. Read the publishing guide.

q ▸ common questions 19

faq

Questions about the generator

Is the generated config a working server?

It is a scaffold: a valid MCP server entry plus a tool stub with a typed input schema, ready to paste into an MCP client. To make the tool actually act and transact on a site, connect it to a real Writ workflow - that is the part that logs in, navigates, and returns structured output.

Which MCP clients does this work with?

Any MCP-compatible client. The output follows the standard mcpServers config shape used by Claude, Cursor, and other clients. Point the client at a Writ MCP server URL and authenticate with a scoped wt_ key.

What makes a Writ MCP tool different from a read-only one?

Most website-to-MCP tools only read page text. A Writ tool acts: it logs in, fills forms, clicks, handles 2FA on your own authenticated account, completes multi-step tasks, and returns typed JSON. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

Do I need an account to use the generator?

No. The generator is free and needs no login. You only need a Writ account when you want to connect a real workflow and run the tool for real.

go ▸ publish an mcp tool 23

get started

Make the tool actually act

Connect a Writ workflow and your agent can log in, transact, and get structured output. Start free.

Get started Explore Writ MCP