Deploy GitHub Copilot

Deploy GitHub Copilot sites with VibeDeploy

GitHub Copilot writes the code inside VS Code, and the finished site sits in your workspace waiting for a home. VibeDeploy gives it one: push the repo and every commit goes live, or add one MCP server and Copilot's agent publishes to an EU-hosted URL for you.

Deploy your GitHub Copilot siteSee pricing

Why VibeDeploy for GitHub Copilot

Copilot's agent mode can scaffold, code and even run your build, but VS Code has no publish button. Since the project already lives in a Git repo, the shortest path to production is a host that builds on every push. VibeDeploy does exactly that from Belgian infrastructure, and adds an MCP route for deploys straight out of the editor.

cloud_sync

GitHub push equals deploy

Your Copilot project is already version-controlled. Connect the repo once and VibeDeploy builds and redeploys on every push, with no CI workflow files to write or maintain.

cable

MCP in VS Code, configured right

Copilot agent mode speaks the Model Context Protocol. One entry in .vscode/mcp.json (with the "servers" key VS Code expects) and the agent can deploy, manage domains and roll out updates without you opening a browser.

shield_lock

Belgian servers, no metering

Sites are served from Belgium with custom domains and automatic SSL on every plan. Flat monthly pricing means frequent AI-driven redeploys cost nothing extra.

How to deploy a GitHub Copilot site

  1. 1

    Prompt the site into existence in VS Code

    Use Copilot's agent mode to build the project. It can run commands like npm run build in the terminal itself, asking for your approval before each one. Any static output works: Vite, Astro, SvelteKit, a static Next.js export, or hand-written HTML.

  2. 2

    Create your VibeDeploy account

    Start a 14-day free trial at vibedeploy.be, no credit card needed. The trial includes custom domains, automatic SSL and EU hosting; paid plans start at €15 per month afterwards.

  3. 3

    Easiest route: connect the GitHub repo

    You are already in the GitHub ecosystem, so use it. Push the project to a repo, choose New Site in the VibeDeploy dashboard and connect it. From then on every push triggers a fresh build and deploy. Working without a repo? Drag the build folder into the dashboard instead.

  4. 4

    Editor route: register the MCP server

    Run 'MCP: Add Server' from the command palette (pick HTTP, then Workspace or Global), or create .vscode/mcp.json by hand. Mind the key: VS Code expects a top-level "servers" object, not the "mcpServers" key other editors use. Then tell Copilot in agent mode to deploy the site to VibeDeploy and it answers with the live URL.

    // .vscode/mcp.json
{
  "servers": {
    "vibedeploy": {
      "type": "http",
      "url": "https://mcp.vibedeploy.be/mcp"
    }
  }
}
  5. 5

    Attach your own domain

    Add the domain in your site settings and create the CNAME record it shows you. SSL certificates are issued automatically, usually within a minute. Until then the site is already reachable at name.vibedeploy.be.

GitHub Copilot hosting at a glance

How GitHub Copilot's default hosting and a generic alternative compare to VibeDeploy.

FeatureGitHub Copilot default / generic altVibeDeploy
Publish path from VS CodeManual / DIYMCP agent tools or git push
Build on git pushWrite your own CI workflowIncluded, zero config
Hosting jurisdictionUsually USEU (Belgium)
Custom domain + SSLManual certificate setupAutomatic on every plan
Cost modelVariesFlat per plan, 14-day free trial

Common questions about deploying GitHub Copilot

Do I need a paid Copilot plan for this?expand_more

No. VS Code has a free Copilot tier, and agent mode with MCP support is generally available. Combined with VibeDeploy's 14-day trial, you can take a project from first prompt to a live URL without paying anyone anything.

VS Code is not picking up my MCP config. Why?expand_more

The most common cause is the wrong top-level key. Cursor and several other tools use "mcpServers", but VS Code reads a "servers" object, either from .vscode/mcp.json in the workspace or from the user-level file behind the 'MCP: Open User Configuration' command. Rename the key, or let the 'MCP: Add Server' flow write the file for you.

Can Copilot run the build before deploying?expand_more

Yes. In agent mode Copilot can execute npm run build in the integrated terminal, and it asks before running any terminal command. Often you do not need it to: connect the GitHub repo and VibeDeploy runs the build on its own infrastructure after every push.

Does this work in Visual Studio too, not just VS Code?expand_more

Copilot agent mode with MCP support is also available in Visual Studio 2022 and later. The configuration steps differ from VS Code, but the endpoint is the same: https://mcp.vibedeploy.be/mcp. And the GitHub build-on-push route works from any editor at all.

What about server-side code?expand_more

VibeDeploy serves static and single-page-app output. A Copilot project that compiles to static files deploys as-is; API routes or server-side rendering need a server host. If Copilot scaffolded a full-stack app, ask it to produce a static export or split the frontend out.

Ship your GitHub Copilot project today

14-day free trial, no credit card. Custom domain in 60 seconds. Hosted in Belgium.

Start free trialCompare plans