A
licenseNot graded
qualityB
maintenanceEnables AI agents to publish live, stateful HTML pages over MCP, providing shareable URLs, per-viewer data, and version history.
MIT
@share-html/mcp-server
by arunai30
Related Servers
Alternatives to @share-html/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenancePublish and manage shareable HTML/Markdown pages with access control and comments via MCP clients.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to deploy HTML pages and manage them (list, archive, move, rename) in a versioned library via MCP tools.25MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to publish HTML artifacts to permanent, shareable, versioned pages on Artifyde via MCP.105MIT
- FlicenseNot gradedqualityCmaintenanceEnables publishing, updating, and sharing HTML artifacts with strict security isolation (origin separation, CSP, API keys) via MCP tools.1-
- AlicenseNot gradedqualityDmaintenancePublishes HTML pages straight from your AI assistant to a shareable URL, then lets you manage them - update, list, search, fetch, and delete pages in a public or private workspace. Turns "share what I just made" into a single tool call from Claude, Cursor, or any MCP client.MIT
TDQS
A3.7/5.0
Scored across 12 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: lifecycle, sharing, and publishing for pages are well separated. The only potential overlap is between 'publish_html' and 'publish_page', but 'publish_html' creates a new page while 'publish_page' brings an offline page back online; the descriptions clarify this difference.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern (get_page, publish_html, update_page, list_pages, etc.), but there are deviations: 'end_current_viewing_sessions' uses a verb_phrase and 'get_page_sharing'/'set_page_sharing' add a suffix. Overall, the naming is predictable and readable.
Tool Count5/5
With 12 tools, the count is well-scoped for a page management server, covering creation, retrieval, updates, sharing, and deletion without excessive granularity or obvious redundancy.
Completeness5/5
The surface covers the full lifecycle of pages: creation (publish_html), retrieval (get_page, list_pages), updates (update_page), deletion (delete_page), and sharing controls (get/set_page_sharing, end_current_viewing_sessions, unpublish/publish_page). There are no apparent gaps for the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues