VS Code · MCP
Copilot built it in VS Code.
Send an address, not a file.
Agent mode will happily build a report, a dashboard or a prototype as a single HTML file. Add one MCP server and it can also put that file where the right people can open it.
No card required · Unlimited viewers · Secure by default
The situation
What happens to VS Code's output today
The preview is the only viewer
It looks right in the editor's preview pane and exists nowhere else. Everyone who asked for it is waiting on a file.
A file is a copy the moment it leaves
You attach index.html. It gets forwarded. When the agent rebuilds it with the new numbers, the people holding the old one never find out.
Hosting it properly is a project
A domain, an auth layer, permissions and a way to update in place — for something that might be thrown away on Friday. So it stays on localhost.
Setup
Connect VS Code
Publish from Copilot's agent mode to a URL your organisation can open, with the version history kept.
Opens VS Code and asks you to add the server; you approve the connection in your browser. If nothing happens, follow the steps below.
- 1.
Or add it to .vscode/mcp.json
{ "servers": { "deliverd": { "type": "http", "url": "https://deliverd.dev/api/mcp" } } }In the project for one repository, or in your user settings for all of them. The key is “servers” — VS Code ignores an “mcpServers” block.
- 2.
Start it
Run “MCP: List Servers” from the command palette, start the server, and approve the connection in your browser.
No token is written anywhere. Deliverd implements the MCP authorization spec, so the client registers itself and you approve it in a browser — and removing someone from your organisation cuts their connection off at once, rather than whenever a token happens to expire.
What you get
Once it is connected
Everything below is what happens to a report after VS Code publishes it.
A URL instead of a file
The report lands on an address you can send. It stays put, so a link you shared last month still opens the report — not a stale copy of it.
Behind your own sign-in
Readers authenticate with the identity your organisation already uses, including SAML single sign-on. Nobody gets a password to remember or a file to lose.
You choose who, in plain English
“Finance team”, “Sarah Jones”, “everyone”. Ambiguous phrases come back as a list to pick from rather than a guess, so a board pack cannot land in the wrong inbox.
Every version kept
Publishing again updates the same URL and keeps what was there before. You can see what changed, and roll back if the new one is wrong.
Comments on the passage, not the page
A reader selects a sentence and comments on it. Your agent can read those threads, fix what they point at, and mark them resolved.
A record of who opened it
Views, versions, access changes and share links are all written to an audit trail you can export.
Questions
VS Code and Deliverd.
What does the Add to VS Code button do?
It opens VS Code and asks you to add the server entry, exactly as if you had written it into .vscode/mcp.json yourself. Nothing is written until you confirm, and the entry holds only a URL.
Where does the config go if I add it by hand?
.vscode/mcp.json inside a project, or your user settings for every project. The key is “servers” — VS Code's file is not the same shape as Cursor's, and an “mcpServers” block is ignored.
Do I need a token?
No. VS Code registers itself with the server and opens a browser for you to approve the connection. Removing you from the organisation cuts the connection off at once.
Does this work with the Insiders build?
Yes — the second button opens Insiders instead. Both builds read the same mcp.json format.
Stop sending VS Code’s output around as files.
Publish it to an address instead, and let the people who need it open it with the sign-in they already have.