Skip to main content
Glama
sota-deploy

@sota-io/mcp

by sota-deploy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @sota-io/mcp

No user-submitted related servers found.

    Related Servers

    • BasicDeploy MCP Server

      AkaciaNL
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to create and manage BasicDeploy containers with PostgreSQL, S3 storage, and public URLs, including deploying apps, running commands, viewing logs, and sharing containers.
      18
      34 npm
      MIT

    • krexel-mcp

      Syfer-web
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to deploy, manage, and rollback websites via the Krexel API, supporting site uploads, deploys, logs, rollbacks, environment variables, and status checks.
      9
      57 npm
      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.
      -

    • Dokploy MCP Server

      huuthangntk
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Dokploy deployments, including creating and deploying applications, managing databases, configuring domains with SSL, and monitoring application status through a standardized interface.
      14 npm
      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.3/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: deploy, project lifecycle (list, create, delete), environment variables (set, get), logs, rollback, status, and domain management (add, list, get, remove). There is no overlap or ambiguity between any of the tools.

    Naming Consistency4/5

    The tool names follow a consistent verb-noun pattern using kebab-case (e.g., list-projects, create-project, delete-project, get-logs, set-env, add-domain, remove-domain). However, 'deploy' and 'rollback' are verbs without a noun object, which is a minor deviation from the pattern.

    Tool Count5/5

    With 13 tools, the set is well-scoped for a DevOps PaaS server. It covers the essential operations for deploying, managing projects, handling environment variables, viewing logs, and managing custom domains without being excessive or too thin.

    Completeness4/5

    The tool surface covers the core lifecycle: project CRUD, deployment, logs, env vars, rollback, and domain management. Minor gaps include the absence of a tool to update project settings or trigger a redeploy without re-uploading, but these are workable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources