Skip to main content
Glama

Related Servers

Alternatives to cloudfact

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes a local development project as a secure MCP server over a stable HTTPS URL via Cloudflare tunnel, with configurable access permissions and 33 development tools for file, command, Git, and process operations.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables 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.
      2
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables remote MCP clients to access local filesystem and shell commands by deploying a Cloudflare Worker relay and a local daemon, providing tools like read/write files, exec commands, git status, etc.
      597 npm
      1
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables the deployment of HTML content, folders, and full-stack projects to EdgeOne Pages to generate publicly accessible URLs. It integrates with edge functions and KV storage to provide fast content delivery and supports custom domain configuration.
      2
      353 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to publish HTML pages, files, or directories as public permanent links, with optional token-based updates to keep the same URL.
      4
      2
      91 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for self-hosted static site publishing on Cloudflare Workers. Enables AI coding agents to deploy pages with a single 'publish' tool and get live URLs, with support for atomic updates, versioning, and per-site passwords.
      5 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 13 tools

    Disambiguation4/5

    Tools are mostly distinct with clear purposes, but some overlap exists: power/stop both affect serving state, and deploy/expose both publish to URLs, though descriptions clarify the differences (power toggles the link, stop stops local server/tunnel; deploy serves static files, expose proxies an existing port). Overall, agents can distinguish with careful reading.

    Naming Consistency3/5

    Naming mixes verbs (deploy, expose, stop, remove, rotate, list) with nouns or noun-verbs (power, logs, doctor, catalog, project, credentials, status). No consistent verb_noun or noun pattern, though all lowercase and single-word commands. Some predictability exists but not uniform.

    Tool Count5/5

    13 tools for a deployment/publishing service is well-scoped, covering creation, management, diagnostics, and metadata without bloat. Each tool earns its place, and the count is in the ideal range.

    Completeness5/5

    The surface covers the full lifecycle: deploy/expose (create), list/catalog/status/logs (read), power/stop/rotate (update), remove (delete), plus diagnostics and metadata (project, credentials). No obvious gaps; even edge cases like quick tunnels and account-wide visibility are addressed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues