VibeHost
Guides

Deploy from OpenCode

Use VibeHost from inside OpenCode, the open-source terminal AI coding agent by SST. MCP server or vibehost CLI as a tool.

OpenCode is an open-source terminal coding agent built by the SST team. It is heavily adopted and model-agnostic, and it supports 75+ LLM providers. It talks to VibeHost two ways: through our MCP server (interactive, OAuth) or through the vibehost CLI wrapped as a tool (scripted, PAT).

Add VibeHost to your OpenCode config (~/.config/opencode/opencode.json):

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

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

In an OpenCode session, describe what you want:

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

OpenCode 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.

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

OpenCode can shell out to vibehost deploy ./dist, vibehost app inspect, 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

SituationUse
First-time setupMCP (browser sign-in, no token to paste)
Interactive deploys inside OpenCodeMCP
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