Deploy from Antigravity IDE

Antigravity IDE, Google's agentic IDE, can talk to VibeHost in two ways: through the MCP server, where the agent picks VibeHost tools itself, or through the vibehost CLI for local shell workflows and CI.

Option 1: MCP server (recommended for interactive use)

Antigravity creates ~/.gemini/config/mcp_config.json on first launch. Open it in your editor:

open -e ~/.gemini/config/mcp_config.json

Then add:

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

If you already have other MCP servers, add only the vibehost entry under the existing mcpServers object.

Antigravity uses serverUrl for Streamable HTTP MCP servers. Most other clients call this field url.

Now load the config and authenticate from inside Antigravity:

1. Open Antigravity.
2. Click Settings in the bottom-left corner, then click Customizations in the left sidebar.
3. Find the Installed MCP Servers section in the panel.
4. Click Refresh at the top of that section. vibehost appears in the list with this red message under it:

   Error: calling "initialize": sending "initialize": Unauthorized

   That's expected before authentication. Continue to the next step.
5. Click Authenticate next to vibehost. A browser tab opens on api.vibehost.com.
6. Approve the request. Copy the authorization code (it's prefixed with mcpc_), paste it into the Antigravity prompt, and submit.
7. Antigravity refreshes vibehost automatically. The Unauthorized error disappears and you'll see the tool count and a Sign out button (list_workspaces, create_app, deploy, ...).

Verify in an Antigravity chat:

List my VibeHost workspaces.

If Antigravity calls list_workspaces and returns your workspaces, the integration is live. From here you can ask for full flows:

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

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

Option 2: CLI through shell commands (recommended for scripts)

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

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. Antigravity can then call vibehost deploy ./dist, vibehost app inspect, etc. through its shell interface.

For CI or unattended scripts, use a Personal Access Token as a secret environment variable instead:

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

Every CLI command takes --json and returns {ok, data | error}, which an agent can parse without reading prose. See the CLI reference.

When to pick which

Both can coexist.

See also

• MCP server lists every tool and explains authentication.
• Personal access tokens covers PAT setup for CI and scripts.
• Sibling coding agents: Antigravity CLI, Claude Code, Codex CLI, Cursor, Windsurf, OpenCode, Copilot CLI, Hermes Agent, Grok Build