easydeploy-ai-mcp
OfficialRelated Servers
Alternatives to easydeploy-ai-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.87 npm-
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI assistants to make HTTP requests (GET, POST, PUT, DELETE) to external APIs through standardized MCP tools.42MIT
- AlicenseAqualityDmaintenanceA 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.32444 npm45MIT
- FlicenseNot gradedqualityDmaintenanceA 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.4 npm-
- AlicenseNot gradedqualityDmaintenanceA dead simple MCP server for exposing your app functions to AI agents like Claude Desktop.8 npm6MIT
- AlicenseNot gradedqualityDmaintenanceMCP 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.21 npm8MIT
TDQS
Scored across 30 tools
Most tools map cleanly to distinct resources and actions, with clear separation between uploads, datasets, model versions, training, aliases, and predictions. A few boundaries could still be confused, especially get_model vs get_model_version, list_dataset_versions vs get_dataset_version, and complete_upload vs create_dataset_version, but the descriptions generally resolve them.
The tool set uses a consistent snake_case verb_noun convention throughout: list_*, get_*, create_*, update_*, run_*, submit_*, set_*, start_*, and complete_*. upload_from_url is the only slightly different verb phrase, but it remains clear and consistent with the overall style.
Thirty tools is heavy for any single MCP server, even one covering a full ML lifecycle. Most tools are purposeful and non-redundant, but the surface could likely be consolidated through fewer generic resource tools or combined list/get operations.
The surface covers the core ML workflow well: projects, uploads, datasets and versions, models and versions, aliases, training, reports, predictions, account status, and a playbook. Minor lifecycle gaps remain, such as deletion/cleanup operations for projects, datasets, models, versions, or aliases.