MCP server

Give your agent an MCP tool that publishes HTML.

HTMLHost.ai ships a hosted Model Context Protocol server. Connect it once and any MCP client — Claude Code, Claude Desktop, Cursor, or your own agent — can publish HTML artifacts, update existing pages, and list what it has shipped. No CLI install required.

Get an API key Prefer the CLI?

$ claude mcp add --transport http htmlhost \
    https://htmlhost.ai/mcp \
    --header "Authorization: Bearer hh_..."

# Then ask the agent:
# "Publish this dashboard with the htmlhost tool"

deploy_html

Publish a standalone HTML document and get back a public URL, optionally grouped into a project folder.

update_html

Replace the content behind an existing URL so a shared review link always shows the latest version.

list_pages

Let the agent see what it has published, with URLs and view counts.

Setup

Three steps to agent-native publishing.

Create an API keySign in and create a key in the API keys tab. It identifies the account that owns published pages.

Add the MCP serverPoint your MCP client at https://htmlhost.ai/mcp with the Authorization header shown above.

Ask for a URLTell the agent to publish its HTML output with the htmlhost tool and reply with the link.

FAQ

Practical answers before you publish.

Which transport does the server use?

Streamable HTTP. Each JSON-RPC request gets a direct JSON response, which works with current MCP clients.

Does it work with Claude Desktop?

Yes. Add a custom connector pointing at https://htmlhost.ai/mcp with your Authorization header.

Is there a local server to install?

No. The MCP endpoint is hosted; only an API key is needed.

What about the CLI?

The CLI remains the lightest option for shell-capable agents. MCP suits clients without shell access or with managed tool configs.