Skip to main content
Glama
aizuikmal

publish-my

by aizuikmal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to publish-my

No user-submitted related servers found.

    Related Servers

    • Demox MCP Server

      demox-site
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to deploy static websites to the Demox platform with automatic directory packaging and cloud storage integration. It includes tools for managing deployments, such as listing, viewing, and deleting websites.
      7
      16 npm
      MIT
    • drop2run-mcp by Drop-to-run

      drop2run-mcpofficial

      Drop-to-run
      A
      license
      A
      quality
      B
      maintenance
      Publishes what an AI made — a page, a markdown or PDF doc, or a whole site — to a live HTTPS link. Runs locally over stdio from the @drop2run/mcp npm package, or hosted at https://mcp.dropto.run/mcp for chats that connect by URL.
      20
      3
      MIT
    • SnapHost by snaphost-ai

      SnapHostofficial

      snaphost-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Send a live, private link to a client from Claude. SnapHost publishes what your assistant builds as a shareable website with a stable URL, updates it in place, restricts viewers by email or password, rolls back bad versions, serves custom domains, and stores form and waitlist data with no backend.
      MIT
    • thinhost-mcp by thinhost

      thinhost-mcpofficial

      thinhost
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to publish static sites and build folders as live websites, push updates, provision and manage custom domains with DNS, and send transactional email. Ships as a local pip/uvx server that reads build folders directly, or as a hosted HTTP endpoint for Claude Code, Claude Desktop, and other MCP clients.
      11
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool targets a distinct step in the static-hosting lifecycle (publish, check activation, list, reconnect), and descriptions spell out the trigger conditions. The only soft overlap is between check_activation and reconnect_site, since both hinge on the user clicking an emailed link, though the preconditions (new site vs. lost key) are stated clearly enough to separate them.

    Naming Consistency5/5

    All four tools follow a uniform snake_case verb_noun pattern (publish_site, check_activation, list_sites, reconnect_site). No mixed conventions or vague standalone verbs.

    Tool Count4/5

    Four tools is a tight, purposeful surface for a static-site publishing service, with each tool earning its place. It sits at the low end of the comfortable range, but nothing feels redundant or padded.

    Completeness3/5

    Publish (create), re-publish (update), list (read), activation check, and key recovery are covered, so the core loop is closed. However, there is no way to unpublish/delete a site, rename it, or inspect a single site's details, which are predictable needs for a hosting service.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources