home / mcp / edgeone pages mcp server

EdgeOne Pages MCP Server

Deploy HTML, folders, and full-stack projects to EdgeOne Pages and obtain public URLs for edge-delivered content.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "bach-ai-tools-edgeone-pages-mcp": {
      "url": "https://mcp-on-edge.edgeone.site/mcp-server",
      "headers": {
        "EDGEONE_PAGES_API_TOKEN": "<EDGEONE_PAGES_API_TOKEN>",
        "EDGEONE_PAGES_PROJECT_NAME": "<EDGEONE_PAGES_PROJECT_NAME>"
      }
    }
  }
}

You deploy HTML content, folders, or full-stack projects to EdgeOne Pages and receive public URLs that are served from the edge for fast delivery. This MCP server simplifies deploying content and managing it at the edge, with options for HTML, folders, or full-stack deployments.

How to use

You use an MCP client to connect to the EdgeOne Pages MCP Server and run the available tools to deploy content. There are two primary deployment paths:

- deploy_html: deploys generated HTML content to EdgeOne Pages, automatically creating a publicly accessible URL. This is ideal for content produced by an LLM or other generators that you want to publish quickly.

- deploy_folder: deploys complete projects, including static sites or full-stack applications, to EdgeOne Pages. You can update an existing project or create a new one.

How to install

Prerequisites: you need Node.js 18 or higher.

1) Ensure Node.js is installed. Verify with: node -v and npm -v.

2) Create a configuration for the MCP server. You can use the provided examples to connect to EdgeOne Pages MCP. Place the configuration in a file named mcp.config.json in your project directory.

3) Run the MCP client command to start using the EdgeOne Pages MCP. The following examples show the available stdio configurations you can use directly.

{
  "mcpServers": {
    "edgeone-pages-mcp-server": {
      "timeout": 600,
      "command": "npx",
      "args": ["@bachstudio/edgeone-pages-mcp"]
    }
  }
}

{
  "mcpServers": {
    "edgeone-pages-mcp-server": {
      "timeout": 600,
      "command": "npx",
      "args": ["@bachstudio/edgeone-pages-mcp", "--region", "china"]
    }
  }
}

Additional notes on extended configuration and token usage

If you need to deploy folders or zip files to EdgeOne Pages projects, you can provide your EdgeOne Pages API token and optionally specify a project name to update an existing project. This variant is shown in the legacy configuration block.

Tool details summary

Key tools you will use are the deploy_html and deploy_folder tools. deploy_html handles HTML content deployment and edge delivery, while deploy_folder deploys complete sites or apps to EdgeOne Pages.

Available tools

deploy_html

Deploy HTML content generated by your workflow to EdgeOne Pages and obtain a public URL with edge delivery.

deploy_folder

Deploy a full project (static or full-stack) to EdgeOne Pages, with options to update an existing project or create a new one.