A place to publish the files AI generates — HTML sites, PDFs, markdown, CSV, images, video — as clean, access-controlled links like acme-proposal.quickhost.ing, with per-recipient open tracking and client comments your agent can read and act on.

How do I share a Claude artifact or a ChatGPT page with a client?

Download it as a file and drag it onto the dashboard, or let your agent publish it directly over MCP. Either way it is live on its own subdomain in seconds, gated however you choose, and your client needs no account to open it.

What file types can I publish?

Multi-file HTML sites as a zip or a folder, single HTML files, PDFs, markdown, plain text, CSV, TSV, JSON, images, and video. Each one gets a viewer built for it, and sites are served exactly as uploaded.

Can I password-protect a link, or make it expire?

Yes, on every plan. A project can be public, password-protected with a doorcode you can read back and re-send, or private behind named signed links you revoke individually. Any project can carry an expiry date.

How do I know if the client opened it?

Give each recipient their own named link. The dashboard then shows opens per person — count, first opened, last opened — and an email arrives the first time each link is opened.

Can clients comment without creating an account?

Yes. They highlight text, drop a pin, or mark a PDF page or a video timestamp, add a name, and comment. No sign-up. You see the thread in the dashboard and your agent sees it over MCP or qh comments --json.

Can my AI agent use this without me?

That is the intended shape. There is an MCP server with 17 tools, a CLI with --json on every command, a REST API with stable machine-readable error codes, and agent documentation at /mcp.md (how to connect Claude Code, Codex, Gemini CLI, Cursor and VS Code), /llms.txt, /docs.md and /.well-known/agent.md.

Does it run backend code or build my project?

No. Static files only, served exactly as uploaded — no functions, no build pipeline. That is deliberate: nothing compiles, so nothing can break after you have sent the link.

Is there a free plan?

No, and there will not be. Plans start at $8 a month with a 7-day trial of Studio. That is why there are no upsell banners on your deliverables, no branding badge on your client’s page, and no link that dies because you forgot to log in. Access is invite-only while billing is being finished.

Are viewers tracked with cookies or scripts?

No. Engagement is measured from server access logs: no analytics script is added to your work, no cookies are set on viewers, and unique-visitor counts use salted hashes that rotate daily. Every project is noindex by default.

MCP

Connect your agent to QuickHost

QuickHost has an MCP server with 17 tools, so an agent can publish a file, password-gate it, hand back the URL and read the comments that come back — without you opening a browser. It takes one command in most clients, and a pasted URL in the rest.

Step one

Which of the two setups do I need?

It is decided by your client, not by you. Clients that let you set a header — Claude Code, Cursor, Codex, VS Code — use a token you create first. Clients that only take a URL — the Claude and ChatGPT connector panels — sign you in through OAuth instead, and there is no token to copy.

If your client takes a header

Create a token at app.quickhost.ing/settings under API tokens. It is shown once and starts with qh_. Treat it like a password: it can publish, change who can see a project, and read your clients’ comments. Wherever the setup below says TOKEN, paste that value.

If your client takes a URL

Skip the token entirely. Paste https://api.quickhost.ing/mcp into the connector panel and approve the sign-in when it appears. Your client registers itself and handles the rest.

Step two

How do I add it to my client?

Pick yours. If it is not listed, any MCP client that speaks Streamable HTTP will work — point it at the same endpoint.

Claude Code

Token

Run it in your terminal, then /mcp in a session lists the tools.

claude mcp add --transport http quickhost \
  https://api.quickhost.ing/mcp \
  --header "Authorization: Bearer TOKEN"

Claude Desktop

Settings → Connectors → Add custom connector. Paste the URL and sign in when it asks. There is no token to copy.

https://api.quickhost.ing/mcp

ChatGPT

Settings → Connectors → Add. Same as above: paste the URL, approve the sign-in.

https://api.quickhost.ing/mcp

Cursor

Token

Add to ~/.cursor/mcp.json.

{
  "mcpServers": {
    "quickhost": {
      "url": "https://api.quickhost.ing/mcp",
      "headers": { "Authorization": "Bearer TOKEN" }
    }
  }
}

Codex CLI

Token

Add to ~/.codex/config.toml.

[mcp_servers.quickhost]
url = "https://api.quickhost.ing/mcp"
http_headers = { Authorization = "Bearer TOKEN" }

Step three

How do I know it worked?

Ask your agent to list your projects. If it comes back with a list — or an honest “you have none yet” — the connection is good and the token is valid. A 401 means the token is wrong or was revoked; create a new one.

Try this

Publish proposal.html to QuickHost as acme-proposal, password-gated, and give me back the URL and the doorcode.

For the agent

Can my agent set this up itself?

Yes, and that is the shorter path. Point it at https://api.quickhost.ing/mcp.md — the same instructions as above, written to be executed rather than read, covering every client we have verified. Everything an agent needs is published as plain text: no login, no JavaScript, no scraping a rendered page.

/mcp.md: Per-client connection instructions
/llms.txt: What QuickHost is, for a model reading about it
/docs.md: The full API surface in one file
/.well-known/agent.md: Discovery entry point