Deploy from Grok Build — VibeHost MCP + CLI Setup

Grok Build is xAI's terminal-based coding agent — available to SuperGrok and X Premium+ subscribers. Deploy to VibeHost two ways: through our MCP server (interactive, OAuth) or via the vibehost CLI wrapped as a tool (scripted, PAT).

VibeHost is a private-by-default hosting platform that gives AI-built apps a permanent, shareable URL. It ships an official remote MCP server with 46 tools covering deployments, custom domains, access control, and team collaboration — any MCP-compatible coding agent can connect with a single URL. Grok Build is one of ten officially supported coding agents.

Option 1: MCP server (recommended for interactive use)

Add VibeHost to your Grok Build MCP config. The standard path is .mcp.json in your project root, or ~/.grok/.mcp.json for global access across all projects.

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

Alternative — if your Grok Build version does not pick up the remote server with url, use mcp-remote as a local bridge:

{
  "mcpServers": {
    "vibehost": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.vibehost.com/mcp"]
    }
  }
}

Restart Grok Build or run /mcp in the TUI to reload. First tool call opens your browser for OAuth. After approval, Grok Build has the full VibeHost tool surface — deploy, promote, rollback, list logs, manage custom domains.

Verify the server is discovered:

grok inspect

In a Grok Build session, just describe what you want:

Deploy this directory to VibeHost as a new app called my-grok-app. It's a Vite + React build.

Grok Build 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 | sh

Install the vibehost-deploy skill so Grok Build auto-discovers it via its plugin system:

npx skills add gntc-labs/skills --skill vibehost-deploy -g -y -a grok

Or from inside the Grok Build TUI, run /plugin to search and install vibehost-deploy.

For local interactive use, sign in once with the CLI:

vibehost login
vibehost whoami --json

vibehost login opens a browser approval flow and stores the CLI token in ~/.config/vibehost/config.json.

For CI or unattended scripts, use a Personal Access Token instead:

export VIBEHOST_TOKEN="<your-personal-access-token>"
vibehost whoami --json

Grok Build 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

Both can coexist — set up MCP for interactive sessions and keep the CLI installed for scripts.

FAQ

Does Grok Build support VibeHost natively? Yes. VibeHost is an officially supported MCP integration for Grok Build. Add the MCP server URL to your .mcp.json config and Grok Build discovers all 46 VibeHost tools automatically. No plugin or extension required.

Do I need to install anything to use VibeHost with Grok Build? For the MCP path, no installation is needed — just a config entry and an OAuth approval. For the CLI path, install the vibehost CLI with a one-line curl command, or install the vibehost-deploy skill via /plugin in the Grok Build TUI.

Can I use both MCP and CLI at the same time? Yes. Both can coexist. MCP is best for interactive sessions where Grok Build picks the right tools automatically. The CLI is best for scripted workflows, CI pipelines, or when you want raw stdout/stderr output.

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, Antigravity CLI, Windsurf, OpenCode, Copilot CLI, Hermes Agent