Give ChatGPT real web actions on any site
Give ChatGPT real web actions on any site (login, forms, multi-step tasks) over MCP.
https://api.usewrit.app/mcp Writ tools, inside the chat, through a connector
ChatGPT connects to Writ as a remote MCP connector and signs in with OAuth — there is no config file and no API key to paste. Once connected it can read a page, collect a site, build an API from one, or run a workflow you saved, including on sites you are signed in to.
- 1
The connection is OAuth, so nothing secret is typed into a settings box and you can revoke it from Writ at any time.
- 2
Your logins stay in Writ as sealed identities: ChatGPT can act as you on a site without ever seeing a password or a one-time code.
What ChatGPT can do with a Writ tool
Each tool is an API Writ built from one sentence: it acts on the live site (a real browser only when the site needs one), then returns structured output.
Authenticated actions
ChatGPT acts on your own accounts - log in, pass TOTP and mailbox-OTP 2FA, then click, fill, and submit. Not a read-only crawl.
Any site, no API required
Each tool was built and tested on the live site, so it reaches sites that ship no API at all - internal dashboards, vendor portals, no-API web apps.
Typed, structured output
Every tool returns typed JSON ChatGPT can read and act on - fields, not raw page text - so the agent can chain the result into the next step.
Add Writ to ChatGPT over HTTP
Paste the server block, authenticate with a scoped wt_ key, and every saved workflow is callable - the ones you pin appear as their own tools.
https://api.usewrit.app/mcp - 1Step 1
In ChatGPT, open Settings → Connectors and turn on developer mode.
- 2Step 2
Create a connector and paste the Writ MCP URL above.
- 3Step 3
Sign in to Writ when ChatGPT opens the consent page — no API key to paste or rotate.
Why this setup is different. This client connects over OAuth, so nothing secret is ever typed into a settings box: ChatGPT registers itself, you approve the connection on Writ’s own consent page, and the access it gets is limited to reading and running your workflows. Revoke it any time from Writ under Settings → Connections.
Every workflow is callable; the ones you pin are tools. Anything you save in Writ - an API Scribe built, a ready-made one you rebuilt, a recorded step - is callable from ChatGPT through writ_run_workflow; pin a workflow and it shows up as its own tool with a typed schema. See how MCP tools work or read the developer MCP docs.
Login, 2FA, and dynamic pages - handled
The sites worth automating are usually the hard ones. ChatGPT gets tools that handle them.
Because every tool runs the real site flow (a real browser when the site needs one), ChatGPT can complete tasks a read-only MCP server never could: sign in, pass two-factor, navigate pages that render with JavaScript, and submit. It runs on your own accounts and credentials, on sites you are authorized to use.
Three ways to get a ChatGPT tool
All three produce the same callable API - which becomes its own tool the moment you pin it.
Describe it
Tell Scribe your goal in one sentence; it drives the live site, tests the result and hands you the API.
Pick a ready-made API
The marketplace lists APIs other people built and Writ checks daily: call one as is in the cloud, or rebuild it locally on Writ Desktop.
Record the difficult part
When a login or a picker needs your hands, click through just that step in a real browser; Writ builds the rest around it.
Use Writ tools in any MCP client
ChatGPT + Writ questions
How do I add Writ tools to ChatGPT?
What can ChatGPT actually do with a Writ MCP tool?
Does it handle login and 2FA in ChatGPT?
Is this read-only, like most website-to-MCP servers?
Give ChatGPT tools that act
Describe the site once; Writ builds the API, and your agent calls it as an authenticated, action-taking MCP tool. Get started free.