Skip to main content
Glama
licc168

htmltolink-mcp

by licc168
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to htmltolink-mcp

No user-submitted related servers found.

    Related Servers

    • deloc-mcp by delocdev

      deloc-mcpofficial

      delocdev
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Deloc — deploy static sites from AI coding agents. Say "deploy this to Deloc" in Claude Code or Cursor and get a live URL back without leaving your editor.
      4
      MIT

    • drop

      neuronik-io
      A
      license
      Not graded
      quality
      D
      maintenance
      Publishes 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

    • vibie-mcp

      shdomi8599
      A
      license
      A
      quality
      F
      maintenance
      Deploy static HTML folders to permanent vibie.page URLs from Claude, Cursor, or any MCP client. One-line auto-install wires up the config, OAuth device-flow handles auth, and a folder marker lets repeat deploys skip the slug.
      4
      36 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are unmistakably distinct: 'deploy' triggers a deployment, while 'status' reads the deployment status. There is no overlap in their purposes or outcomes.

    Naming Consistency4/5

    Both names are concise, lowercase, and single-word, following a predictable command-style pattern. However, 'status' is a noun while 'deploy' is a verb, representing a minor inconsistency in part of speech.

    Tool Count4/5

    With only two tools, the server is minimal but well-aligned to its narrow purpose. It is slightly under the typical range, yet both tools are essential and justify their existence.

    Completeness4/5

    The core deployment workflow is covered: deploying and checking status. A setup or initialization tool could be useful, but the current surface does not present critical gaps for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources