Skip to main content
Glama

Related Servers

Alternatives to Snaphost MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to deploy and manage SnapDeploy containers and resources—including builds, logs, environment variables, databases, and custom domains—directly through natural language.
      15
      53 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to deploy code to any hosting provider by creating PRs, building, and verifying health checks, all from a single natural language command.
      62 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to build and deploy an app from a GitHub repository to a managed live server and then operate it — logs, captured errors, health checks, managed Postgres, secrets, custom domains, email authentication, and Stripe checkout links. It also exposes safe, read/write-labelled tools so agents can rebuild, start/stop, and inspect projects without ever editing source code.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to deploy and manage full multi-service applications on Constructor from a single request, covering image builds, service configuration, start/stop lifecycle, logs, and file syncing on research desks. It handles browser-based sign-in and token renewal automatically so agents can inspect deployments and report results without manual setup.
      14
      478 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Deploys the current folder or a GitHub repo to a live HTTPS URL on Dockhold, and lets AI tools read status/logs, set variables, and resize apps and managed databases.
      MIT

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action pair: deploy, logs, delete, status, and list. There is no overlap or ambiguity — deploy creates, logs fetches, delete removes, status checks, and list enumerates. An agent can clearly distinguish which tool to invoke.

    Naming Consistency5/5

    All tools follow a consistent snaphost_ prefix followed by a clear verb naming the action (deploy, logs, delete, status, list). The action verbs are simple and unambiguous, maintaining a uniform style throughout.

    Tool Count5/5

    Five tools is well-scoped for a deployment lifecycle server. Each tool earns its place covering deploy, monitor (logs/status), clean up (delete), and discovery (list) without bloat or deficiency.

    Completeness4/5

    The core deploy lifecycle is well covered: deploy, status, logs, list, and delete. Minor gaps include the absence of an update/redeploy operation to replace an existing deploy, and no ability to manage env variables post-deploy, but these are workaround-able gaps for the primary use case.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data