Skip to main content
Glama

Related Servers

Alternatives to Lizard MCP

  • A
    license
    C
    quality
    B
    maintenance
    Enables deploying and managing infrastructure via natural language, including project/domain management, compute nodes, image deployment, and CI/CD integration.
    70
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables managing Sliplane deployments, projects, and application status through natural language, with OAuth or API key auth.
    MIT

Related Servers

  • A
    license
    B
    quality
    C
    maintenance
    Enables AI agents to deploy and roll back applications, read build and runtime logs, diagnose broken apps, and run commands inside containers. It also manages environment variables, PostgreSQL databases, domains, cron jobs, marketplace services, and backups on a PaaS platform, with safety annotations so clients can confirm destructive actions.
    58
    13 npm
    MIT
  • A
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables AI assistants to manage cloud infrastructure through natural language by providing a unified interface to the Dokploy platform. Supports Docker containers, applications, databases, domains, monitoring, and deployment operations through conversational commands.
    31 npm
    1
    -
  • 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

TDQS

A3.5/5.0

Scored across 89 tools

Disambiguation4/5

The tools are mostly clearly separated by resource and action, with descriptions that explain scope differences such as service vs project vs workspace pause/resume/delete. A few areas still invite confusion, especially deploy_redeploy vs deploy_restart vs git_checkout, service_pause vs service_sleep_set, and config_apply vs narrower service/secrets tools, but the descriptions generally resolve the choice.

Naming Consistency4/5

Names overwhelmingly follow a snake_case resource_action convention, e.g. service_list, project_create, sandbox_resume, pr_merge. There are minor deviations and uneven verb choices such as show vs get, plus outlier names like whoami, but the overall pattern is predictable.

Tool Count1/5

89 tools is far beyond an appropriate surface for an agent-facing server, even for a broad cloud platform. The sheer number creates high selection and context burden, and many capabilities could be grouped into fewer higher-level tools or resource-oriented operations.

Completeness4/5

The surface covers a very wide platform lifecycle: workspaces, projects, services, addons, deploys, logs, metrics, secrets, domains/DNS, volumes, billing, templates, sandboxes, Git, pull requests and CI. There are still minor lifecycle gaps such as explicit project/workspace get or update operations, PR comments/reviews, and some billing/domain purchase actions, but core workflows are well covered.

Maintenance

ActivityActive
ResponsivenessLimited data