hostwares-mcp

Deploy and manage Hostwares from Claude, Cursor, ChatGPT, or any MCP client — in plain language.

Most people don't need this package. Hostwares runs a hosted MCP server. If your client supports remote MCP (Claude Code, Claude Desktop, Cursor, ChatGPT), connect straight to it and skip the install:

claude mcp add --transport http hostwares https://mcp.hostwares.com \
  --header "Authorization: Bearer sk_your_key_here"

This package exists for clients that only speak local stdio.

What it does

A thin stdio bridge to https://mcp.hostwares.com. It defines no tools of its own — it fetches the tool list from the server at startup and forwards calls there.

That matters: the previous version shipped its own copy of the tool definitions, so the package silently drifted from the platform whenever a tool changed and users were stuck on a stale list until they upgraded. Now the server is the single source of truth and new tools appear without republishing anything.

Related MCP server: CreateOS MCP

Setup

1. Create an API key at Dashboard → API Keys.

2. Add it to your client's MCP config.

Claude Desktop (claude_desktop_config.json) / Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "hostwares": {
      "command": "npx",
      "args": ["-y", "github:Hostwares/hostwares-mcp"],
      "env": { "HOSTWARES_API_KEY": "sk_your_key_here" }
    }
  }
}

Once published to npm you can use ["-y", "hostwares-mcp"] instead.

Usage

> Deploy this repo to Hostwares as my-app
> Why is my-app returning 502? Check the logs
> Set DATABASE_URL on my-app
> Point app.example.com at my-app

Tools

deploy · list_sites · get_status · get_logs · set_env · add_domain · create_database · list_databases · restart_site

All are backed by the same services as the dashboard and the hw CLI, so results are identical however you drive the platform.

Billing

Hosting is pay-first. deploy creates the site plus an invoice and returns an invoiceUrl; the build starts automatically once that invoice is paid. Your assistant will give you the link. The site is not live until get_status reports it running.

Environment

Security

Your key is read from the environment and sent only to Hostwares. It is never written to stdout — stdout is the JSON-RPC channel — and never logged. A key can only reach resources owned by the account that created it. Revoke anytime from Dashboard → API Keys.

Privacy Policy

Full policy: https://hostwares.com/privacy

What this bridge collects. Nothing. It runs on your machine, holds no database, writes no logs to disk, and sends nothing to any third party. It is a stdio-to-HTTP proxy: it forwards each JSON-RPC message to https://mcp.hostwares.com and returns the response unchanged.

What is transmitted. Only the arguments of the tool you invoke — a site id, a domain name, or environment-variable values you ask it to set — plus your API key for authentication, sent over HTTPS to Hostwares. Conversation content is not sent; the bridge never sees your chat.

What Hostwares stores. Your account data (sites, databases, domains, invoices) and an audit record of actions taken with your API key, so you can see what was changed and when.

Third-party sharing. None. Hostwares does not sell or share account data. Deployments run on infrastructure operated by Hostwares' hosting providers, as described in the full policy.

Retention. Account data is retained while the account is open, and is deleted on request or after account closure, per the full policy.

Your API key. Read from the HOSTWARES_API_KEY environment variable, never written to disk or to stdout by this bridge. Revoke it at any time at https://hostwares.com/dashboard/api-keys.

Contact. support@hostwares.com

Development

npm install
npm run build
HOSTWARES_API_KEY=sk_... node dist/index.js

Docs: https://hostwares.com/docs/mcp · License: MIT