Deploy from GitHub Copilot CLI

GitHub Copilot CLI brings Copilot to the terminal. It speaks MCP, so it can call VibeHost tools directly. It can also shell out to vibehost when a script gives better control than tool calls.

Option 1: MCP server (recommended for interactive use)

Copilot CLI reads MCP servers from ~/.copilot/mcp-config.json:

{
  "mcpServers": {
    "vibehost": {
      "url": "https://api.vibehost.com/mcp",
      "type": "http"
    }
  }
}

Restart Copilot CLI. First tool call opens your browser for OAuth. After approval, Copilot has access to every VibeHost tool, so it can deploy, promote, roll back, read logs, and manage custom domains.

In a Copilot session:

Deploy this directory to VibeHost as a new app called my-copilot-app.

Copilot creates the app, uploads the files, deploys them and returns the live URL. The tool calls behind that are described once, in Choosing an upload path.

Option 2: CLI as a tool (recommended for scripts and CI)

Install the CLI:

curl -fsSL -o vibehost-install.sh https://vibehost.com/install.sh
cat vibehost-install.sh
sh vibehost-install.sh && rm vibehost-install.sh

Authenticate with a Personal Access Token:

export VIBEHOST_TOKEN=$(pass vibehost/pat)
vibehost whoami --json

Copilot CLI can shell out to vibehost deploy ./dist etc. Every command takes --json and returns {ok, data | error}, which an agent can parse without reading prose. See the CLI reference.

When to pick which

Both can coexist.

See also

• MCP server lists every tool and explains authentication.
• Personal access tokens covers PAT setup for CI and scripts.
• Sibling coding agents: Claude Code, Codex CLI, Cursor, Antigravity, Antigravity CLI, Windsurf, OpenCode, Hermes Agent, Grok Build