Skip to main content
Glama
cgmorah

empaya-mcp-server

by cgmorah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to empaya-mcp-server

No user-submitted related servers found.

    Related Servers

    • easypanel-mcp-server

      helbertparanhos
      A
      license
      B
      quality
      A
      maintenance
      MCP Server for full Easypanel control via Claude Code, Cursor, and Claude Desktop. Provides 37 tools for deploy, logs, env vars, domains, databases, and monitoring with built-in safety guards.
      57
      14 npm
      4
      MIT

    • coderocket-mcp

      mlgraham
      A
      license
      A
      quality
      B
      maintenance
      MCP server for CodeRocket Deploy providing AI-generated CI/CD workflows and AI code review as tools inside Claude Code.
      9
      6 npm
      MIT

    • vps-mcp

      ereskovsky
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for managing VPS servers via SSH, enabling command execution, file transfer, Docker management, and server documentation from within Claude.
      8 npm
      ISC

    • coolify-mcp-server

      Softtor
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Coolify API integration, enabling management of applications, databases, services, servers, and deployments via Claude Code or any MCP-compatible client.
      2 npm
      2
      MIT

    • AgenSysAdmin

      E13ctr0N
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for remote Linux server administration via SSH, integrating with Claude Code to manage Ubuntu/Debian servers.
      2
      -
    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

    B3.2/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose covering different Cloudways management tasks (deployment, backups, logs, environment variables, SSL, etc.). No two tools appear to do the same thing.

    Naming Consistency4/5

    All names use snake_case and start with a verb, but there is some inconsistency in whether 'cloudways' is included in the noun (e.g., 'list-cloudways-apps' vs 'check-deployment-status'). Overall the pattern is mostly predictable.

    Tool Count5/5

    12 tools is appropriate for a Cloudways management server. Each tool covers a necessary operation without unnecessary bloat, and the number is within the ideal 3-15 range.

    Completeness4/5

    The tool surface covers major workflows like listing, deploying, backups, logs, SSL, and environment variables. Minor gaps exist (e.g., no delete backup or delete environment variable), but overall it is largely sufficient for common tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources