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 — heavily-adopted, model-agnostic, supports 75+ LLM providers. It talks to VibeHost two ways: through our MCP server (interactive, OAuth) or via the vibehost CLI wrapped as a tool (scripted, PAT).
Option 1: MCP server (recommended for interactive use)
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 the full VibeHost tool surface — deploy, promote, rollback, list logs, manage custom domains.
In an OpenCode session, just describe what you want:
Deploy this directory to VibeHost as a new app called my-opencode-app.
OpenCode picks the right tools (create_app + create_deployment) and returns the live URL.
Option 2: CLI as a tool (recommended for scripts and CI)
Install the CLI:
curl -fsSL https://vibehost.com/install.sh | shAuthenticate with a Personal Access Token:
export VIBEHOST_TOKEN=$(pass vibehost/pat)
vibehost whoami --jsonOpenCode can shell out to vibehost deploy ./dist, vibehost app inspect, etc. Every command takes --json and returns {ok, data | error} for clean agent parsing — see the CLI reference.
When to pick which
| Situation | Use |
|---|---|
| First-time setup | MCP (OAuth is one-click) |
| Interactive deploys inside OpenCode | MCP |
| Scripted / unattended workflows | CLI + PAT |
| You want every write to prompt for confirmation | MCP |
| You want raw stdout / stderr from the deploy | CLI |
Both can coexist.
See also
- MCP server — full tool list + auth details
- Personal access tokens — PAT setup for CI / scripts
- Sibling coding agents: Claude Code, Codex CLI, Cursor, Antigravity, Windsurf, Copilot CLI, Gemini CLI, Hermes Agent