Skip to main content
Glama

Related Servers

Alternatives to Neptune MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Cloud infrastructure provisioning via natural language. Enables deploying production-ready infrastructure on AWS, GCP, Azure, or Oracle with a single prompt.
      12
      8 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to discover, evaluate, and provision cloud infrastructure across AWS, GCP, and Azure with cross-cloud normalization, cost comparisons, and deployable execution kits.
      5
      11 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with natural language control over AWS, Azure, GCP, and Alibaba Cloud infrastructure through dynamic API discovery and execution. Supports 51,900+ cloud operations and includes OpenTofu integration for complete infrastructure lifecycle management.
      3
      MIT

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct purposes, but wait_for_deployment and get_deployment_status are closely related and add_new_resource's name is misleading (it only returns info about resource types, not actually adding). However, descriptions generally clarify the differences.

    Naming Consistency3/5

    The majority follow a verb_noun pattern (list_projects, get_logs, delete_project), but some deviate: 'info' and 'login' lack objects, and 'add_new_resource' implies an action different from its actual informational purpose. This mixed convention reduces predictability.

    Tool Count4/5

    15 tools is at the high end of the ideal range, but each addresses a distinct aspect of cloud deployment and management. A few informational tools (info, get_project_schema, add_new_resource) are somewhat redundant but still marginally useful.

    Completeness3/5

    Core project operations (list, deploy, delete, status) and resource operations (provision, bucket, secret, database) are covered, but there is no create_project tool, no secret retrieval, and no resource deletion. These gaps may require workarounds.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues