Skip to main content

Hostsmith

Docs Quick start

Quick start

Pick the path that matches your client. Each one ends with the same result: an MCP-capable agent that can publish files to a public HTTPS URL.

AI agents can make mistakes. Review tool calls before approving destructive ones (delete_site, overwrite deploys). You are responsible for the content your agent publishes. Hostsmith and ops42 OU are not liable for damages caused by AI-generated actions - see the Terms of Service.

1. Install the server

Claude (web, Desktop, Cowork)

  1. In Claude, open Customize > Connectors, click + Add, then Add custom connector.
  2. Enter Hostsmith as the name and paste the MCP server URL:
    https://mcp.hostsmith.net/mcp
  3. Click Continue, finish adding the connector, then connect it. Claude opens Hostsmith in your browser to authorize the connector against your Hostsmith account.

Claude Code, Cursor, Cline, Windsurf, Zed

Add this entry to your client's MCP config (file location varies by client - see the client setup page):

{
  "mcpServers": {
    "hostsmith": {
      "command": "npx",
      "args": ["-y", "@hostsmith/mcp-server"]
    }
  }
}

The first tool call opens your browser to authorize the server against your Hostsmith account.

Other Streamable-HTTP clients

Point your client directly at the hosted server:

{
  "mcpServers": {
    "hostsmith": {
      "url": "https://mcp.hostsmith.net/mcp"
    }
  }
}

The client handles OAuth automatically.

If you prefer self-hosting, see Local HTTP.

2. Authorize

The first time your agent calls a Hostsmith tool, your browser opens a Hostsmith consent screen. Sign in (or create a free account), confirm the scopes, and approve. The session lives in your client; you do not paste an API key anywhere.

You only do this once per client. See Authentication for what's happening under the hood.

3. Create a site

In your agent, prompt:

List the domains I can host on, then create a site under the shared us.hostsmith.link domain.

The agent will call list_domains to confirm the domain, then create_site with domain: "us.hostsmith.link". The response contains the new siteId and the public URL.

Pick a different shared domain (eu.hostsmith.link) or one of your custom domains if you prefer - both appear in list_domains.

4. Deploy a file

Now ship something:

Generate a one-page HTML profile of {your topic} and deploy it to that site.

The agent generates index.html and calls deploy_files with { siteId, files: [{ fileName: "index.html", content: "..." }] }. Within seconds, the URL from step 3 is live.

5. (Optional) Iterate

Ask the agent to update the page, add a stylesheet, or attach a custom domain. The same MCP tools handle it - see the recipes for end-to-end examples.

For files larger than ~1 MB or any binary content (PDF, image, video, zip), the agent will use deploy_create_upload + deploy_finalize instead of deploy_files. The MCP server picks the right path based on the size you give it - you don't need to ask.

What's next

  • Tools reference for the full list of what your agent can do.
  • Recipes for ready-made prompts (custom domain, multi-file, partition switch, private sites).
  • Limits and errors for quotas and how to interpret failures.
Previous MCPNextClients