VibeHost
Guides

GitHub Copilot CLI

Use VibeHost from inside GitHub Copilot CLI (15M+ developers). Connect via MCP or the vibehost CLI as a tool.

GitHub Copilot CLI brings Copilot to the terminal. It speaks MCP, so it can call VibeHost tools directly — or shell out to vibehost when scripted control beats tool-calling.

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 the full VibeHost tool surface — deploy, promote, rollback, list logs, manage custom domains.

In a Copilot session:

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

Copilot picks the right tools (create_app + create_deployment) and returns the live URL.

Install the CLI:

curl -fsSL https://vibehost.com/install.sh | 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} for clean agent parsing — see the CLI reference.

When to pick which

SituationUse
First-time setupMCP (OAuth is one-click)
Interactive deploys from CopilotMCP
Scripted / unattended workflowsCLI + PAT
You want every write to prompt for confirmationMCP
You want raw stdout / stderr from the deployCLI

Both can coexist.

See also

On this page