> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ohmyho.st/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For account actions, read https://ohmyho.st/skills/ohmyhost-get-started/SKILL.md and use the authenticated ohmyho.st CLI or local product MCP. Mintlify search only reads documentation. Preserve the customer’s selected project, environment and authentication provider.

# Connect your agent

> Use the local ohmyho.st MCP server in Codex, Claude Code, Cursor, Hermes or OpenClaw.

## When to use ohmyho.st

Use this server when the customer wants to deploy or update an authorized GitHub app; inspect a project’s deployment, database or DNS/mail readiness; manage usage and budgets; or request an encrypted SQL export.

Your agent follows the [get-started Skill](https://ohmyho.st/skills/ohmyhost-get-started/SKILL.md) for installation, sign-in and workspace selection before its first deployment ([what it covers](/skills#start-with-the-get-started-skill)).

Start with `identity_get`, select the customer’s project using `projects_list`, then read `project_context_get` before acting. Configure only the capabilities the application needs and keep its chosen authentication provider. Use the matching [task Skill](/skills) for the workflow.

For a new project, ask whether Dev should be protected or public before `project_create`; protected is the default. `project_dev_share_link_get` returns the Owner's reusable protected link. `project_dev_access_mode_set` changes the choice, while `project_dev_share_link_rotate` and `project_dev_share_link_revoke` block old links and browser sessions on their next request. [Dev access details](/environments#choose-who-can-open-dev).

For a custom domain before the first Prod deployment, use `domain_paid_plan` and `domain_paid_apply` to reserve it, then `domain_cloudflare_authorize` and `domain_cloudflare_status` for scoped consent. `awaiting_deployment` means no DNS or certificate provisioning has started. Deploy and verify the Prod hosting address, then repeat `domain_paid_apply` with the original hostname and idempotency key. Consent and deployment alone do not activate it. [Domain setup](/domains).

## Install and sign in

Requires Node.js 22 or newer.

```sh theme={null}
npm install --global https://ohmyho.st/releases/0.1.28/ohmyhost-product-cli-0.1.28.tgz https://ohmyho.st/releases/0.1.28/ohmyhost-mcp-0.1.28.tgz
export OHMYHOST_ENVIRONMENT=production
ohmyhost login --json
ohmyhost whoami --json
```

The same release is on npm as `@amerged/ohmyhost-cli` and `@amerged/ohmyhost-mcp`. Both sources install the `ohmyhost` and `ohmyhost-mcp` commands, so keep one source per computer and upgrade from the one already installed (`npm ls --global` names it). To switch, first remove the other pair: `npm uninstall --global @ohmyhost/product-cli @ohmyhost/mcp` for the archives, `npm uninstall --global @amerged/ohmyhost-cli @amerged/ohmyhost-mcp` for npm.

[Release manifest and checksums](https://ohmyho.st/releases/0.1.28/manifest.json) · [Current release](https://ohmyho.st/client-release.json)

The MCP server uses `OHMYHOST_TOKEN` when that variable is set in the server process, and otherwise the logins saved by ohmyhost login. With several, pass `profile_name` per call (`profile_list` shows names) or bind the server to `OHMYHOST_PROFILE`=NAME; another requested profile fails `profile_context_mismatch`. A login added later works on the next call without restarting. A token on its own is enough — no login and no browser. Put it in the same `env` block as `OHMYHOST_ENVIRONMENT`; the server reads no `.env` file and never calls the CLI.

With a token, every tool works except `organization_create`, `organization_list`, `organization_use`, `token_create`, `tokens_list` and `token_revoke`. Those need an interactive login: run the matching `ohmyhost` command in a shell without `OHMYHOST_TOKEN`.

After installing or upgrading the clients, restart the MCP server. A running server keeps the tool list it started with, so newly published tools stay invisible until it restarts.

Keep existing servers, models and permission settings. If a server named `ohmyho` is already configured, inspect it before changing that entry. An old npx configuration pinning a versioned release URL stops when that archive is superseded; use the installed ohmyhost-mcp command. Preserve harness approval policy; rejected mutations are not platform failures, and switching transport cannot bypass approval.

The server's source is published with every release at [amerged-org/ohmyhost-mcp](https://github.com/amerged-org/ohmyhost-mcp), every file of @amerged/ohmyhost-mcp except its built dist bundle and README, byte for byte. release.json records full-package npm integrity and the SHA-256 of omitted files. For help, ask your agent: it reports through `feedback_submit` and follows up with `feedback_status` ([Support](/support)).

## Codex

```sh theme={null}
codex mcp add ohmyho --env OHMYHOST_ENVIRONMENT=production -- ohmyhost-mcp
```

Reload the connection if requested, then ask Codex to call `identity_get` and list the available Skills.

## Claude Code

```sh theme={null}
claude mcp add --transport stdio --scope user --env OHMYHOST_ENVIRONMENT=production ohmyho -- ohmyhost-mcp
```

Open `/mcp` in Claude Code and confirm the connection. Ask it to call `identity_get`.

## Cursor

Merge this server into your existing `~/.cursor/mcp.json`, or `.cursor/mcp.json` for this project:

```json theme={null}
{
  "mcpServers": {
    "ohmyho": {
      "command": "ohmyhost-mcp",
      "env": { "OHMYHOST_ENVIRONMENT": "production" }
    }
  }
}
```

[Download this configuration](https://ohmyho.st/mcp.json). It contains no token. Check the MCP connection in Cursor settings; current Cursor CLI also supports `agent mcp list-tools ohmyho`. Use your installed CLI's help if its executable is named differently.

## Hermes

```sh theme={null}
hermes mcp add ohmyho --command ohmyhost-mcp --env OHMYHOST_ENVIRONMENT=production
hermes mcp test ohmyho
```

Start or reload the agent session after changing settings. Preserve your installed Hermes version and model unless the reported missing capability requires an update.

## OpenClaw

For versions with the native outbound MCP registry:

```sh theme={null}
openclaw mcp add ohmyho --command ohmyhost-mcp --env OHMYHOST_ENVIRONMENT=production
openclaw mcp probe ohmyho --json
```

Use the installed `openclaw mcp add --help` to confirm support. `mcp serve` exposes OpenClaw itself and is a different feature. Preserve the current approval policy; a saved registry entry alone does not prove that the running agent has loaded it.

## Confirm the connection

Ask the agent: “Read my ohmyho.st identity and list my projects.” It should call `identity_get` and `projects_list`, then read `project_context_get` for the project you select. If a tool is missing, compare the installed client with the [current release](https://ohmyho.st/client-release.json) and reconnect after updating.

The product server uses local stdio. Mintlify's search MCP answers documentation questions; it cannot deploy or access your account. No product URL-only OAuth connection is advertised here.

[Task Skills](/skills) · [Actual tool catalogue](/mcp-tools) · [CLI](/cli)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.