Give VS Code (Copilot) real web actions on any site
Give Copilot agent mode real web actions on any site (login, forms, multi-step tasks) over MCP.
{
"servers": {
"writ-cloud": {
"type": "http",
"url": "https://api.usewrit.app/mcp"
}
}
} Writ tools, inside Copilot agent mode
Copilot in agent mode speaks MCP. Point VS Code at your Writ server and the agent can pull live data or run a saved workflow while it works on the code — instead of you pasting a fixture in by hand.
- 1
The workspace config holds only a URL, so the file is safe to commit: the sign-in happens in the editor over OAuth.
- 2
A site with no API becomes a callable endpoint your code can keep using after the session ends.
What VS Code (Copilot) 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
VS Code (Copilot) 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 VS Code (Copilot) can read and act on - fields, not raw page text - so the agent can chain the result into the next step.
Add Writ to VS Code (Copilot) 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.
{
"servers": {
"writ-cloud": {
"type": "http",
"url": "https://api.usewrit.app/mcp"
}
}
} - 1Step 1
Create .vscode/mcp.json in the workspace with the block above.
- 2Step 2
Open the Copilot chat view and switch to Agent mode.
- 3Step 3
Approve the Writ sign-in when VS Code opens it — the config file holds no key.
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 VS Code (Copilot) 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. VS Code (Copilot) gets tools that handle them.
Because every tool runs the real site flow (a real browser when the site needs one), VS Code (Copilot) 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 VS Code (Copilot) 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
VS Code (Copilot) + Writ questions
How do I add Writ tools to VS Code (Copilot)?
What can VS Code (Copilot) actually do with a Writ MCP tool?
Does it handle login and 2FA in VS Code (Copilot)?
Is this read-only, like most website-to-MCP servers?
Give VS Code (Copilot) 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.