htmldrop-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTMLDROP_API_URL | No | Override for staging or self-hosted htmldrop instances. | https://htmldrop.app/api/v1 |
| HTMLDROP_API_TOKEN | Yes | The hsk_live_… token minted in your dashboard. Required for stdio. The remote server uses OAuth instead. | |
| HTMLDROP_PUBLIC_URL | No | User-facing origin for share links (…/s/<slug>). Only needed when HTMLDROP_API_URL points at a non-public address; set it to e.g. https://htmldrop.app. |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| htmldrop_publishA | Publish an HTML or Markdown document as a hosted page on htmldrop. Returns the public share URL. Use this whenever a user asks to publish, share, or 'put on the web' some HTML / Markdown content. Pass exactly one of |
| htmldrop_listA | List every site the authenticated tenant has published. Returns each site's slug, id, and public URL. |
| htmldrop_deleteA | Delete a site by its id. The id is the opaque string returned from htmldrop_list (NOT the slug). Once deleted the public URL returns 404 immediately. |
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 3 tools
Each tool has a distinct action: publish, list, and delete. There is no overlap or ambiguity between the tools.
All tool names follow the same pattern: htmldrop_ + verb (publish, list, delete). This is perfectly consistent and predictable.
Three tools is well-scoped for a focused service that publishes, lists, and deletes hosted HTML/Markdown. Each tool is necessary and none are redundant.
The core lifecycle is covered: publish (create), list (read), and delete. A minor gap is the lack of an update or edit capability, but the main workflows are complete.