@share-html/mcp-server
Related Servers
Alternatives to @share-html/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to publish live, stateful HTML pages over MCP, providing shareable URLs, per-viewer data, and version history.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to publish HTML pages and small sites over MCP, returning a stable link and keeping every version, with access limited to specific people, an organization, or anyone with the link.3AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to publish HTML or Markdown pages to a hosted or self-hosted bin, returning shareable read links, rendered URLs, PDF exports, and an editable write link. Pages can be updated in place on the same URL, and agents can keep private scratchpads for context shared across MCP clients.2MIT
- AlicenseNot gradedqualityDmaintenancePublish and manage shareable HTML/Markdown pages with access control and comments via MCP clients.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to deploy HTML pages and manage them (list, archive, move, rename) in a versioned library via MCP tools.39 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to publish HTML artifacts to permanent, shareable, versioned pages on Artifyde via MCP.51 npmMIT
TDQS
Scored across 12 tools
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.
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.
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.
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.