A
licenseA
qualityA
maintenanceEnables publishing sanitized static HTML pages from an MCP agent and receiving shareable URLs, with tools for updating, listing, publishing, and deleting pages.
12
194 npm
MIT
cloudbase-html-mcp
by zyfasos
Related Servers
Alternatives to cloudbase-html-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables publishing, updating, and sharing HTML artifacts with strict security isolation (origin separation, CSP, API keys) via MCP tools.1-
- AlicenseBqualityDmaintenanceEnables deployment of HTML content, folders, and full-stack projects to EdgeOne Pages to generate publicly accessible URLs. It utilizes EdgeOne Pages Functions and KV storage for high-performance edge delivery of web applications.27 npmMIT
- AlicenseAqualityBmaintenanceMCP server for publishing HTML or Markdown to a live hosted URL via htmldrop. Provides tools to publish, list, and delete hosted sites, with remote OAuth and API token authentication.325 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables sharing self-contained HTML files via public or access-key-protected private links. Provides MCP tools to create shares, retrieve public share metadata, and describe the service.6-
- AlicenseNot gradedqualityAmaintenanceLets MCP clients upload, list, and retrieve HTML artifacts and their metadata, including submitting files via signed upload tickets.2Apache 2.0
TDQS
A4.3/5.0
Scored across 6 tools
Disambiguation4/5
Most tools are clearly distinct: status, publish, get, list, offline, online each target a different lifecycle action. However, publish_html and online_html both make HTML publicly accessible, and only the descriptions clarify that one is for online/overwrite workflows while the other is for restoring offline pages.
Naming Consistency4/5
Five tools follow a consistent verb_noun pattern: publish_html, get_html, list_html, offline_html, online_html. hosting_status breaks that pattern by using a noun phrase instead of an action-oriented name like check_status or get_status.
Tool Count5/5
Six tools are well-scoped for the HTML hosting lifecycle: service status, publish/update, read, list, offline, and online. There is no obvious bloat or missing core operation at this level.
Completeness4/5
The set covers the core lifecycle well: create/overwrite, query, list, delete, restore, and status checking. The main gap is that list_html explicitly does not inventory the full cloud-side set of sites, so discovery of unknown remote sites is not possible without a known ID or URL.
Maintenance
ActivitySlowing
ResponsivenessNo issues