VibeHost
Guides

Antigravity

Use VibeHost from inside Antigravity, the agentic IDE. MCP server for native tool calls or the vibehost CLI as a tool.

Antigravity is an agentic IDE. Like other coding agents, it talks to VibeHost via the MCP server for native tool calls, or via the vibehost CLI when you'd rather drive it through plain shell commands.

In Antigravity, open Settings → Customizations → Open MCP Config (or the agent-session sidebar's ... → MCP Servers → Manage MCP Servers → View raw config). Add this entry to mcp_config.json:

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

Save. Antigravity reloads the config automatically. First tool call opens your browser for OAuth; after approval, Antigravity has the full VibeHost tool surface — deploy, promote, rollback, list logs, manage custom domains.

Note: Antigravity uses serverUrl (not url) for HTTP-based MCP servers — this differs from most other clients.

In an Antigravity chat, just describe what you want:

Build this directory and deploy it to VibeHost as a new app called my-antigravity-app.

Antigravity picks the tools (typically 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

Antigravity can now call vibehost deploy ./dist, vibehost app inspect, etc. through its shell-tool interface. 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 inside AntigravityMCP
Scripted / unattended workflowsCLI + PAT
You want every write to prompt for confirmationMCP
You want raw stdout / stderr from the deploy stepCLI

Both can coexist.

See also

On this page