VibeHost
Guides

Hermes Agent

Use VibeHost from inside Hermes Agent, Nous Research's open-source self-improving terminal agent. MCP server or vibehost CLI as a tool.

Hermes Agent (github.com/NousResearch/hermes-agent) is Nous Research's open-source coding agent — built around a self-improving skill loop, native MCP client, and multiple terminal backends (local, Docker, SSH, Modal, Vercel Sandbox, etc.). MCP setup reference. It talks to VibeHost two ways: through our MCP server (interactive, OAuth) or via the vibehost CLI wrapped as a tool (scripted, PAT).

Hermes reads MCP config from ~/.hermes/config.yaml. Add VibeHost under mcp_servers:

mcp_servers:
  vibehost:
    url: "https://api.vibehost.com/mcp"

Restart Hermes (or let auto-reload kick in — Hermes watches the config file). First tool call opens your browser for OAuth. After approval, Hermes has the full VibeHost tool surface — deploy, promote, rollback, list logs, manage custom domains.

In a Hermes session, just describe what you want:

Deploy this directory to VibeHost as a new app called my-hermes-app.

Hermes picks the right tools (create_app + create_deployment) and returns the live URL.

Hermes also supports per-server tool filtering with include / exclude lists if you want to expose only a subset of VibeHost's tools to the agent.

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

Hermes can shell out to vibehost deploy ./dist, vibehost app inspect, etc. through its terminal-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 HermesMCP
Scripted / unattended workflowsCLI + PAT
You want every write to prompt for confirmationMCP
You want raw stdout / stderr from the deployCLI

Both can coexist.

See also

On this page