Publish HTML from AI agents with the API or MCP

Option 1 — MCP (Claude Code, Claude Desktop, Cursor, any MCP client)

The endpoint speaks MCP's Streamable HTTP transport and exposes three tools:

• publish_html — html (or files), optional slug, password, update. Returns the URL.
• list_pages — your live pages and plan usage.
• delete_page — removes a page by slug.

Claude Code

Copyclaude mcp add --transport http htmltourl https://www.htmltourl.dev/api/mcp \
  --header "Authorization: Bearer hu_your_key_here"

Cursor, Claude Desktop and other clients (JSON config)

Copy{
  "mcpServers": {
    "htmltourl": {
      "url": "https://www.htmltourl.dev/api/mcp",
      "headers": { "Authorization": "Bearer hu_your_key_here" }
    }
  }
}

Then just ask: "Build a one-page summary of this CSV and publish it with htmltourl as q3-summary."

Option 2 — REST API (scripts, CI, notebooks, custom agents)

Copycurl -X POST https://www.htmltourl.dev/api/publish \
  -H "Authorization: Bearer $HTMLTOURL_KEY" \
  -H "Content-Type: application/json" \
  -d '{"html": "<h1>Build #512 passed</h1>", "slug": "ci-512"}'

The response contains url, slug and expiresAt. Multi-file sites go in a files map; ZIPs can be posted as application/zip. Full reference: API docs.

Option 3 — An instruction file, no integration

Agents that can run shell commands only need to be told how. Add this to AGENTS.md, CLAUDE.md or your system prompt:

Copy## Sharing HTML
When the user wants to share an HTML file, publish it:
curl -s -X POST https://www.htmltourl.dev/api/publish \
  -H "Authorization: Bearer $HTMLTOURL_KEY" -H "Content-Type: text/html" \
  --data-binary @path/to/file.html
Reply with the "url" from the JSON response.

Rules that keep agents safe

• Keys are account credentials. Store them in environment variables or the MCP client config, never in the HTML.
• Published means visible. Anyone with the URL can view source. Tell the agent not to publish secrets, customer data or internal URLs, and use password for internal reports.
• Use update to republish to the same slug instead of creating a new page each run.
• Pages are noindex and follow your plan's limits (Free: 3 pages, 24 hours).