Publish AI-generated HTML in one step

From a chat app: ChatGPT, Gemini or Claude

1. 1Ask the assistant for “one self-contained HTML file with inline CSS and JavaScript”. A single file publishes without broken references.
2. 2Copy the code it writes and paste it into the BrewPage editor. If the answer is a document rather than a page, paste it as Markdown.
3. 3Press Publish and share the link. Keep the owner token if you will publish a new version later.

Chat apps write the HTML but usually cannot send it anywhere from the chat window, so the copy-and-paste step is the reliable path. Desktop clients that support MCP servers can publish directly once the BrewPage server is connected.

From a coding agent: Claude Code, Codex, Cursor and others

Coding agents run commands, so they can publish their own output. Add one instruction to the agent's project notes, such as AGENTS.md or CLAUDE.md, and it will publish finished reports and reply with a link:

Instruction for the agent

When you finish an HTML page or a Markdown report the user should see, publish it to BrewPage and return the link. POST the HTML to https://brewpage.app/api/html with Content-Type: text/html (Markdown: Content-Type: text/markdown). Requests without ns publish to the public namespace; set a non-public ns for an unlisted address. Return the link from the response and keep the ownerToken for updates. Full API: https://brewpage.app/llms.txt

For tool-based publishing, connect the MCP server, which works with MCP clients such as Claude, Codex, Cursor and Gemini:

MCP server config

{ "mcpServers": { "brewpage": { "command": "npx", "args": ["-y", "brewpage-mcp@1.9.3"] } } }

Claude Code users can also install the brewdoc plugin and run /publish; the steps are on the Claude artifacts page. Agents that load llms.txt find the whole API described there.

The request behind it

Every path above ends in the same call. JSON works well when the HTML is already in a variable:

Publish HTML from JSON

curl -X POST "https://brewpage.app/api/html" \
  -H "Content-Type: application/json" \
  -H "User-Agent: MyAgent/1.0" \
  -d '{"content": "<h1>Build report</h1><p>All checks passed.</p>"}'

The response carries the link, the ownerToken and the expiry date. In GitHub Actions the same step is one action:

GitHub Actions step

- name: Publish report
  id: brewpage
  uses: kochetkov-ma/brewpage-action@v1.1.2
  with:
    path: ./report.html
- run: echo "Report: ${{ steps.brewpage.outputs.url }}"

Check AI output before you publish

• One file. Generated pages sometimes point at style.css or app.js that were never written. After publishing, BrewPage warns when a page references local files that were not uploaded; inline them, or publish the folder as a site.
• No secrets. Generated code can contain API keys, tokens or internal URLs copied from the conversation. Remove them before publishing.
• The right audience. Public pages can be listed and found, unlisted links can be forwarded, and only a password restricts reading.
• Browser features. If the page stores data in the browser or changes the address bar, it works best on its own subdomain; BrewPage may choose that address automatically and tells you why.

Limits

Size

One HTML or Markdown page up to 5 MB. A multi-file site up to 20 MB in total, 100 files, 5 MB per file.

Lifetime

1 to 30 days, 15 by default. When the time is up the content is deleted for good, with no recovery. Updating a page keeps its original expiry date; it does not extend it.

Visibility

Public publications without a password can appear in the gallery and in search results, but neither is guaranteed. An unlisted address is not private: anyone who has the link can open it. Set a password (at least 4 characters) when readers should have to enter one.

Ownership

There are no accounts. The owner token returned with each publish is the only way to update or delete; a lost token cannot be recovered, and the content then simply expires.

Usage

Publishing and reading are rate-limited per IP address. A 429 response carries a Retry-After header that says when to try again.

Attribution

Published pages show a small BrewPage badge. Publishing follows the terms, and anyone can report a page.

Compared with typical hosting for generated pages

Publishing AI-generated HTML — FAQ

Related guides