Model Context Protocol moderate risk

Edgeone Pages

Deploys HTML content, folders, or full-stack projects to EdgeOne Pages, providing publicly accessible URLs; requires careful API token management.

Connections & Capabilities

Connects To

GitHub

Capabilities

writeexec

Quickstart

Config

{
  "mcpServers": {
    "edgeone-pages-mcp-server": {
      "url": "https://mcp-on-edge.edgeone.site/mcp-server"
    }
  }
}

Exposed MCP Tools (2)

moderate

deploy_html

Deploys static HTML content to EdgeOne Pages and returns a public URL.

Writes HTML content to EdgeOne Pages KV store, potentially overwriting existing content.

high

deploy_folder

Deploys a folder or full-stack project to EdgeOne Pages.

Deploys entire projects, potentially including executable code, and requires API token.

Safety Assessment

The service is relatively safe for deploying static HTML content. However, deploying full-stack applications and managing API tokens require careful security considerations to prevent unauthorized access and potential vulnerabilities.

Supports deploying static content, reducing server-side code execution risks.
Offers both stdio and HTTP streaming MCP server options, providing flexibility.
Provides options to create new projects or update existing ones, allowing for controlled deployments.
Documentation includes architecture diagrams and implementation details for better understanding.

Requires an EdgeOne Pages API token for folder and zip deployments, posing a secret management risk.
The `deploy_folder` tool can deploy full-stack applications, potentially introducing vulnerabilities if not properly secured.
Lack of explicit input validation details could lead to injection vulnerabilities.
Deprecated MCP server configurations might introduce compatibility or security issues if still used.