Ohmyho.st

What ohmyho.st does

The ohmyho.st MCP server gives an agent an interface to manage resources in an ohmyho.st workspace. Its tools cover deployment planning and execution, deployment inspection and logs, GitHub connection status, PostgreSQL database access, customer domains, production mail, billing controls, identity, and support feedback.

The ohmyho.st MCP server can also inspect project usage-related state, scheduled function runs, database compute settings, issued database credentials, and deployment status. Operations with greater impact are separated into planning, review, and execution steps where the API provides them. For example, project deletion has separate planning and execution tools, and deployments have separate plan and create operations.

How it works

The server runs locally over standard input and output beside the agent. It is installed as the ohmyhost-mcp Node.js command and communicates with ohmyho.st using the access granted by the user. Node.js 22 or newer is required.

Authentication can come from OHMYHOST_TOKEN or from a login saved by ohmyhost login --json. The token takes precedence when present. If multiple saved logins exist, calls can specify profile_name; alternatively, OHMYHOST_PROFILE binds the server to one saved login. The identity_get tool shows which customer, organization, and credential context is active.

Database tools are limited by the service behavior described in the tool set: queries return at most 100 rows and have a five-second timeout, while writes are explicitly authorized INSERT, UPDATE, DELETE, or upsert operations. Database credentials can be issued, listed, and revoked, and compute size can be read or changed.

Setup and configuration

Install the CLI and MCP package globally, select the production environment, and log in:

npm install --global @amerged/ohmyhost-cli @amerged/ohmyhost-mcp
export OHMYHOST_ENVIRONMENT=production
ohmyhost login --json

Register ohmyhost-mcp with the selected MCP client using its stdio configuration. Codex, Claude Code, Cursor, Hermes, and OpenClaw are documented registration targets. Cursor uses the token-free https://ohmyho.st/mcp.json configuration, while the other documented examples start the local command directly.

After registration, reload the client if needed and call identity_get to verify the connection. Keep tokens out of committed or shared MCP configuration; the public configuration only needs the environment setting.

Tools and capabilities

The ohmyho.st MCP server includes tools for:

• Planning and starting deployments, listing deployments, reading deployment details, and retrieving normalized diagnostics.
• Connecting GitHub and checking the workspace connection.
• Querying or writing project-owned Dev and Prod PostgreSQL databases.
• Managing database credentials and selecting standard or performance compute.
• Planning, applying, inspecting, and removing customer-owned domains, including Cloudflare authorization state.
• Configuring production mail domains, checking DNS and delivery readiness, listing recent messages, reading received messages, retrying webhooks, and managing inbound webhooks.
• Creating or inspecting hosted checkout sessions, opening the billing portal, and configuring automatic recharge.
• Submitting support feedback and checking its receipt status.

Limitations and notes

The server acts with the permissions of the selected ohmyho.st login or token. Some actions are owner-only or require owner/admin access. Mail message content is available only before its stated 72-hour expiry, and webhook retries have a shared limit. Database access credentials are time-bound, and revocation ends open sessions and removes the PostgreSQL role.

The ohmyho.st MCP server is distributed through the npm package @amerged/ohmyhost-mcp. The repository mirrors the published package rather than serving as a normal pull-request development repository. Existing installations of older similarly named global packages may need to be removed first because both provide the same command names.