Skip to main content
Glama
EasyDeploy-AI

easydeploy-ai-mcp

Official

Related Servers

Alternatives to easydeploy-ai-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.
      30 npm
      -
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to make HTTP requests (GET, POST, PUT, DELETE) to external APIs through standardized MCP tools.
      4
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that provides integration with the Coolify API, enabling DevOps teams to manage Coolify deployments, applications, services, and servers through MCP tools.
      32
      112 npm
      45
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server built with the mcp-framework for developing and managing custom tools. It provides a structured foundation for building and integrating modular components like data processors and API clients into Claude Desktop.
      12 npm
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A dead simple MCP server for exposing your app functions to AI agents like Claude Desktop.
      5 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Dify Console API that enables managing apps, workflows, knowledge bases, models, plugins, and MCP servers programmatically from Claude Code or any MCP client.
      13 npm
      8
      MIT

    TDQS

    A3.8/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, and the upload/train/predict flows are well explained. Minor overlap exists between get_training_status and model-version status tracking, and between complete_upload and create_dataset_version for registering dataset versions.

    Naming Consistency5/5

    Tool names consistently use snake_case with predictable verb_noun phrasing such as list_projects, get_dataset, create_model_version, and run_batch_prediction. The few create_* tools that also update still follow the same naming convention.

    Tool Count3/5

    28 tools is heavy, though it reflects a broad MLOps platform spanning projects, datasets, versions, models, training, and predictions. Several list/get pairs could likely be consolidated, but few tools are clearly redundant.

    Completeness4/5

    The core ML lifecycle is well covered: upload, dataset/model/version creation, training, reporting, and ad-hoc/batch prediction. Gaps remain around deletion operations, model-version updates, and endpoint/deployment management hinted at by account status.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues