Gemini CLI
Use VibeHost from inside Google's Gemini CLI. MCP server or the vibehost CLI as a tool.
Gemini CLI is Google's open-source terminal coding agent. It supports MCP for native tool calls — or shell out to the vibehost CLI when scripted control is better.
Option 1: MCP server (recommended for interactive use)
Gemini CLI reads MCP servers from ~/.gemini/settings.json:
{
"mcpServers": {
"vibehost": {
"httpUrl": "https://api.vibehost.com/mcp"
}
}
}Restart Gemini CLI. First tool call opens your browser for OAuth. After approval, Gemini has the full VibeHost tool surface — deploy, promote, rollback, list logs, manage custom domains.
In a Gemini session:
Deploy this directory to VibeHost as a new app called my-gemini-app.
Gemini picks the right tools (create_app + create_deployment) and returns the live URL.
Note: Gemini uses httpUrl (not url) for HTTP-based MCP servers.
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 --jsonGemini 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
| Situation | Use |
|---|---|
| First-time setup | MCP (OAuth is one-click) |
| Interactive deploys from Gemini | 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, OpenCode, Copilot CLI, Hermes Agent