Let any AI assistant publish a website to a live public URL in seconds — free, no account. Claim within 72h to keep it forever.
Agents often assume a hostname needs a connector — it doesn't. This is a public endpoint you POST to directly. Paste this into your agent (click to copy):
The phrases that break the "I need a connector" assumption: "POST directly," "public endpoint — no connector/registry/auth," "GET it first."
| What | URL | Use for |
|---|---|---|
| MCP server | https://mcp.gearhost.com/ | Claude, ChatGPT (connectors), any MCP client |
| OpenAPI 3.1 | https://octane.gearhost.com/preview/?openapi | ChatGPT GPT Actions, Gemini |
| Swagger 2.0 | https://octane.gearhost.com/preview/?openapi=2.0 | Microsoft Copilot Studio connectors |
| Gemini tools | https://octane.gearhost.com/preview/?gemini | Google GenAI function-calling |
| Manifest | https://octane.gearhost.com/.well-known/ai-plugin.json | Machine discovery |
Claude.ai / Desktop: Settings → Connectors → Add custom connector → paste https://mcp.gearhost.com/ (no auth).
Claude Code (CLI): run
Transport http (Streamable HTTP), auth none. Then ask Claude to “publish this site to GearHost” — the tools (publish_website, get_site_status, rollback_website, …) appear automatically.
No setup at all? You can also just POST a JSON-RPC tools/call to https://mcp.gearhost.com/ directly — it's a public endpoint (a plain GET returns a how-to).
Or add it by hand: an HTTP MCP server at https://mcp.gearhost.com/ with no auth. Then ask the agent to “publish this site to GearHost”.
Prefer MCP? In ChatGPT’s connector/developer settings, add the MCP URL https://mcp.gearhost.com/ instead.
publish_website, have your app POST the JSON to https://octane.gearhost.com/preview/.url and a token to update it later.octane.gearhost.com, scheme HTTPS. Save & publish, then add the publishWebsite action to your agent.html, files, or zip_base64.token (Bearer), or publish again with the same name + project_key (a ≥16-char secret you store) to update across sessions.claim_url; register a notify_url webhook to get an expiring_soon nudge.A static site can still have a working contact form. Point any HTML form at GearHost Forms and each message is emailed to the site owner, who can reply straight to the visitor. It starts working once the site is kept in a GearHost account.
_subject (email subject), _next (a thank-you page on the same site). _gotcha is a spam trap.Accept: application/json from fetch() to get {"ok":true} instead of a page.GearHost CloudSites · gearhost.com · Privacy & Terms