EdgeOne Pages MCP
Related Servers
Alternatives to EdgeOne Pages MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables the deployment of HTML content, folders, and full-stack projects to EdgeOne Pages to generate publicly accessible URLs. It integrates with edge functions and KV storage to provide fast content delivery and supports custom domain configuration.2434 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to deploy and manage static websites directly on EdgeOne Pages. Provides simple one-click deployment with KV storage for hosting website files accessible through custom domains.-

EdgeOne Pages MCPofficial
AlicenseBqualityDmaintenanceA service that enables rapid deployment of HTML content to EdgeOne Pages and automatically generates publicly accessible URLs for the deployed content.2434 npm434MIT- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to deploy and manage static websites directly on EdgeOne Pages. Simple self-hosted solution with one-click deployment and KV storage for website files.-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to deploy and manage static websites directly on EdgeOne Pages through a self-hosted Model Context Protocol solution. It simplifies web hosting by allowing natural language commands to handle site deployment and KV storage management.-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to deploy and manage static websites directly through EdgeOne Pages. It provides a self-hosted solution for hosting website files using KV storage and managing content through the Model Context Protocol.-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: deploy_folder_or_zip handles directory or zip file deployments for built frontends, while deploy_html handles direct HTML content deployments. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern starting with 'deploy_' and clearly indicate their target (folder_or_zip vs. html). The naming is uniform and predictable throughout the set.
With only 2 tools, the server feels thin for a deployment service. It lacks essential operations like listing deployments, updating or deleting them, or managing projects, which limits agent workflows and creates dead ends.
The toolset is severely incomplete for a deployment domain. It provides create-like operations (deploy) but lacks read, update, delete, or management functions (e.g., list_deployments, get_deployment_status, delete_deployment), making it difficult for agents to handle full lifecycle tasks.