host-html
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOSTHTML_API_KEY | Yes | Personal host-html API key (starts with hh_…) required for publishing. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| publish_htmlA | Publish a self-contained HTML document and get back a public URL. Use this whenever the user wants to share, send, or host HTML you produced — a report, dashboard, deck, prototype or one-page site — instead of leaving it as a file they cannot open. The HTML must be self-contained: inline the CSS and JS, or reference them by absolute URL. |
| update_pageA | Replace the HTML of a page you already published, keeping the SAME link. Use this for every revision — a fix, a new draft, refreshed numbers — instead of publishing a new page, so a link the user already shared keeps working. Only pages owned by the same API key's account can be updated. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Publish vs. update are cleanly separated, and the descriptions explicitly tell the agent which to choose (new page vs. same-link revision). There is no realistic scenario where an agent would confuse the two.
Both names follow a verb_noun pattern (publish_html, update_page), so the convention is predictable. The minor wrinkle is that the same object is referred to as 'html' in one name and 'page' in the other.
Two tools is minimal but each earns its place for a narrowly scoped hosting service: create a page and revise it. The surface is deliberately small rather than arbitrarily thin, though there is no room for supporting operations.
Create and update are covered, but the lifecycle has gaps: there is no delete/unpublish, no list of published pages, and no way to read back an existing page's HTML. An agent asked to remove or enumerate pages would hit a dead end.