Skip to main content
Glama
justaba

Snaphost MCP

by justaba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Snaphost MCP

No user-submitted related servers found.

    Related Servers

    • @snapdeploy/mcp

      AAR-Labs
      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
      134 npm
      MIT

    • golive-mcp

      abbylester1
      A
      license
      Not graded
      quality
      A
      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.
      54 npm
      1
      MIT
    • dockhold by dockhold

      dockholdofficial

      dockhold
      A
      license
      Not graded
      quality
      B
      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

    • WebDeploy MCP

      ghbhiee
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients and users to deploy static sites, Node.js services, and Python web applications without Docker, with tools for project management, deployment, rollback, and domain configuration.
      -

    • thedeployer

      Avinash147-1193
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to check repository deploy readiness, deploy apps to your own cloud (AWS, Google Cloud, Azure, DigitalOcean), and migrate apps from platforms like Heroku, Railway, Render, or Vercel with rollback.
      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

    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

    ActivityStale
    ResponsivenessNo issues

    Resources