home / mcp / edgeone pages mcp server

EdgeOne Pages MCP Server

Provides deployment of HTML content, folders, and full-stack projects to EdgeOne Pages with public URLs and optional custom domains.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "15538420886-mcp": {
      "url": "https://your-custom-domain.com/mcp-server",
      "headers": {
        "EDGEONE_PAGES_API_TOKEN": "YOUR_API_TOKEN",
        "EDGEONE_PAGES_PROJECT_NAME": "my-edgeone-project"
      }
    }
  }
}

Deploy a flexible MCP server that lets you publish HTML content, folders, or full-stack projects to EdgeOne Pages and obtain publicly accessible URLs. This server supports both self-hosted deployments and cloud-based options, giving you control, scalability, and straightforward integration with your EdgeOne Pages projects.

How to use

You can use the MCP server to publish static HTML content or entire projects to EdgeOne Pages and receive a public URL. Choose a deployment method that matches your needs: self-hosted EdgeOne Pages deployment for minimal maintenance and HTTPS with your own domain, or a cloud-based option on Tencent Cloud CVM or Tencent CloudBase for managed scaling. After deployment, configure your MCP client to point at the server so you can deploy content and retrieve the published URL.

How to install

Prerequisites: Node.js 18 or higher must be installed on the host where you run the MCP server.

Step 1 — Choose your deployment path and set up the MCP server as shown in the deployment options below.

Option 1: Deploy Self-Hosted Version to EdgeOne Pages (Recommended)

This method is ideal when you want HTTP access and automatic scaling with EdgeOne Pages.

Option 2: Deploy on Tencent Cloud CVM

This approach gives you full server control and supports the stdio transport for local or SSH-based workflows.

Option 3: Deploy Using Tencent CloudBase

Use Tencent CloudBase for quick deployment using managed cloud functions and HTTP triggers.

Security considerations

Regardless of deployment method, protect sensitive tokens, enable HTTPS, and monitor access. Use environment variables for secrets, configure firewalls, and maintain regular logging and alerts.

Troubleshooting

If the service won’t start or deployments fail, verify Node.js version, dependencies, API tokens, and network access. Check logs from the process manager or cloud function logs for detailed error messages.

MCP Configuration

Configure your MCP client to connect to the available MCP server endpoints. The following configurations illustrate how to reference both HTTP-based and stdio-based MCP servers.

Tool details

Deploys include dedicated tools for HTML content and folder/project deployments. These tools handle content delivery, edge storage, and public URL generation.

Notes on custom domains and ICP

Custom domains optimize branding and SEO. If you plan to use a custom domain, ensure ICP filing requirements are met where applicable and verify domain status before deployment.

Available tools

deploy_html

Deploy HTML content through the MCP server to EdgeOne Pages Functions and KV storage, returning a public URL.

deploy_folder

Deploy a complete static or full-stack project to EdgeOne Pages, with an option to update existing projects or create new ones.