htmldrop
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port (default 3000) | 3000 |
| BASE_DOMAIN | No | Base domain for artifact subdomains | localhost |
| KEY_TTL_DAYS | No | TTL for keyed publishes (default 30) | 30 |
| ANON_TTL_DAYS | No | TTL for anonymous publishes (default 7) | 7 |
| MAX_HTML_SIZE_BYTES | No | Upload cap in bytes (default 26214400) | 26214400 |
| CLOUDFLARE_R2_ENDPOINT | No | Optional R2 storage endpoint | |
| CLOUDFLARE_R2_BUCKET_NAME | No | Optional R2 bucket name | |
| RATE_LIMIT_KEY_PER_MINUTE | No | Per-key rate limit (default 60) | 60 |
| RATE_LIMIT_ANON_PER_MINUTE | No | Per-IP rate limit (default 10) | 10 |
| CLOUDFLARE_R2_ACCESS_KEY_ID | No | Optional R2 access key ID | |
| CLOUDFLARE_R2_SECRET_ACCESS_KEY | No | Optional R2 secret access key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| publish_htmlA | Publish an HTML or markdown artifact (or fetch a remote HTML page) and get a shareable URL. Markdown is rendered into a clean reader page. Useful for sharing reports, dashboards, visualizations, or any document produced by an agent. |
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 1 tool
With only one tool, there is no possibility of ambiguity. The tool's purpose is clearly defined and distinct by default.
With a single tool, naming is trivially consistent. The verb_noun pattern (publish_html) is clear and appropriate.
One tool is on the borderline of being too thin. While it may suffice for a simple publishing server, it feels minimal and could benefit from additional tools (e.g., list, delete).
The tool covers basic publishing and fetching, but lacks management capabilities like listing, updating, or deleting published content, which are notable gaps for a complete service.