xhostd

View saved version →

---
name: xhostd
description: >-
  Use when the user wants to deploy a website, API, or service to an HTTPS
  URL, host a static site, create a preview URL for a branch, or check a
  deploy's status or logs, and when the user asks for work on an xhostd app
  or account, such as its database, environment variables, secrets,
  snapshots, or custom domains. Covers the lifecycle: create app → push code
  → deploy → live HTTPS URL, plus channels, env, snapshots, domains, and
  browser-based sign-in.
---

# xhostd hosting

xhostd is hosting designed for agents. You create an app, push its code to the git repo the app owns, and deploy it. Every app gets a production HTTPS URL; named channels give preview URLs. The same remote MCP tools are available on Claude Code, claude.ai, Codex, Cursor, ChatGPT, and other OAuth-capable clients. The procedure below is identical across clients, except in a client with no shell access: it has no git, and there `commit_files` writes the commit. This skill names each tool by its bare name, such as `deploy`. Your client might add a prefix of its own; call the tool whose name ends with the bare name.

The user's instructions take precedence over guidelines provided in a skill.

## Authentication

There are two ways to hold an authenticated session. Pick the one that matches who is present.

**A. A person is present: OAuth.** The xhostd connector (claude.ai, the Claude desktop app, and Claude Code) and the plugin open `/auth/login` in a browser. The user signs in with a username or email and password, or uses Google as an alternative. A preprovisioned account signs in directly without signup, email verification, multifactor authentication (MFA), or SMS. Call the tools. If a tool reports unauthenticated:
- **Claude Code:** tell the user to run `/mcp`, select the xhostd entry whose tool reported unauthenticated (**claude.ai xhostd**, **xhostd**, or the plugin's xhostd entry), and choose **Authenticate**.
- **Codex:** refresh or reconnect the xhostd plugin, then retry the first tool call. Browser-based sign-in opens on its own.
- **Cursor:** tell the user to open **Customize** in the sidebar, find the **xhostd** MCP server, and turn it on or follow its sign-in prompt. A browser opens for sign-in. Then retry the first tool call.
- **claude.ai and the Claude desktop app:** tell the user to open **Settings → Connectors**, select **xhostd**, and reconnect. If it isn't listed, search for xhostd in the Connectors directory and choose **Connect to Claude**.
- **ChatGPT:** tell the user to reconnect xhostd in ChatGPT's app settings.

Never ask a person for an API token to sign in on this path. The OAuth session carries one for the tools. The one exception is work outside the tools — an HTTPS git push, a download link, `psql` — which reads `$XHOSTD_TOKEN` from the shell. When that variable is unset and no SSH key pushes for the account, write the commit with `commit_files`, as **Pushing code with git** describes. For other work, ask the person to create a token on the console /tokens page and export it as `XHOSTD_TOKEN`; never ask them to paste the value into the conversation.

**B. No person is present.** A plugin or connector session signs in through path A. An agent that runs with no person at a browser, outside a plugin or connector, can open an account of its own with an SSH key. That setup changes the machine's client configuration, so a person decides on it. [Register as an agent](https://docs.xhostd.com/guides/register-as-agent) describes the steps. `get_stats` with `view="overview"` reports such an account's limits.

Such an account has no email, so no person can open the console for it. No tool binds an address: binding runs over the HTTP API with the token that `POST /registrations` or `POST /auth/ssh-key` returned, because only that token carries the `email:bind` scope. When a person gives you an address, send `POST /me/email-verifications` with `{"email": "<address>"}` and the bearer header; the platfor

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 21 — file references are metadata, not package contents.